[gentoo-project] Call for agenda items - Coucil meeting 2020-11-08

[gentoo-project] Call for agenda items - Coucil meeting 2020-11-08

[Georgy Yakovlev]

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

In 2 two weeks from now, the Council will meet again. This is
the time to raise and prepare items that the Council should put on the
agenda to discuss or vote on.

Please respond to this message with agenda items. Do not hesitate to
repeat your agenda item here with a pointer if you previously
suggested one (since the last meeting).

The agenda for the meeting will be sent out on Sunday 2020-11-01.

Please reply to the gentoo-project list.
-- 
Georgy

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

Re: [gentoo-project] Call for agenda items - Coucil meeting 2020-11-08

[Michał Górny]

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

On Sun, 2020-10-25 at 17:17 -0700, Georgy Yakovlev wrote:
> In 2 two weeks from now, the Council will meet again. This is
> the time to raise and prepare items that the Council should put on the
> agenda to discuss or vote on.
> 
> Please respond to this message with agenda items. Do not hesitate to
> repeat your agenda item here with a pointer if you previously
> suggested one (since the last meeting).
> 
> The agenda for the meeting will be sent out on Sunday 2020-11-01.
> 
> Please reply to the gentoo-project list.

I would like to request the Council to vote on pre-approval of EAPI 8
items [1].

[1] https://wiki.gentoo.org/wiki/Future_EAPI/EAPI_8_tentative_features

-- 
Best regards,
Michał Górny


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

Re: [gentoo-project] Call for agenda items - Coucil meeting 2020-11-08

[Ulrich Mueller]

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

>>>>> On Mon, 26 Oct 2020, Michał Górny wrote:

> I would like to request the Council to vote on pre-approval of EAPI 8
> items [1].

For easy reference, please find the complete list below. The PMS team
will start working on the specification after pre-approval of features.

Of course, the finished PMS spec for EAPI 8 will be brought before the
Council again, for final approval.


1. New features

a) Selective fetch restriction
   Bug #371413 [2]

b) Install-time CBUILD dependencies (IDEPEND)
   Bug #660306 [3]


2. Enhancements of existing features

a) Variant of || ( ) with defined runtime behaviour
   Bug #489458 [4]
   - From original EAPI 6 (and 7) feature list

b) Pass --datarootdir to configure
   Bug #651958 [5]

c) Pass --disable-static to configure
   Bug #744871 [6]

d) Accumulate PROPERTIES and RESTRICT over eclasses and ebuilds
   Bug #701132 [7]

e) RESTRICT value for network-restricted tests
   Bug #553696 [8]

f) dosym -r to create symlinks relative to link location
   Bug #708360 [9]

g) Second optional argument for usev
   Bug #744868 [10]


3. Other changes

a) Less strict naming rules for files in updates directory
   Bug #692774 [11]

b) Bash 5.0
   Bug #636652 [12]

c) More consistent insopts/exeopts
   Bug #657580 [13]


4. Removals and bans

a) unpack: Remove support for 7-Zip, RAR, and LHA
    Bug #690968 [14]


> [1] https://wiki.gentoo.org/wiki/Future_EAPI/EAPI_8_tentative_features

[2] https://bugs.gentoo.org/371413
[3] https://bugs.gentoo.org/660306
[4] https://bugs.gentoo.org/489458
[5] https://bugs.gentoo.org/651958
[6] https://bugs.gentoo.org/744871
[7] https://bugs.gentoo.org/701132
[8] https://bugs.gentoo.org/553696
[9] https://bugs.gentoo.org/708360
[10] https://bugs.gentoo.org/744868
[11] https://bugs.gentoo.org/692774
[12] https://bugs.gentoo.org/636652
[13] https://bugs.gentoo.org/657580
[14] https://bugs.gentoo.org/690968

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

Re: [gentoo-project] Call for agenda items - Coucil meeting 2020-11-08

