Ciaran McCreesh a écrit :
Kills the upgrade path completely. No good.
Lemme sum this up in layman's terms :
1) EAPI _has_ to be known before sourcing an ebuild. There's no way to
avoid that for various reasons, all 100% valid.
2) Putting the EAPI in the filename :
+ it solves 1)
+ it keeps backward compatibility because old PM won't recognize the
filenames
- it's not very "pretty"
3) Putting the EAPI in metadata.xml or in another external file
+ it solves 1)
+ it keeps pretty file names
- it breaks backwards compatibility
- (specific to metadata.xml) PM will have to learn to read XML (yuck)
That's about it, right?
--
Rémi Cardona
LRI, INRIA
[EMAIL PROTECTED]
[EMAIL PROTECTED]
--
gentoo-dev@lists.gentoo.org mailing list
