| 1 |
On Sun, Aug 30, 2009 at 10:45 AM, William Hubbs<williamh@g.o> wrote: |
| 2 |
> On Sun, Aug 30, 2009 at 08:16:47PM +0530, Nirbheek Chauhan wrote: |
| 3 |
>> On Sun, Aug 30, 2009 at 7:41 PM, Matthias Schwarzott<zzam@g.o> wrote: |
| 4 |
>> > Hi there! |
| 5 |
>> > |
| 6 |
>> > The new udev-145 and newer have some new kernel requirements. How should the |
| 7 |
>> > ebuild verify they are met? |
| 8 |
>> > Some possible ways: |
| 9 |
>> > 1. Check config under /usr/src/linux |
| 10 |
>> > 2. Check /proc/config.gz |
| 11 |
>> > 3. Print message for user in pkg_postinst |
| 12 |
>> > |
| 13 |
>> |
| 14 |
>> ebuilds usually use linux-info.eclass for this, but that only checks |
| 15 |
>> /usr/src/linux -- although checking /proc/config.gz *as well* would be |
| 16 |
>> better. That change should be made in the eclass. |
| 17 |
> |
| 18 |
> I agree here. The eclass should check /proc/config.gz. |
| 19 |
> Also, another reason to use the eclass is it respects KBUILD_OUTPUT if |
| 20 |
> it is set. |
| 21 |
> |
| 22 |
> If /proc/config.gz is the first thing we check, I don't think we need to |
| 23 |
> bother at all with checking .config since we know the setup of the |
| 24 |
> running kernel. What does everyone think? |
| 25 |
|
| 26 |
William, not picking on you, just replying in general. |
| 27 |
|
| 28 |
People that suggest to only check /proc/config.gz only are pretty |
| 29 |
crazy considering that file is a tunable option. What if the user has |
| 30 |
CONFIG_IKCONFIG_PROC=n?? The ebuild fails?! Of course, I haven't seen |
| 31 |
any code yet, so maybe people are just suggesting to check config.gz |
| 32 |
if is exists, then proceed via other means? ;-) |
| 33 |
|
| 34 |
-Jeremy |
Archives