Re: [PATCH] Move all dashed form git commands to libexecdir
- From
A Large Angry SCM <gitzilla@gmail.com>
- Date
- Nov 29, 2007, 00:59 UTC
- Message-ID
- <474E0EE6.6070107@gmail.com>
- In-Reply-To
- <7vfxyq2c9b.fsf@gitster.siamese.dyndns.org>
Junio C Hamano wrote: [...]
Show 25 quoted lines
> Would people agree with a rough roadmap like this? > > - v1.5.4 will ship with gitexecdir=$(bindir) in Makefile. But the > release notes for the version will warn users that: > > (1) using git-foo from the command line, and > > (2) using git-foo from your scripts without first prepending the > return value of "git --exec-path" to the PATH > > is now officially deprecated (it has been deprecated for a long time > since January 2006, v1.2.0~149) and upcoming v1.5.5 will ship with > the default configuration that does not install git-foo form in > user's PATH. > > - Post v1.5.4, start cooking gitexecdir=$(libexecdir)/git-core, aiming > for inclusion in v1.5.5, perhaps in Mar-Feb 2008 timeframe. > > - The release notes for v1.5.5 will warn users that git-foo will be > removed in v1.6.0 for many commands and it will be merely an accident > if some of them still work. > > - Post v1.5.5, start cooking the change that does not install hardlinks > for built-in commands, aiming for inclusion in v1.6.0, by the end of > 2008.
So long as there remains the option in the Makefile to install the "dashed" commands in $(bindir) for those of us that wish it.