On Tue, Aug 23, 2005 at 03:20:16PM +0200, Paul de Vrieze wrote: > To allow for this to work with current portage versions, perhaps it would > be an option to introduce a new extension for .ebuild scripts that use > it's functionality. That would allow all non-EAPI aware portage versions > to automatically ignore ebuilds that use this. not much for .ebuild? in the tree, personally. Why? Cause portage *should not* ignore those ebuilds. If the user wants to merge something that is a later ebuild api then they have, at least portage chucks an exception that the UI can wrap into "upgrade portage".
With what you're proposing, we instead get bugs about portage missing packages. > ps. I would also suggest requiring that EAPI can be retrieved by a simple > line by line parsing without using bash. (This allows for changing the > parsing system) No, that's yanks EAPI setting away from eclasses. Only time this would be required is if we move away from bash; if that occurs, then I'd think a new extension would be required. As is, shifting the 'template' loaded for an ebuild can be done in ebd's init_environ easy enough, so no reason to add the extra restrictions/changes. My 2 cents, at least ;) ~harring
pgpcTll4VxAEM.pgp
Description: PGP signature
