From: Junio C Hamano <junkio@cox.net>
To: Alan Chandler <alan@chandlerfamily.org.uk>
Cc: git@vger.kernel.org
Subject: Re: Problem with template location
Date: Wed, 09 Nov 2005 13:29:32 -0800 [thread overview]
Message-ID: <7vr79pbjcz.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <200511092045.55300.alan@chandlerfamily.org.uk> (Alan Chandler's message of "Wed, 9 Nov 2005 20:45:55 +0000")
Alan Chandler <alan@chandlerfamily.org.uk> writes:
> I don't know whether this is something that can be fixed at install time, or
> whether the README should be changed to make it clear that you need the
> prefix on the first stage of the process as well as the second.
Thanks Alan and Jon. This seems to be hitting some people so
here is what I plan to push out.
-- >8 -- cut here -- >8 --
Subject: Update INSTALL
Explicitly mention how to install by hand in build-as-user and
install-as-root steps.
Signed-off-by: Junio C Hamano <junkio@cox.net>
---
INSTALL | 9 ++++++---
1 files changed, 6 insertions(+), 3 deletions(-)
applies-to: 132cf7a143b9ed08e69399da6caa0c627d26f181
c44922a7817398d63bb2b46dc599bd05c710e746
diff --git a/INSTALL b/INSTALL
index bbb13f3..06b11e1 100644
--- a/INSTALL
+++ b/INSTALL
@@ -5,10 +5,13 @@ Normally you can just do "make" followed
will install the git programs in your own ~/bin/ directory. If you want
to do a global install, you can do
- make prefix=/usr install
+ $ make prefix=/usr ;# as yourself
+ # make prefix=/usr install ;# as root
-(or prefix=/usr/local, of course). Some day somebody may send me a RPM
-spec file or something, and you can do "make rpm" or whatever.
+(or prefix=/usr/local, of course). Just like any program suite
+that uses $prefix, the built results have some paths encoded,
+which are derived from $prefix, so "make all; make prefix=/usr
+install" would not work.
Issues of note:
---
0.99.9.GIT
next prev parent reply other threads:[~2005-11-09 21:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 20:45 Problem with template location Alan Chandler
2005-11-09 21:06 ` Jon Loeliger
2005-11-09 21:29 ` Junio C Hamano [this message]
2005-11-09 21:49 ` Peter Eriksen
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=7vr79pbjcz.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=alan@chandlerfamily.org.uk \
--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