Hi Jonathan, On Tue, Jan 31, 2012 at 10:33:38AM -0600, Jonathan Nieder wrote: > When I try to use my copy of git like this: > > git clone bzr::lp:bash > > I get the following result: > > Cloning into 'bash'... > fatal: Unable to find remote helper for 'bzr' > > The cause seems to be that git-remote-bzr is installed in a private > directory fo the git copy in /usr, so my private copy under $HOME > does not see it. > > If I install bzr-git from the upstream source, the remote helper seems > to go on the $PATH instead, which works[*]. > > Thoughts? > Jonathan > > [*] It is possible that git should provide some infrastructure with > its own PATH or PYTHONPATH-style variable for other packages to > register new commands instead of cluttering the main PATH. Feel free > to contact [email protected] about that, cc-ing me and Jon Seymour > <[email protected]> or file a bug against the Debian git package. Thanks for the patch.
The main reason I was installing into /usr/lib/git-core was that it meant not polluting /usr/bin with something that shouldn't be invoked directly. Upstream installs to /usr/bin because there is no easy way to find out the proper git library directory. It really does belong in /usr/lib/git-core I think (or some sort git-specific directory), so I'll file a bug against git requesting something like that per your suggestion. For now, I'll apply your patch and install to /usr/bin. A single extra file in /usr/bin isn't the end of the world. Plus, git-remote-bzr actually has a man page these days. :-) Cheers, Jelmer
signature.asc
Description: Digital signature
