BZR_REMOTE_PATH as a per-branch option

[Jelmer Vernooij]

Daniel Clemente wrote:
>   Hi,
> 
>   I installed bzr in ~/bin/bzr in a hosting server. To make push/pull/… find it, I had to use the enviroment variable BZR_REMOTE_PATH=/home7/danielcl/bin/bzr in my local machine.
>   I added this to my .bashrc since I couldn't find a better place to declare it. I don't want to type it each time because I will often use that server.
> 
>   However, when I connect to other servers, this setting also applies. Ex:
> 
> --------------------
> : ~/.bazaar/plugins/bzrtools ; bzr.dev pull 
> Using saved parent location: bzr+ssh://bazaar.launchpad.net/~abentley/bzrtools/bzrtools.dev/
> Enter passphrase for key '/home/dc/.ssh/id_rsa':                                                                              
> Server does not understand Bazaar network protocol 3, reconnecting.  (Upgrade the server to avoid this.)                      
> Enter passphrase for key '/home/dc/.ssh/id_rsa': 
> Server does not understand Bazaar network protocol 2, reconnecting.  (Upgrade the server to avoid this.)                      
> bzr: ERROR: Generic bzr smart protocol error: Server is not a Bazaar server: Received bad protocol version marker: "Not allowed to execute '/home7/danielcl/bin/bzr serve --inet --directory=/ --allow-writes'.\r\n"
> 
> : ~/.bazaar/plugins/bzrtools ; 
> --------------------
> 
> 
>   My question is therefore: can I enable BZR_REMOTE_PATH just for some branches? Could it be a per-branch option, like whoami?
Yes, you can put something in locations.conf. For example, I have the
following set:

[bzr+ssh://people.samba.org/]
bzr_remote_path = /home/jelmer/bzr.dev/bzr

Cheers,

Jelmer