[Michał Górny]

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

On Mon, 2020-10-26 at 09:18 +0100, Ulrich Mueller wrote:
> > > > > > On Mon, 26 Oct 2020, Michał Górny wrote:
> > I would like to request the Council to vote on pre-approval of EAPI 8
> > items [1].
> 
> For easy reference, please find the complete list below. The PMS team
> will start working on the specification after pre-approval of features.

For even easier reference, a short summary of each item.

No real killer features this year.

> 1. New features
> 
> a) Selective fetch restriction
>    Bug #371413 [2]

Allow applying RESTRICT=fetch/mirror to a subset of package's SRC_URI.
 Useful e.g. for proprietary packages that fetch free patches.
The proposed syntax is the usual RESTRICT=... + in SRC_URI:

- mirror+http:// (mirror+ftp://...) to ignore mirror restriction
- fetch+http:// (...) to ignore fetch restriction

> b) Install-time CBUILD dependencies (IDEPEND)
>    Bug #660306 [3]

Allow specifying dependencies that are required for pkg_*inst
and preserved until pkg_*rm, installed into CBUILD root.  This is
a somewhat old request that used to be worked around via RDEPEND, except
that this hack does not work for cross.

We have found no use case for 'CHOST IDEPEND', so only one dep type
here.

> 2. Enhancements of existing features
> 
> a) Variant of || ( ) with defined runtime behaviour
>    Bug #489458 [4]
>    - From original EAPI 6 (and 7) feature list

This will probably be postponed again, as there is nobody willing
to implement it.

> b) Pass --datarootdir to configure
>    Bug #651958 [5]
> 
> c) Pass --disable-static to configure
>    Bug #744871 [6]

I don't think these two need an extra comment.

> 
> d) Accumulate PROPERTIES and RESTRICT over eclasses and ebuilds
>    Bug #701132 [7]

This is to improve consistency a little and reduce the confusion.  Some
developers have accidentally overwritten RESTRICT, thinking it was
accumulated like IUSE or *DEPEND.

> e) RESTRICT value for network-restricted tests
>    Bug #553696 [8]

The new value indicates that the package's tests have no other issues
except for Internet access.  For the majority of our users, this will be
equivalent to RESTRICT=test; except that some developers will be able
to disable this and run the tests, effectively also disabling network-
sandbox for src_test().  The rationale is that bad tests are better than
no tests ;-).

> f) dosym -r to create symlinks relative to link location
>    Bug #708360 [9]

An easier way to create relative symlinks, without having to count all
the '../'s yourself.

> g) Second optional argument for usev
>    Bug #744868 [10]

This fills the gap between usev and usex.  'usev a b' is equivalent
to 'usex a b ""', i.e. output 'b' if true and empty string otherwise. 

Note that 'usex a b' outputs 'no' if false which is sometimes desirable,
sometimes confusing but changing it today would be more confusing.

> 3. Other changes
> 
> a) Less strict naming rules for files in updates directory
>    Bug #692774 [11]

PMS requires the current quarterly scheme but for no real reason (we do
not require the files to be processed in a specific order).  We would
like to allow any names going forward, so that years from now, when we
require EAPI 8 for profiles, we would eventually be able to change
update file naming to a scheme optimal for the time.

> b) Bash 5.0
>    Bug #636652 [12]

The usual deal, accounting for the current stable.

> 
> c) More consistent insopts/exeopts
>    Bug #657580 [13]

We seem to have a historical mess over which functions respect *opts,
and which do not.  The goal is to clear it up by making insopts apply
only to doins/newins, and exeopts only to doexe/newexe.

In other words, doconfd, doenvd, doheader, doinitd will no longer be
affected by insopts/exeopts and instead reliably use the standard mode
for the directory in question.  If someone really needed to do something
different, doins/doexe will still be available.

> 4. Removals and bans
> 
> a) unpack: Remove support for 7-Zip, RAR, and LHA
>     Bug #690968 [14]

