On 12 March 2012 20:10, Ciaran McCreesh <ciaran.mccre...@googlemail.com> wrote: > On Mon, 12 Mar 2012 20:49:22 +0100 > Ulrich Mueller <u...@gentoo.org> wrote: >> > That's already not the way things work, since different version >> > strings can be equal versions (and it's illegal to do this), >> > so it's not relevant to the discussion. >> >> This is a design flaw in our versioning system, and it can only occur >> in some corner cases where version components have leading zeros. > > You know, if we had GLEP 55, we could fix that. Although it's debatable > whether it's a flaw, since we're trying to match upstream version > formats where reasonably possible. > > -- > Ciaran McCreesh
I'm sure that it's been considered already, but what are the arguments against embedding the EAPI on a per-package (default) or per-version basis in metadata.xml. It IS metadata after all. Something like: <eapi>6</eapi> <!-- Default EAPI unless a versioned tag exists. --> <eapi version="=1.2.*">4</eapi> <eapi version="<1.2">3</eapi> Where the version attribute should presumably have the same syntax as versions in package.* already.
