Junio C Hamano wrote:
[...]
Ok. So here is a revised roadmap that a panda brain (that is not so
well working today due to fever) came up.
- 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.
If further will warn users that git-foo form will be removed in
v1.5.6 for many commands and it will be merely an accident if some of
them still work after that.
- Post v1.5.4, start cooking gitexecdir=$(libexecdir)/git-core, aiming
for inclusion in v1.5.5, perhaps in Feb-Mar 2008 timeframe. This
will also affect the sample RPM spec and resulting RPM binary
packages I will place on k.org, and I'll ask Gerrit to do the same on
Debian side. The official binary packaging of individual distros are
not under my control, but if there is a handy list of people I can
send this notice to for other distros, that would help this process.
- The release notes for v1.5.5 will warn users again that git-foo will
be removed in v1.5.6 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.5.6, in May-Jun
2008 timeframe.
Again, there needs to remain support in the Makefile to install the
"dashed" versions of the commands for those that want it; and be able to
set gitexecdir=$(binder) without editing the Makefile.
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
