On Wed, 13 Apr 2016 08:55:56 -0400 NP-Hardass <np-hard...@gentoo.org> wrote: [...] > The idea was partly due to consistency. Rather than calling mate_this > gnome2_that, it'd provide one namespace. Additionally as mentioned in > my initial email, since GNOME and MATE aren't always in synch, if the > gnome2 eclass chooses to change something, and it's better that mate > eclass stays with what we have, all I have to do is fill in the stub, > and all ebuilds retain their current implementation. Otherwise, I'd > have to mass edit all ebuilds to replace the offending gnome2_ with > mate_.
yep, makes sense > 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 > This has an > added bonus, which is that the gnome2 eclass inherits gnome.org, so I > have to make sure to re-inherit mate-desktop.org whenever gnome2 is > (re)inherited to prevent all of variables like SRC_URI from being > overwritten. Hope that I'm conveying that logic adequately. ok, maybe you could add a comment that no ebuild should inherit both gnome2 & mate eclasses then
