> Mike Frysinger писал 2012-05-25 19:42:
> > On Thursday 24 May 2012 23:47:23 Ryan Hill wrote:
> >> Is there any sane way to handle sub-eclasses? eg. foo-base inherits
> >> foo-functions.
> >
> > i was thinking of extending the metadata to handle this. did you
> > have any
> > specific ideas in mind ? i can see inheriting say distutils should
> > not require
> > people to also inherit python eclasses ...
>
> May we can use eclass dep graph?

no ... that sort of defeats the whole reason that drove this work. we don't
want the mere fact that one eclass inherits another to imply that it's part of
that eclasses guaranteed API. a lot of eclasses inherit eutils, but i don't
think any of them should be guaranteeing that inherit which means ebuilds need
to include it themselves if they use functions from it (like epatch).
there are a cases with split up or hierarchical eclasses (java, mysql, qt,
php, python, xorg come to mind) where the entry point might vary, but they all
share core eclasses that largely should not be inherited by the end ebuild.
maybe a new eclass-level keyword @INHERITED-API ? it takes a space delimited
list of eclasses that are guaranteed by the API. so in distutils.eclass, we'd
add:
# @INHERITED-API: python
and repoman would use this to build a tree of implicit funcs to allow w/out a
direct inherit.
-mike