From: Jeremy Olexa <darkside@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About udev-145: new features / extras and kernel requirements
Date: Mon, 31 Aug 2009 10:46:56 -0500 [thread overview]
Message-ID: <90b936c0908310846s4b398761x154d464242fedb3e@mail.gmail.com> (raw)
In-Reply-To: <20090830154520.GA32569@linux1>
On Sun, Aug 30, 2009 at 10:45 AM, William Hubbs<williamh@gentoo.org> wrote:
> On Sun, Aug 30, 2009 at 08:16:47PM +0530, Nirbheek Chauhan wrote:
>> On Sun, Aug 30, 2009 at 7:41 PM, Matthias Schwarzott<zzam@gentoo.org> wrote:
>> > Hi there!
>> >
>> > The new udev-145 and newer have some new kernel requirements. How should the
>> > ebuild verify they are met?
>> > Some possible ways:
>> > 1. Check config under /usr/src/linux
>> > 2. Check /proc/config.gz
>> > 3. Print message for user in pkg_postinst
>> >
>>
>> ebuilds usually use linux-info.eclass for this, but that only checks
>> /usr/src/linux -- although checking /proc/config.gz *as well* would be
>> better. That change should be made in the eclass.
>
> I agree here. The eclass should check /proc/config.gz.
> Also, another reason to use the eclass is it respects KBUILD_OUTPUT if
> it is set.
>
> If /proc/config.gz is the first thing we check, I don't think we need to
> bother at all with checking .config since we know the setup of the
> running kernel. What does everyone think?
William, not picking on you, just replying in general.
People that suggest to only check /proc/config.gz only are pretty
crazy considering that file is a tunable option. What if the user has
CONFIG_IKCONFIG_PROC=n?? The ebuild fails?! Of course, I haven't seen
any code yet, so maybe people are just suggesting to check config.gz
if is exists, then proceed via other means? ;-)
-Jeremy
next prev parent reply other threads:[~2009-08-31 10:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 14:11 [gentoo-dev] About udev-145: new features / extras and kernel requirements Matthias Schwarzott
2009-08-30 14:24 ` Arun Raghavan
2009-08-30 15:26 ` [gentoo-dev] " Duncan
2009-08-30 14:46 ` [gentoo-dev] " Nirbheek Chauhan
2009-08-30 15:45 ` William Hubbs
2009-08-30 16:18 ` Mike Auty
2009-08-31 15:46 ` Jeremy Olexa [this message]
2009-08-31 4:25 ` Lars Wendler
2009-08-30 15:05 ` Bruno
2009-08-30 19:20 ` Robin H. Johnson
2009-11-09 16:35 ` Mart Raudsepp
2009-11-12 9:08 ` Matthias Schwarzott
2009-11-09 19:22 ` Daniel Drake
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=90b936c0908310846s4b398761x154d464242fedb3e@mail.gmail.com \
--to=darkside@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