found 625753 git/1:1.7.5-1
quit
Hi Peter,
Peter Eisentraut wrote:
> I use git-new-workdir
> (/usr/share/doc/git/contrib/workdir/git-new-workdir) quite a bit. It
> would be nice to make it easier to access.
See also [1] and [2].
> In the alternative, make the existing
> location executable, so that one could symlink it to /usr/local/bin or
> ~/bin or whatever. The way it currently is I either have to make a
> copy and change the permissions, or change the permissions on the
> packaged file, both of which have some drawbacks.
Yep. Currently git-new-workdir is packaged as though it were just an
example of how to script git. To treat it as part of the
functionality of the package, we'd have to move it out of
/usr/share/doc. So you are quite right, there is a real bug here ---
and it wouldn't even be enough to just "chmod +x" it to fix.
Where should the contributed add-ons go? The obvious answer is
/usr/lib/git, but that could be confusing since its name is so similar
to /usr/lib/git-core (where the standard commands go). Maybe it
should be like so:
$ ls -l /usr/lib/git
total 4
lrwxrwxrwx 1 root root 11 May 5 14:58 commands ->
../git-core
drwxr-xr-x 4 root root 4096 May 5 14:58 contrib
What do you think?
In the meantime it is possible to work around this by putting the
following as git-new-workdir in your ~/bin:
#!/bin/sh
exec sh /usr/share/doc/git/contrib/workdir/git-new-workdir "$@"
[1] http://bugs.debian.org/619782
[2] https://git.wiki.kernel.org/index.php/SoC2011Ideas#Multiple_work_trees
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
