From: John Mylchreest <johnm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] linux-info.eclass and $CONFIG_CHECK
Date: Wed, 21 Sep 2005 17:47:09 +0100 [thread overview]
Message-ID: <1127321229.18868.115.camel@localhost> (raw)
In-Reply-To: <1127318615.30787.46.camel@cgianelloni.nuvox.net>
[-- Attachment #1: Type: text/plain, Size: 1873 bytes --]
On Wed, 2005-09-21 at 12:03 -0400, Chris Gianelloni wrote:
> The current /usr/src/linux method works quite well for releases. The
> only issue we're having is a non-fatal check being fatal, which is going
> to be fixed.
OK, so being the huy who wrote and looks after all this stuff, here is
my 2c and reasoning.
First of all, falling back on `uname -r` isn't going to happen for
several reasons. I can understand for some why this might seem sensible
(what happens if you remove your kernel sources for example). But the
fact remains that testing the currently running kernel is not a viable
option in my mind. Why? well, 1: the running kernel bares absolutely no
relevance on the environment which you're building this for. 2: you can
pass KERNEL_DIR manually, so if you refuse to work in the expected way
then set KERNEL_DIR to point to the right location.
Secondly, I have thought about this some more during the day, just as I
did at initial implementation (The code could do with a tidy-up
anyways). After much deliberation I feel the actual best way to deal
with this, is to have an override envvar which will bypass a die, and
simply warn instead. This will mean that those people who cross-compile
regularly, or building stages etc will work fine, and normal operation
would continue to refuse a build if the environment its building for
doesn't seem sane. At the end of the day, the true root cause of
something die'ing when it shouldn't is at the ebuild. That.. and if its
really not that important, then surely the ebuild can call the config
check itself, and handle it as it feels fit.
I'll update the bug also with this.
--
Role: Gentoo Linux Kernel Lead
Gentoo Linux: http://www.gentoo.org
Public Key: gpg --recv-keys 9C745515
Key fingerprint: A0AF F3C8 D699 A05A EC5C 24F7 95AA 241D 9C74 5515
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-09-21 16:54 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 7:42 [gentoo-dev] linux-info.eclass and $CONFIG_CHECK Georgi Georgiev
2005-09-21 8:18 ` Marius Mauch
2005-09-21 8:27 ` Paul de Vrieze
2005-09-21 8:33 ` Georgi Georgiev
2005-09-21 11:43 ` Andrew Gaffney
2005-09-21 13:11 ` Chris Gianelloni
2005-09-21 13:18 ` Paul de Vrieze
2005-09-21 15:01 ` Martin Schlemmer
2005-09-21 9:41 ` Alin Nastac
2005-09-21 9:44 ` Henrik Brix Andersen
2005-09-21 13:17 ` Daniel Drake
2005-09-21 13:26 ` Chris Gianelloni
2005-09-21 13:57 ` Alin Nastac
2005-09-21 14:22 ` Chris Gianelloni
2005-09-21 14:33 ` Henrik Brix Andersen
2005-09-21 15:51 ` Mike Frysinger
2005-09-21 15:57 ` Chris Gianelloni
2005-09-21 15:05 ` Martin Schlemmer
2005-09-21 16:03 ` Chris Gianelloni
2005-09-21 16:47 ` John Mylchreest [this message]
2005-09-21 17:52 ` Chris Gianelloni
2005-09-22 8:46 ` Paul de Vrieze
2005-09-22 13:36 ` Chris Gianelloni
2005-09-22 10:49 ` Henrik Brix Andersen
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=1127321229.18868.115.camel@localhost \
--to=johnm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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