Re: [gentoo-dev] [GLEP] Use EAPI-suffixed ebuilds (.ebuild-EAPI)

[Ciaran McCreesh]

On Tue, 18 Dec 2007 00:40:05 +0100
Thomas de Grenier de Latour <degrenier@×××××××××××.fr> wrote:
>  - metadata/cache: latest PMS i've found (2007/07/08 on dev.g.o/~spb)
> says it contains some "<category>/<package>-<version>" files. If a
> package manager assumes the "<version>" syntax is the one defined in
> the said PMS, and you extend this syntax, don't your fear it will
> trigger some bugs in said packages manager?

The package manager shouldn't be fishing around in metadata/cache. It
should only be doing direct lookups in there based upon ebuilds it
finds.

(latest PMS, by the way, is svn co http://svn.repogirl.net/pms)

>  - /var/db/pkg: this one is not specified anywhere afaik, but here
> too, putting some "<category>/<package>-<version>" with a new
> "<version>" syntax may trigger weird some packages manager bugs.
> Which would basically prevent forbid beetween several package
> managers which don't support the same EAPI set, or simply downgrading
> your favorite one.

You already can't downgrade package managers, so there's no regression
there.

>  - profiles/*: how will the various files there ("packages", etc.)
> ever be allowed to use some atoms which use an extended versioning
> syntax?

Currently profiles/* is limited to using EAPI-0 style things. You
can't, for example, use slot deps in profiles/. Removing this
restriction could be done in two ways (package-mask-1 etc, or
profiles/*/eapi).

-- 
Ciaran McCreesh