From: Hallvard B Furuseth <h.b.furuseth@usit.uio.no>
To: Phillip Susi <psusi@ubuntu.com>
Cc: <git@vger.kernel.org>
Subject: Re: make install rewrites source files
Date: Fri, 27 Jan 2012 10:46:55 +0100 [thread overview]
Message-ID: <79b0e5e55a438cc757cfeb6408be4d23@ulrik.uio.no> (raw)
In-Reply-To: <4F1DC2F7.2070502@ubuntu.com>
On Mon, 23 Jan 2012 15:28:39 -0500, Phillip Susi <psusi@ubuntu.com>
wrote:
> On 1/23/2012 9:18 AM, Hallvard Breien Furuseth wrote:
>> However, make install should not write to the source directory in
>> any case. That fails as root if root lacks write access there, due
>> to NFS mounts that map root to nobody etc. At least git-instaweb
>> and GIT-BUILD-OPTIONS are rewritten. You can simulate this with su
>> nobody -s /bin/bash -c 'make -k install' after configuring with
>> prefix=<directory owned by nobody>.
>
> If you want to build locally from a read only nfs mount, then you
> should run the configure script in a local directory:
>
> mkdir /tmp/build
> (...)
Not a read-only nfs mount. Just an ordinary remote mount where root
on the local host is mapped to nobody on the remote host. (Having
local root access does not mean you should get root on the remote.)
In any case, it's normal practice to do as little as possible as root,
and also to at least try not write to the source dir during install.
BTW, building in /tmp can be nasty to other users when you don't know
how much space the build (and maybe test) will use, so you may need
access to some other local dir.
--
Hallvard
prev parent reply other threads:[~2012-01-27 10:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 14:18 make install rewrites source files Hallvard Breien Furuseth
2012-01-23 20:15 ` Junio C Hamano
2012-01-23 20:57 ` Hallvard Breien Furuseth
2012-01-26 22:52 ` Clemens Buchacher
2012-01-27 0:49 ` Junio C Hamano
2012-01-27 13:11 ` Hallvard Breien Furuseth
2012-01-23 20:28 ` Phillip Susi
2012-01-23 20:52 ` Junio C Hamano
2012-01-27 9:46 ` Hallvard B Furuseth [this message]
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=79b0e5e55a438cc757cfeb6408be4d23@ulrik.uio.no \
--to=h.b.furuseth@usit.uio.no \
--cc=git@vger.kernel.org \
--cc=psusi@ubuntu.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).