From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] About the 'eapi' file in profile directories
Date: Sun, 1 Aug 2021 03:02:10 +0100 [thread overview]
Message-ID: <9D494357-A100-4E3C-88F7-FFEE98AF4A3A@gentoo.org> (raw)
In-Reply-To: <35f80c1a-ed6e-a231-d0ea-c69de7b9161f@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
> On 1 Aug 2021, at 00:23, Joshua Kinard <kumba@gentoo.org> wrote:
>
>> [snip]
>
> Yeah, I found one mention in the Wiki[1], but not under "Profiles" in the
> devmanual[2]. The Wiki description doesn't say why that file is needed in
> every single subdirectory.
>
> [1] https://wiki.gentoo.org/wiki/Profile_(Portage)#Profile_structure
> [2] https://devmanual.gentoo.org/profiles/index.html
>
> That said, the PMS reference actually provides the clearest explanation. I
> think that language should be in the devmanual at [2], as it also explains
> the lack of inheritance.
>
Does this PR [0] for the devmanual help a bit? Let me know if you have feedback
(either here or on GitHub is fine, I don't mind).
> Okay, mystery solved. We'll have to someday revisit why this file can't be
> inherited, which would allow us to reduce the number of copies in the tree.
>
Yeah, I think this is worth investigating. I've wondered the same thing before.
[0] https://github.com/gentoo/devmanual/pull/240
best,
sam
[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2021-08-01 2:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-31 22:42 [gentoo-dev] About the 'eapi' file in profile directories Joshua Kinard
2021-07-31 22:47 ` Sam James
2021-07-31 23:23 ` Joshua Kinard
2021-08-01 2:02 ` Sam James [this message]
2021-08-01 4:58 ` Joshua Kinard
2021-08-01 12:19 ` Mart Raudsepp
2021-08-01 19:19 ` Joshua Kinard
2021-08-01 20:00 ` Joshua Kinard
2021-08-01 21:54 ` Ulrich Mueller
2021-08-02 13:39 ` Rich Freeman
2021-08-01 13:59 ` Ulrich Mueller
2021-08-01 13:42 ` Ulrich Mueller
2021-08-02 12:47 ` Ulrich Mueller
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=9D494357-A100-4E3C-88F7-FFEE98AF4A3A@gentoo.org \
--to=sam@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