[MERGE][#109143] Support bzr+ssh://host/~/path

[Martin Pool]

2009/3/18 Andrew Bennetts <andrew.bennetts at canonical.com>:
> This feature is overdue.  It allows you to use URLs like:
>
>    bzr+ssh://myhost/~/code/foo
>
> Rather than:
>
>    bzr+ssh://myhost/home/myuser/code/foo
>
> This makes bzr+ssh URLs consistent with SFTP URLs.
>
> I think the only slightly risky thing here is that using /~/ in the URL changes
> the bzr invocation on the remote side from using --directory=/ to --directory=.
>
> If the server's SSH daemon is configured to only allow “bzr serve --inet
> --directory=/ --allow-writes”, or a branch in the user's home directory depends
> on data outside of their home directory (e.g. due to a shared repository in
> /home/), then /~/ won't work for that user.  But that's not a regression, and
> arguably just a server configuration issue rather than an issue in the client's
> behaviour.

It would be great to have that feature.  But if you're implementing it
by changing the ssh invocation method, then that does seem a bit
problematic: it may cause problems with configurations that check the
command, as you say, and it also means it won't work if bzr+ssh is
invoked over something other than ssh.

Could we perhaps instead have either file:///~mbp/foo expand properly,
at least optionally, and then have the server look them up?

-- 
Martin <http://launchpad.net/~mbp/>