From: Oleg Verych <olecom@flower.upol.cz>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Jan Engelhardt <jengelh@computergmbh.de>,
zippel@linux-m68k.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Unfortunate infinite make recursion
Date: Sun, 23 Sep 2007 00:23:11 +0200 [thread overview]
Message-ID: <20070922222311.GQ24301@flower.upol.cz> (raw)
In-Reply-To: <20070922204002.GA31873@uranus.ravnborg.org>
On Sat, Sep 22, 2007 at 10:40:02PM +0200, Sam Ravnborg wrote:
> On Sat, Sep 22, 2007 at 05:42:52PM +0200, Oleg Verych wrote:
> > * Sat, 22 Sep 2007 13:24:32 +0200 (CEST)
> > []
> > > The make O=$PWD truncates the Makefile, making it necessary to run `git
> > > checkout Makefile` - should you have git; or reextract the tarball
> > > (should you /still/ have it). Well, can we catch this case somehow?
> >
> > Read-only source-tree for kbuild user, end of question. By current kbuild
> > one can garbage source by various means. Read-write for quilt, git and
> > editor users.
>
> Please Oleg.
> You know very well that most people will not have their kernel src RO.
Sure, if it will be not comfortable.
But if kbuild deals with this transparently, it must be OK. Brokenness
due to binutils, kbuild, root user bugs won't garbage source. Only thing
to ask from experienced users *and* kernel developers, is
`useradd kbuild`, everything else will not bother anybody.
I just express my vision, of course. But see, i can't play with kernel
sources error-free now. If i type some `make` somewhere in obj or src
tree, i need to know, that vanilla source stays so in any circumstances.
Currently it's not.
It is about making things in order on my working place (not looking to be
in order, though :). Not thinking every time, if something fscked sources,
saves my and time of diff/patch. Experimenting/testing/finding fixes with
small amount of in-development sources in obj tree, also very helpful.
____
next prev parent reply other threads:[~2007-09-22 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-22 11:24 Jan Engelhardt
2007-09-22 15:42 ` Oleg Verych
2007-09-22 20:40 ` Sam Ravnborg
2007-09-22 22:23 ` Oleg Verych [this message]
2007-09-23 6:03 ` Sam Ravnborg
2007-09-23 7:37 ` Oleg Verych
2007-09-22 20:52 ` Sam Ravnborg
2007-09-23 6:17 ` Jan Engelhardt
[not found] <96blF-29e-27@gated-at.bofh.it>
2007-09-22 21:19 ` Bodo Eggert
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=20070922222311.GQ24301@flower.upol.cz \
--to=olecom@flower.upol.cz \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=zippel@linux-m68k.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
all inboxes | Powered by JetHome®