On Wednesday 16 February 2005 09:47, John Mylchreest wrote: > Morning All, > > Further to a previous thread where I said I would get a GLEP ready for > viewing, please find it here: > http://dev.gentoo.org/~johnm/files/glep33.txt > > All comments or criticisms are more than welcome. > Please let me know what your thoughts are.
Quoting GLEP: > An implication of this (if it wasn't clear from the elib description) > is that elibs cannot change their exported api dependant on the api (as some > eclass do for example). Sorry, I didn't parse the above... 'dependant on the api', what does that mean? > The next major release of portage will address this- the environment that > the ebuild was built in already contains the eclasses functions, as such the > env can be re-used rather then relying on the eclass. In other words, > binpkgs and installed ebuilds will no longer go and pull needed eclasses > from the tree, they'll use the 'saved' version of the eclass they were > built/merged with. How does that work with optional elib imports? Suppose you didn't import it when merging, and it was later removed from the tree, and you want to import it when unmerging. Also, I really don't like the idea of removing old-style eclasses from the tree, and requiring users to manually emerge eclass-compat to be able to unmerge perfectly valid old ebuilds. Firstly, we'll get a _lot_ of queries from users who don't know about eclass-compat, and they'll be quite upset. IMHO it's an ugly solution. Secondly, I don't see why it's needed. You say it's because we can't sign them easily. But after all eclass devs have moved everything to new eclasses, we can freeze eclass/* and never ever commit under it again. How hard would it be, then, to add an eclass/Manifest and sign the whole dir just once? Wouldn't it look the same as the new signed eclass/elib dirs? -- Dan Armak Gentoo Linux developer (KDE) Public GPG key: http://dev.gentoo.org/~danarmak/danarmak-gpg-public.key Fingerprint: DD70 DBF9 E3D4 6CB9 2FDD 0069 508D 9143 8D5F 8951
pgpv1dopLc7Nc.pgp
Description: PGP signature
