Gentoo Archives: gentoo-pms

From: Zac Medico <zmedico@g.o>
To: gentoo-pms@l.g.o
Subject: Re: [gentoo-pms] EAPI specification in ebuilds
Date: Wed, 11 Apr 2012 18:22:52
In Reply to: Re: [gentoo-pms] EAPI specification in ebuilds by David Leverton
On 04/11/2012 11:02 AM, David Leverton wrote:
> 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.
The spec says "The package manager may optionally determine the \t{EAPI} of an ebuild by parsing it", which implies that you can implement a "pretend" mode that doesn't really determine the EAPI by parsing it, but parses it anyway and uses the result to generate deprecation warnings. A "pretend" mode like this is useful for initial deployment, in order to warn people with non-conformant ebuilds that are outside of the main tree. -- Thanks, Zac