>>>>> On Sun, 01 Aug 2021, Joshua Kinard wrote: > Let's go one further, though, and also add a mention of eapi, borrowing some > of the lingo from PMS, since the file is so prolific. See the attached > patch and let me know how the language looks.
> diff --git a/profiles/eapi/text.xml b/profiles/eapi/text.xml > new file mode 100644 > index 0000000..477ff24 > --- /dev/null > +++ b/profiles/eapi/text.xml > @@ -0,0 +1,18 @@ > +<?xml version="1.0"?> > +<guide self="profiles/eapi/"> > +<chapter> > +<title>Profiles <c>eapi</c> Files</title> > +<body> > + > +<p> > +An <c>eapi</c> file may be found in each profile directory. If present, this > +file specifies the EAPI to use when handling the directory. Otherwise, EAPI > 0 > +will be used instead. The contents of the file is a single line specifying > the > +numeric value of the supported EAPI. This file is not inherited by > <c>parent</c> > +nor in subdirectories. > +</p> > + > +</body> > +</chapter> > +</guide> > + This doesn't really belong there, because the "Profiles" chapter in the devmanual describes only the top-level profiles dir. So the wording from https://projects.gentoo.org/pms/8/pms.html#x1-320004.4 would apply (for the single profiles/eapi file): | The profiles directory may contain an \t{eapi} file. This file, if it | exists, must contain a single line with the name of an EAPI\@. This | specifies the EAPI to use when handling the profiles directory; a | package manager must not attempt to use any repository whose profiles | directory requires an EAPI it does not support. If no \t{eapi} file is | present, EAPI 0 shall be used. That said (and hard to believe), the devmanual currently doesn't describe the profile tree at all. Ulrich
signature.asc
Description: PGP signature