These are barely used, and PMS-specified tools for LHA and RAR are non-
free.  It's better to maintain them in unpacker.eclass, so that we can
switch to free and maintained tools (e.g. 7-Zip) easily.

> 
> 
> > [1] https://wiki.gentoo.org/wiki/Future_EAPI/EAPI_8_tentative_features
> 
> [2] https://bugs.gentoo.org/371413
> [3] https://bugs.gentoo.org/660306
> [4] https://bugs.gentoo.org/489458
> [5] https://bugs.gentoo.org/651958
> [6] https://bugs.gentoo.org/744871
> [7] https://bugs.gentoo.org/701132
> [8] https://bugs.gentoo.org/553696
> [9] https://bugs.gentoo.org/708360
> [10] https://bugs.gentoo.org/744868
> [11] https://bugs.gentoo.org/692774
> [12] https://bugs.gentoo.org/636652
> [13] https://bugs.gentoo.org/657580
> [14] https://bugs.gentoo.org/690968

-- 
Best regards,
Michał Górny


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

Re: [gentoo-project] Call for agenda items - Coucil meeting 2020-11-08

[Ulrich Mueller]

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

>>>>> On Mon, 26 Oct 2020, Ulrich Mueller wrote:

> For easy reference, please find the complete list below. The PMS team
> will start working on the specification after pre-approval of features.

After discussion in #gentoo-council, we add another ban to the list:

> 4. Removals and bans

b) Ban useq, hasq, and hasv functions 
   Bug #199722 [15]

As for the rationale, functions useq and hasq are deprecated since at
least 2011. In the Gentoo repo, hasq is no longer used since 2011.
useq is no longer used since March 2020 (in one single package, all
other uses are gone since 2011).

hasv isn't deprecated, but was _never_ used in the Gentoo repo. Also,
its arguments would become inconsistent with usev, because the latter
function will gain an optional second argument in EAPI 8 (item 2g).

Please speak up if you can come up with a possible use case for hasv,
but bear in mind that has&&echo is a trivial replacement.

Ulrich

[15] https://bugs.gentoo.org/199722

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

Re: [gentoo-project] Call for agenda items - Coucil meeting 2020-11-08

[Ulrich Mueller]

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

>>>>> On Mon, 26 Oct 2020, Ulrich Mueller wrote:

> For easy reference, please find the complete list below. The PMS team
> will start working on the specification after pre-approval of features.

And another last-minute addition:

> 3. Other changes

d) Default src_prepare accepts only file names in PATCHES
   Bug #752486 [16]

This is a tiny change. Currently, the implementation allows "clever"
uses like:

   PATCHES=( -d /path/to/patch -p0 -R foo.patch bar.patch )

This is at least confusing, and not the intended use. Ebuilds that need
to apply non-standard patches should add a src_prepare function with
explicit eapply calls.

We fix this by adding a "--" separator to the eapply call, so that it is
clear that all elements of PATCHES are file names.

Ulrich

[16] https://bugs.gentoo.org/752486

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

[gentoo-project] Coucil meeting 2020-11-08

[Georgy Yakovlev]

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

The next Council meeting will be on Sunday 2020-11-08, 19:00 UTC
in the #gentoo-council channel on Freenode.

Agenda:

1. Roll call
2. Vote on EAPI 8 proposals [1][2] + last minute addition[3]
3. Open bugs with Council participation [4]
4. Open floor

[1] https://wiki.gentoo.org/wiki/Future_EAPI/EAPI_8_tentative_features
[2] https://archives.gentoo.org/gentoo-project/message/57a0eef028a9c573b367013e9898efe5
[3] https://archives.gentoo.org/gentoo-project/message/6be2ac89864493a7e5b09a6700641d35
[4] https://wiki.gentoo.org/wiki/Project:Council#Open_bugs_with_Council_participation

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