From: Andreas Ericsson <ae@op5.se>
To: walt <wa1ter@myrealbox.com>
Cc: git@vger.kernel.org
Subject: Re: Does git belong in root's $PATH?
Date: Sat, 07 Jan 2006 19:03:06 +0100 [thread overview]
Message-ID: <43C0025A.9080406@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.64.0601070838470.6317@x2.ybpnyarg>
walt wrote:
> When updated my kernel this morning, the same way I've been doing
> it for many months, I noticed that the -gxxxxxxx localversion
> string was missing from the new kernel's name.
>
> I finally figured out that this happened because /usr/local/bin
> is not in my root's $PATH, and the setlocalversion script depends
> on git. (The only thing I do as root is 'make install').
>
> I suppose I'm asking a philosophical question here: do you
> guys install git where root can find it (as a system tool)?
I install it in /usr/bin. I don't *use* the git-tools as root though, so
I don't feel there's anything to worry about (well, at least no more
than for the other 2847 programs living in my $PATH).
> Does it really matter?
Theoretically, yes, but only if someone can trick you to, as root, doing
something with git which triggers some yet undiscovered bug and makes it
run code it was never meant to.
> (The linux distribution I use is very
> picky about what it includes in root's path...)
>
Not including /usr/local/{bin,sbin} in root's path is considered wise,
since, historically, that's where users would install their own versions
of programs that the system doesn't provide. This use has largely been
obsoleted by $HOME/bin as the default for user-specific programs, mainly
because of disks getting larger and cheaper.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2006-01-07 18:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-07 17:21 Does git belong in root's $PATH? walt
2006-01-07 18:03 ` Andreas Ericsson [this message]
2006-01-07 20:40 ` H. Peter Anvin
2006-01-08 0:37 ` Andreas Ericsson
2006-01-08 0:39 ` H. Peter Anvin
2006-01-08 1:22 ` walt
2006-01-08 3:00 ` H. Peter Anvin
2006-01-07 18:31 ` Linus Torvalds
2006-01-07 20:49 ` H. Peter Anvin
2006-01-07 23:01 ` Sam Ravnborg
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=43C0025A.9080406@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=wa1ter@myrealbox.com \
/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).