From: Junio C Hamano Date: Mon, 14 Nov 2005 21:15:31 GMT Subject: Re: [ANNOUNCE] GIT 0.99.9g Message-ID: <7vwtjbvslo.fsf@assigned-by-dhcp.cox.net> In-Reply-To: <4378578E.5090409@op5.se> Andreas Ericsson writes: > Junio C Hamano wrote: >> My current thinking about this problem is that the handful >> programs that need to run "on the other end" should stay in >> /usr/bin, even after we move most things out of /usr/bin, if >> only to avoid configuration hassles. They are: >> receive-pack, upload-pack >> ssh-fetch, ssh-pull, ssh-push, ssh-upload > > I liked your suggestion of deprecating the /usr/bin use a month or two > before it's effected better. We could then provide symlinks for the > necessary programs that point to their real locations in GIT_EXEC_PATH > and (someday) drop those links when they're no longer needed. Yes, but the problem is when that "someday" comes. Unlike a single machine installation where we can tell "git" to look into somewhere different at the same time we move the subcommands out of /usr/bin, "the other end" can lag behind and sometimes not under control of the end user. I think it's simpler to manage and can be made configuration free if we keep receive-pack and upload-pack in /usr/bin and always call these programs in dash-form (i.e. not "git upload-pack") from the other end. .bash_profile is not read for incoming ssh connections to execute a single command, but many people set their PATH in there, without setting PATH in .bashrc. I personally think that having to set PATH in .bashrc it is actually a bug in what bash does, but that is OT.