[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-dev
Subject:    Re: [gentoo-dev] Guidance on adding kernel config checks to ebuilds
From:       Francesco Riosa <vivo75 () gmail ! com>
Date:       2021-09-30 13:21:24
Message-ID: CAD6zcDy24+dTEGt4xkTLkzO9YNMDXO=K-MT3U+D3GHRDAo8R6Q () mail ! gmail ! com
[Download RAW message or body]

Il giorno lun 27 set 2021 alle ore 18:11 Mike Gilbert <floppym@gentoo.org>
ha scritto:

> I'm looking to solicit opinions on when it is appropriate for an
> ebuild to check for kernel config options using linux-info.eclass. I
> don't think we have any guidelines documented, instead leaving it up
> to the "common sense" of package maintainers.
>
> <snip>

After so many tentatives to fix the kernel checks in these years (almost
all of which had drawbacks or missed some extreme corner case) it's
probably better to give to the user instruments to do ihs own checks rather
than trying to be smart.

An example of how this could work follow:
A file (or directory) is created in /etc/ that contains a list of
<ebuild>,<config_option>,<state_required>
Then the user is responsible to check that list against the wanna be
running kernel

This save probably both computational and human time

state_required - should be well thought out since it can be required
present, absent or maybe even suggested

[Attachment #3 (text/html)]

<div dir="ltr"><div dir="ltr">Il giorno lun 27 set 2021 alle ore 18:11 Mike Gilbert \
&lt;<a href="mailto:floppym@gentoo.org">floppym@gentoo.org</a>&gt; ha \
scritto:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex">I&#39;m looking to solicit opinions on when it is \
appropriate for an<br> ebuild to check for kernel config options using \
linux-info.eclass. I<br> don&#39;t think we have any guidelines documented, instead \
leaving it up<br> to the &quot;common sense&quot; of package \
maintainers.<br><br></blockquote><div>&lt;snip&gt;  </div><div><br></div><div>After \
so many tentatives to fix the kernel checks in these years (almost all of which had \
drawbacks or missed some extreme corner case) it&#39;s probably better to give  to \
the user instruments to do ihs own checks rather than trying to be smart.<br><br>An \
example of how this could work follow:</div><div>A file (or directory) is created in \
/etc/ that contains a list of \
&lt;ebuild&gt;,&lt;config_option&gt;,&lt;state_required&gt;<br>Then the user is \
responsible to check that list against the wanna be running  kernel<br><br>This save \
probably both computational and human time<br><br>state_required - should be well \
thought out since it can be required present, absent or maybe even \
suggested<br><br></div></div></div>



[prev in list] [next in list] [prev in thread] [next in thread]