On Tuesday 27 October 2009, Benito Mourelo Caldeiro wrote:
> On Tue, 2009-10-27 at 09:56 +0300, Ville Skyttä wrote:
>
> > If "git command" vs "git-command" is the only
incompatibility, it should
> > be trivial to provide the latter in the package with tiny wrapper scripts
> > or even just one that parses $0 and add symlink to it for each needed
> > command, or install that script multiple times with different names and
> > hardlink them if wanted, or... (see for example rpmdev-md5, rpmdev-sha*
> > and friends in rpmdevtools).
>
> No problem, I build a package from the last SRPM at
git-scm.com and all
> are in /usr/libexec/git-core. You only need to append it to $PATH if you
> you prefer the old mode.
Well, if one needs to do that manually, it's not backwards compatible. And
even adding a new dir to $PATH wouldn't help scripts that use absolute paths
pointing to the old location of the tools.
(I don't have an opinion whether to update git in EPEL or not.)
Ok.
One solution could be use update-alternatives for old git-* commands
(they are 141 !).
Saudos.