git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Install git-sh-setup.sh into $(prefix)/share/git-core. Call with explicit path.

From
Han-Wen Nienhuys <hanwen@xs4all.nl>
Date
Dec 9, 2006, 13:08 UTC
Message-ID
<457AB54B.8070107@xs4all.nl>
In-Reply-To
<7v3b7qi0b4.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano escreveu:
Show 12 quoted lines
> Eric Wong <normalperson@yhbt.net> writes:
> 
>> Han-Wen Nienhuys <hanwen@xs4all.nl> wrote:
>>> git-sh-setup isn't a 'normal' binary, in that it should be called by
>>> bash only and not run in a subshell. Therefore, it should not be installed
>>> in a executable directory, but rather in $prefix/share/git-core/
>> This seems to break existing hooks, or at least old repositories can
>> be stuck using an old version of git-sh-setup in those hooks.
> 
> Honestly speaking, I do not think this patch is worth it.
> People who care deeply enough should just use gitexecdir that is
> separate from bindir.

And how about coding the path of git-sh-setup (in <prefix>/bin/git-sh-setup) in the shell scripts? This will ensure that the sh-setup is the one from the right package, but still retain backward compatibility for scripts.

Previous: Junio C HamanoNext: Junio C Hamano
Message 6 of 9 in “Install git-sh-setup.sh into $(prefix)/share/git-core. Call with explicit path.”
  1. Install git-sh-setup.sh into $(prefix)/share/git-core. Call with explicit path.Han-Wen Nienhuys, Dec 8, 2006
  2. Nguyen Thai Ngoc DuyDec 8, 2006
  3. Han-Wen NienhuysDec 8, 2006
  4. Eric WongDec 8, 2006
  5. Junio C HamanoDec 8, 2006
  6. Han-Wen NienhuysDec 9, 2006
  7. Junio C HamanoDec 9, 2006
  8. Han-Wen NienhuysDec 9, 2006
  9. Junio C HamanoDec 10, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.