On Tue, 10 Jun 2008 10:33:34 +0200 Tiziano Müller <[EMAIL PROTECTED]> wrote: > Another ugly solution: Having the EAPI on a per-package (like > $portagedir/cat/package-1) or per-tree basis > ($portagedir/profiles/eapi) and start providing our tree as overlays > of more than one tree (will end up in a mess of dependencies, but it > would still be nice to specify the EAPI for a complete overlay > instead of having the name all the ebuilds like .eapi-X :-). > In addition: it wouldn't be possible to identify the EAPI of an > ebuild by just looking at it...
Kills the upgrade path completely. No good. -- Ciaran McCreesh
signature.asc
Description: PGP signature
