From: Junio C Hamano <gitster@pobox.com>
To: Jan Wielemaker <J.Wielemaker@uva.nl>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Bug: /usr/local/bin/git-daemon starts /usr/sbin/git-upload-pack?
Date: Wed, 09 Jul 2008 14:14:06 -0700 [thread overview]
Message-ID: <7vlk0a7obl.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <200807092220.10655.J.Wielemaker@uva.nl> (Jan Wielemaker's message of "Wed, 9 Jul 2008 22:20:10 +0200")
Jan Wielemaker <J.Wielemaker@uva.nl> writes:
> After upgrade to SuSE 11.0 I was forced to update GIT (changed libcurl).
> I did (with some trickery) a pull of the latest git and built it using
> make prefix=/usr/local ..., to find out that /usr/local/bin/git-daemon
> starts /usr/sbin/git-upload-pack.
>
> After creating a symlink to /usr/local/bin/git-upload-pack all works fine
> again, but I guess this is a mistake?
I think this is a distro issue.
Pre-1.6.0 git installs git-everything in $(bindir) and knows things are
there. Current 'master' we are preparing for 1.6.0 instead installs
git-mostofthem in $(prefix)/libexec/git-core and git-someofthem in
$(bindir); our executables know which binaries are installed in $(bindir)
and which ones are installed in $(prefix)/libexec/git-core.
The point is we never install $anywhere/sbin unless the person who is
building explicitly does so (either by futzing the Makefile or giving
bindir=$somewhere from the command line of "make"). The reason your
/usr/local/bin/git-daemon (we do not know who compiled it and how) spawns
something in /usr/sbin is not our doing. Find out who configured it and
why, and more importantly, what _other_ changes are made in the build and
installation procedure to support that change in location.
next prev parent reply other threads:[~2008-07-09 21:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-09 20:20 Bug: /usr/local/bin/git-daemon starts /usr/sbin/git-upload-pack? Jan Wielemaker
2008-07-09 21:14 ` Junio C Hamano [this message]
2008-07-10 7:38 ` Jan Wielemaker
2008-07-10 7:32 ` Brian Foster
2008-07-10 8:59 ` Jeff King
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=7vlk0a7obl.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=J.Wielemaker@uva.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 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).