On Thu, 27 Dec 2007 23:26:27 +0100 Luca Barbato <[EMAIL PROTECTED]> wrote: > Marius Mauch wrote: > > Nope. EAPI (from my POV) defines the API that a package manager has > > to export to an ebuild/eclass. That includes syntax and semantics > > of exported and expected functions and variables (IOW the content > > of ebuilds/eclasses), but does not contain naming and versioning > > rules (as those impact cross-package relationships). > > This restricted definition is ok for everybody?
The restricted definition is certainly OK, but I'm not convinced that the restriction is necessary. There's no particular reason that new version formats can't be introduced in a new EAPI so long as the version strings don't appear in ebuilds using older EAPIs or in profiles. Ditto for naming rules. -- Ciaran McCreesh
signature.asc
Description: PGP signature
