>>>>> On Tue, 18 Dec 2007, Ciaran McCreesh wrote: > | Possibility to extend the behaviour of inherit and add new global > | scope functions (as a result of not sourcing ebuilds with > | unsupported EAPI).
It seems to me that this will inconvenience the users, in order to solve a technical problem of the package manager. Is this really the right way to go? >> Making the file extension variable by adding "-<EAPI>" to it would, >> in my opinion, make the portage tree a bit less clean and not as >> elegant. +1 >> Wouldn't software (like editors determining file type by looking at >> what is after the ".") also need to be reworked to recognize a >> variable string after "-" at the end? > Yep, but that's not very difficult. And as a side effect, editors > could then provide EAPI aware highlighting. They can also do this if EAPI is set within the file. Ulrich -- [EMAIL PROTECTED] mailing list
