| 1 |
On Mon, Sep 27, 2021 at 1:56 PM Rich Freeman <rich0@g.o> wrote: |
| 2 |
> |
| 3 |
> On Mon, Sep 27, 2021 at 1:44 PM Robin H. Johnson <robbat2@g.o> wrote: |
| 4 |
> > |
| 5 |
> > I think we need to strip out a lot of the crap about trying to detect |
| 6 |
> > things in the stuff being built, and reduce the check to the simplest |
| 7 |
> > possible form: |
| 8 |
> > $ time zgrep -w CONFIG_PACKET /proc/config.gz |
| 9 |
> > CONFIG_PACKET=y |
| 10 |
> > |
| 11 |
> |
| 12 |
> Sure, just please don't strip out the part that actually does what you |
| 13 |
> just did - check the running kernel. I don't think we should assume |
| 14 |
> that the user has the configured+prepared sources for a kernel just |
| 15 |
> lying around all the time. I don't build in /usr/src (which is |
| 16 |
> apparently discouraged by upstream anyway), so /proc/config.gz is |
| 17 |
> really the only reliable indication of how things are setup. Well, |
| 18 |
> that or a config file in /boot which I'm sure others don't use (but |
| 19 |
> make install puts it there). |
| 20 |
|
| 21 |
I like the idea of a stripped-down implementation that just checks the |
| 22 |
running kernel config when packages get installed. I think that |
| 23 |
probably means creating a new eclass though, or moving some of the |
| 24 |
current complexity into linux-mod.eclass. |
Archives