All of lore.kernel.org
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: git@vger.kernel.org
Subject: bug: git-sh-setup should not be in $PATH
Date: Wed, 06 Dec 2006 13:14:27 +0100	[thread overview]
Message-ID: <el6c6o$oa7$1@sea.gmane.org> (raw)


Hello,

I often install tools locally so I can run SVN/CVS/etc versions 
in my own account. To do this, I install into

  $HOME/usr/pkg/PACKAGE

and a script that generates scripts in $HOME/usr/bin/ (which is in my $PATH)
like

 #!/bin/sh

 exec /home/lilydev/usr/pkg/git/bin/git-prune "$@"
 # generated: update-pkgs 


this breaks with git-sh-setup; all sh scripts are broken with this
setup.

git-sh-setup isn't a 'normal' binary, in that it should be called by
bash only and not run in a subshell. Therefore I propose that it

- be installed in <prefix>/share/git/

- be invoked with an explicit path, i.e.

  . <prefix>/share/git/



--
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen

             reply	other threads:[~2006-12-06 12:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-06 12:14 Han-Wen Nienhuys [this message]
2006-12-06 12:23 ` bug: git-sh-setup should not be in $PATH Johannes Schindelin
2006-12-06 12:34   ` Han-Wen Nienhuys
2006-12-06 12:56     ` Jakub Narebski
2006-12-06 14:16       ` Han-Wen Nienhuys
2006-12-06 14:51         ` Jakub Narebski
2006-12-06 15:03           ` Han-Wen Nienhuys
2006-12-06 15:27             ` Jakub Narebski
2006-12-06 15:36               ` Han-Wen Nienhuys
2006-12-06 15:56                 ` Jakub Narebski
2006-12-06 16:03                   ` Han-Wen Nienhuys
2006-12-06 16:27                     ` Jakub Narebski
2006-12-06 16:40                       ` Han-Wen Nienhuys
2006-12-06 16:52                         ` Jakub Narebski
2006-12-06 16:56                           ` Han-Wen Nienhuys
2006-12-06 17:11                             ` Jakub Narebski
2006-12-07 13:36                     ` Andreas Ericsson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='el6c6o$oa7$1@sea.gmane.org' \
    --to=hanwen@xs4all.nl \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.