I can see the use for a category one, but I can see no point for a package-local one, if you're going to have it specific for one package, why not just put it in the ebuild, and have no eclass at all?
Actually I'd say the opposite: There is definitely a use for package-local eclasses, however I don't see the point for category-local eclasses (especially as that would very funny to get it working).
Example for package-local eclasses? Whenever you define a function in an ebuild that isn't version specific.
Marius -- [email protected] mailing list
