On Wed, 13 Apr 2016 12:21:40 -0400 NP-Hardass <np-hard...@gentoo.org> wrote:
> >> Furthermore, there was a discussion a long time ago about how > >> functions shouldn't be called without an explicit inherit. That > >> means that even if the mate eclass uses gnome2, if I opt to call > >> gnome2 directly in the ebuild, I have to explicitly inherit it > >> (which mostly defeats the purpose of inheriting it in the mate > >> eclass). > > > > nah, this isnt true in your case: you can define mate.eclass' API > > to always include gnome2.eclass, making it ok to use gnome2 > > functions by inheriting only mate.eclass. this means you can never > > drop gnome2.eclass from mate.eclass though, which may not be > > desired > > > I'm unfamiliar with this. Do you have a reference that I can look at? not on top of my head, but some eclasses do that already (python-r1 for python-utils-r1 for example), and it seems natural that eclass author defines its API :)
