From: Nix <nix@esperi.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Linda Walsh <lkml@tlinx.org>
Subject: Re: Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root
Date: Tue, 20 Dec 2005 17:44:10 +0000 [thread overview]
Message-ID: <87irtjslxx.fsf@amaterasu.srvr.nix> (raw)
In-Reply-To: <20051220155839.GA9185@mars.ravnborg.org> (Sam Ravnborg's message of "Tue, 20 Dec 2005 16:58:39 +0100")
On Tue, 20 Dec 2005, Sam Ravnborg said:
> Consider following use cases:
> 1) Src located on NFS mounted filesystem
Nothing wrong with that. NFS is fast for me.
(Admittedly, on heavily contended networks you're right.)
> 2) Src on RO media
*Good* reason (one that unionfs would solve, but still...)
> 4) Builds for several architectures from same source base
cp -al
> 5) Builds for several different configurations
cp -al
> It is convinient in many places. Maybe not for you but for others.
There were a couple of compelling arguments in there. :)
--
`I must caution that dipping fingers into molten lead
presents several serious dangers.' --- Jearl Walker
next prev parent reply other threads:[~2005-12-20 17:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 23:27 Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root Linda Walsh
2005-12-19 7:19 ` Jan-Benedict Glaw
2005-12-19 22:12 ` Linda Walsh
2005-12-19 22:30 ` Jan-Benedict Glaw
2005-12-20 1:48 ` Linda Walsh
2005-12-30 6:33 ` patch for "scripts/package/buildtar" to pickup "localversion" on "/boot" file objects Linda A. Walsh
2005-12-30 10:15 ` Erik Mouw
2005-12-30 20:23 ` Linda A. Walsh
2005-12-20 15:41 ` Makefile targets: tar & rpm pkgs, while using O=<dir> as non-root Nix
2005-12-20 15:58 ` Sam Ravnborg
2005-12-20 17:44 ` Nix [this message]
2005-12-20 17:37 ` Sam Ravnborg
2005-12-20 20:25 ` Al Viro
2005-12-21 7:49 ` Nix
2005-12-21 8:18 ` Al Viro
2005-12-21 11:22 ` Nix
[not found] ` <52666.10.10.10.28.1135155403.squirrel@linux1>
2005-12-21 8:56 ` Sean
2005-12-20 17:20 ` Ryan Anderson
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=87irtjslxx.fsf@amaterasu.srvr.nix \
--to=nix@esperi.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.org \
--cc=sam@ravnborg.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