On 18-12-2007 00:39:38 +0000, Ciaran McCreesh wrote: > An EAPI is not limited to a numeric name. We could call the next EAPI > "cabbage" if we wanted to. There're already various experimental EAPIs > that don't use pure numbers (for example, "paludis-1"). > > (Sometimes I think the next EAPI *should* be called "cabbage", if only > because it'll help disabuse people of the notion that EAPIs are > orderable...)
While I feel there has been given little to no attention to what EAPI's really are and how they relate to each other, I prefer to go this route myself as well. The EAPI "name" should represent the feature(s) it adds. However, because "features" need not to include previous ones (why would they?), in the Prefix branch of Portage I implemented EAPI to be a space separated list. I merely did this because EAPI=1 ebuilds needed to be tagged as such in an EAPI="prefix" ebuild, and the features EAPI="prefix" adds are ortogonal on the features EAPI=0 or EAPI=1 ... provides. As a result I now have EAPI="prefix 1" ebuilds. Since you seem to argue here that EAPIs are not orderable, I get the impression you imply these "combinations" of EAPIs to be desirable. In that case, what would the extension of the ebuild be like? -- Fabian Groffen Gentoo on a different level -- [EMAIL PROTECTED] mailing list
