[gentoo-project] Council Meeting 2025-06-08: Call for agenda items

[gentoo-project] Council Meeting 2025-06-08: Call for agenda items

[Michał Górny]

[-- Attachment #1: Type: text/plain, Size: 548 bytes --]

Good news, everyone!

In two weeks, the Council will meet again.  Please reply to this message
via gentoo-project@ list, with any agenda items that you'd like to have
discussed.  If you have already suggested once since last meeting,
please reply with a pointer.

The agenda will be sent out next Sunday, on 2025-06-01.  The meeting
will take place on 2025-06-08 at 19:00Z [1], in #gentoo-council channel
on Libera.chat.

[1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20250608T19

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

Re: [gentoo-project] Council Meeting 2025-06-08: Call for agenda items

[Ulrich Müller]

[-- Attachment #1: Type: text/plain, Size: 2674 bytes --]

>>>>> On Sun, 25 May 2025, Michał Górny wrote:

> In two weeks, the Council will meet again.  Please reply to this message
> via gentoo-project@ list, with any agenda items that you'd like to have
> discussed.  If you have already suggested once since last meeting,
> please reply with a pointer.

Another EAPI 9 item, with two sub-items:

a. Sam has submitted another feature: use.stable and package.use.stable
files in profiles [1]. Preliminary wording of the spec is this:

| 5.2.11 use.stable and package.use.stable
|
| The use.stable and package.use.stable files may be used to override
| the default USE flags specified by make.defaults. They only apply to
| packages that are merged due to a stable keyword in the sense of
| section 7.3.3. Each line in use.stable contains a USE flag to enable;
| the -flag syntax indicates that the flag should be disabled.
| The package.use.stable file uses the same format as package.use.
| USE_EXPAND values may be enabled or disabled by using
| expand_name_value.
|
| Stable restrictions are applied exactly when the following condition
| holds: If every stable keyword in KEYWORDS were replaced with its
| tilde-prefixed counterpart (see section 7.3.3), then the resulting
| KEYWORDS setting would prevent installation of the package.
|
| If a flag appears in more than one of package.use, use.stable and
| package.use.stable, then package.use.stable takes precedence over
| package.use, which in turn takes precedence over use.stable.
|
| These files are supported in EAPIs as per table 5.4. They can be
| directories instead of regular files as per section 5.2.5.
|
| Table 5.4: Profile directory support for use.stable and
| package.use.stable
| ---------------------------------------------------------------------
| EAPI               Supports use.stable?  Supports package.use.stable?
| ---------------------------------------------------------------------
| 0,1,2,3,4,5,6,7,8  No                    No
| 9                  Yes                   Yes
| ---------------------------------------------------------------------

Motion: Accept use.stable and package.use.stable for EAPI 9.

b. There doesn't seem to be any visible progress on the "eclass
revisions" feature [2], therefore I'd like to drop it from the list
of EAPI 9 features, and either postpone to EAPI 10, or reject it
altogether.

Motion: Drop eclass revisions from EAPI 9.

After these two motions, I would consider the feature set of EAPI 9
to be complete, so we can start working on its implementation in
package managers.

[1] https://bugs.gentoo.org/955833
[2] https://bugs.gentoo.org/806592

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]