From: Peter Stuge <peter@stuge.se>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Guidance on adding kernel config checks to ebuilds
Date: Mon, 27 Sep 2021 19:11:08 +0000 [thread overview]
Message-ID: <20210927191108.899.qmail@stuge.se> (raw)
In-Reply-To: <CAJ0EP42cipF=oRtNOMq3LFUUej7oPHX5UVQwpQWkimesA511HA@mail.gmail.com>
Mike Gilbert wrote:
> It's a waste of time and effort to pepper random ebuilds with checks
> for options that everyone should have enabled in the first place.
It's not for you to say what everyone should have enabled in their kernel.
There's significant value in ebuilds documenting required kernel options in
a structured manner.
So I welcome simplifications in the checking to achieve millisecond
test times. But the benefit of structured requirements is given even
without any runtime checking at all, as long as required options
continue to be codified /somehow/.
Thank you for your work!
//Peter
next prev parent reply other threads:[~2021-09-27 19:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 16:10 [gentoo-dev] Guidance on adding kernel config checks to ebuilds Mike Gilbert
2021-09-27 16:23 ` Mike Pagano
2021-09-27 17:15 ` Mike Gilbert
2021-09-27 17:44 ` Robin H. Johnson
2021-09-27 17:56 ` Rich Freeman
2021-09-27 18:45 ` Mike Gilbert
2021-09-27 18:15 ` Mike Gilbert
2021-09-27 18:17 ` Mike Pagano
2021-09-27 20:28 ` Jason A. Donenfeld
2021-09-27 20:38 ` Mike Gilbert
2021-09-27 18:18 ` Mike Gilbert
2021-09-27 19:11 ` Peter Stuge [this message]
2021-09-27 19:44 ` Mike Gilbert
2021-09-27 20:56 ` Peter Stuge
2021-09-28 14:00 ` Michael Orlitzky
2021-09-27 17:01 ` [gentoo-dev] " Luca Barbato
2021-09-30 13:21 ` [gentoo-dev] " Francesco Riosa
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=20210927191108.899.qmail@stuge.se \
--to=peter@stuge.se \
--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