* Ramifications of a git-sh-setup outside the PATH
@ 2008-06-27 19:00 Jonathan Nieder
2008-06-28 12:01 ` Alex Riesen
0 siblings, 1 reply; 2+ messages in thread
From: Jonathan Nieder @ 2008-06-27 19:00 UTC (permalink / raw)
To: git
Hi gitsters,
I noticed in the release notes to Git 1.6.0 that dashed-form commands
are moving to a libexecdir outside the PATH. I have been using Git
with nd/dashless applied for about a month, and it does work well
(thanks!). There was one little glitch: to use hg-fast-export.sh from
fast-export.git (of repo.or.cz), I had to put git-sh-setup in the PATH.
I wanted to just change the ". git-sh-setup" line to ". git sh-setup",
but of course that will not work. Am I missing something?
hg-fast-export uses git-sh-setup to handle --help, to provide the
cd_to_toplevel function, and to set GIT_DIR. It would not take much
work to avoid using git-sh-setup, although for my needs it was easier
to put git-sh-setup in the PATH. But really, the use of git-sh-setup
does not seem strange to me at all. Is use of git-sh-setup in scripts
outside Git core discouraged?
The location of git-sh-setup was discussed before in the thread
<http://thread.gmane.org/gmane.comp.version-control.git/33708>.
Thanks for your time, and thank you for Git!
Sincerely,
Jonathan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Ramifications of a git-sh-setup outside the PATH
2008-06-27 19:00 Ramifications of a git-sh-setup outside the PATH Jonathan Nieder
@ 2008-06-28 12:01 ` Alex Riesen
0 siblings, 0 replies; 2+ messages in thread
From: Alex Riesen @ 2008-06-28 12:01 UTC (permalink / raw)
To: Jonathan Nieder; +Cc: git
Jonathan Nieder, Fri, Jun 27, 2008 21:00:27 +0200:
> Hi gitsters,
>
> I noticed in the release notes to Git 1.6.0 that dashed-form commands
> are moving to a libexecdir outside the PATH. I have been using Git
> with nd/dashless applied for about a month, and it does work well
> (thanks!). There was one little glitch: to use hg-fast-export.sh from
> fast-export.git (of repo.or.cz), I had to put git-sh-setup in the PATH.
>
> I wanted to just change the ". git-sh-setup" line to ". git sh-setup",
> but of course that will not work. Am I missing something?
Try
. "$(git --exec-path)/git-sh-setup"
"git-sh-setup" is not a command, but a Bourne Shell script you can use
in your scripts by including it. So ". git sh-setup" just tries to
_include_ file "git" (and will try $PATH and current directory) with
positional argument "sh-setup" (see man 1 bash, for example).
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2008-06-28 12:02 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-06-27 19:00 Ramifications of a git-sh-setup outside the PATH Jonathan Nieder
2008-06-28 12:01 ` Alex Riesen
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).