public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arun Raghavan <ford_prefect@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About udev-145: new features / extras and kernel  requirements
Date: Sun, 30 Aug 2009 19:54:47 +0530	[thread overview]
Message-ID: <6f8b45100908300724h206273b0i9f36cbdf8ef9d271@mail.gmail.com> (raw)
In-Reply-To: <200908301611.53087.zzam@gentoo.org>

2009/8/30 Matthias Schwarzott <zzam@gentoo.org>:
> 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

All of the above? Rationale being (1) is required to check against the
kernel you're supposedly using, (2) for the kernel you definitely are
using, and (3) to make sure people remember.

An alternative to (2) and (3), though is to add a check to the udev initscript.

Cheers,
-- 
Arun Raghavan
http://arunraghavan.net/
(Ford_Prefect | Gentoo) & (arunsr | GNOME)



  reply	other threads:[~2009-08-30  9:16 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 [this message]
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
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=6f8b45100908300724h206273b0i9f36cbdf8ef9d271@mail.gmail.com \
    --to=ford_prefect@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