Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
Zac Medico wrote:
> Since the EAPI parsing behavior is optional for older EAPIs, package
> managers can simply trigger a warning when they detect non-conformant
> ebuilds in the wild, and eventually make it fatal after the community
> has had sufficient warning.
Just to be clear, do you mean "if the PM doesn't detect an EAPI
assignment during parsing but the EAPI is non-0 after generating the
metadata, warn"? ยน Or something else?
[1] As opposed to the already-decided "if the PM detects an EAPI line
during parsing but the EAPI is something else after generating the
metadata, fail" rule.
|
|
