Re: [Duplicity-talk] Scp calls

[AJ Weber]

Yes, re-directing the scp to be a script + scp would probably work.  Would 
not be elegant, but would probably work.

I'm not sure about the "wrapper script".  I'm not familiar with that.  I 
know you can pass custom ssh params, but have not seen how that actually 
runs the params (maybe that's not what you're talking about at all).  But it 
would have to be a bit of a hack like "knock server && scp server..."

----- Original Message ----- 
From: "Gabriel Ambuehl" <address@hidden>
To: "AJ Weber" <address@hidden>
Cc: "Discussion of the backup program duplicity" <address@hidden>
Sent: Monday, January 04, 2010 12:58 PM
Subject: Re: [Duplicity-talk] Scp calls


> On 04.01.2010 18:53, AJ Weber wrote:
> > That would be exactly what I would have to do, which means editing the 
> > source code -- and I'm not "against" that, nor "afraid" of it, but it 
> > breaks compatibility with future duplicity upgrades, etc.
> >
> > I assume I'd have to edit the sshBackend... code, but maybe it would be 
> > better to do it in the main code so the backend becomes irrelevant.  I 
> > could maybe implement a "Pre-Connect" and "Post-Connect" hook of sorts 
> > that gets called before/after the actual backend connection operation.
> >
> > Does anyone think that's worthwhile to develop and add to the project, 
> > and Ken, would you want to add that back into the codeline as a new 
> > feature should I develop it?  I might actually do that work if it was to 
> > be included back into future versions; less enthusiastic if I was doing 
> > it just for me as a once-off.
>
> Can't you simply tell duplicity to use the scp wrapper script instead of 
> pure scp and pass all options to scp inside the script? Worse case 
> renaming scp and using the script in its location should work for sure...