On Fri, 15 May 2009 21:06:13 +0100 Steven J Long <[email protected]> wrote: > > Before an ebuild has had its metadata generated, its EAPI is > > unknown. At this point, the package manager assumes EAPI 0. > > > With the format restriction, that everyone last year seemed happy > with, apart from the few pushing GLEP-55, this isn't an issue.
The format restriction hasn't been agreed upon, and doesn't solve the whole problem anyway. > If you have a use-case that actually requires more in a version > specifier for upstream software, please present it and explain how it > cannot be represented with the above. Go and look at all the ebuilds using MY_PV style hacks. Group these into "necessary because upstream are being silly" and "we're only doing this because of some utterly arbitrary rules imposed in the early days of Gentoo". Most are in the second camp. > In passing, I must express bewildered amusement at the idea of a > format with an unlimited amount of extensions. Not what's being proposed. We're proposing giving each format its own file extension. -- Ciaran McCreesh
signature.asc
Description: PGP signature
