| 1 |
On Friday 25 May 2012 12:06:49 Alexey Shvetsov wrote: |
| 2 |
> Mike Frysinger писал 2012-05-25 19:42: |
| 3 |
> > On Thursday 24 May 2012 23:47:23 Ryan Hill wrote: |
| 4 |
> >> Is there any sane way to handle sub-eclasses? eg. foo-base inherits |
| 5 |
> >> foo-functions. |
| 6 |
> > |
| 7 |
> > i was thinking of extending the metadata to handle this. did you |
| 8 |
> > have any |
| 9 |
> > specific ideas in mind ? i can see inheriting say distutils should |
| 10 |
> > not require |
| 11 |
> > people to also inherit python eclasses ... |
| 12 |
> |
| 13 |
> May we can use eclass dep graph? |
| 14 |
|
| 15 |
no ... that sort of defeats the whole reason that drove this work. we don't |
| 16 |
want the mere fact that one eclass inherits another to imply that it's part of |
| 17 |
that eclasses guaranteed API. a lot of eclasses inherit eutils, but i don't |
| 18 |
think any of them should be guaranteeing that inherit which means ebuilds need |
| 19 |
to include it themselves if they use functions from it (like epatch). |
| 20 |
|
| 21 |
there are a cases with split up or hierarchical eclasses (java, mysql, qt, |
| 22 |
php, python, xorg come to mind) where the entry point might vary, but they all |
| 23 |
share core eclasses that largely should not be inherited by the end ebuild. |
| 24 |
|
| 25 |
maybe a new eclass-level keyword @INHERITED-API ? it takes a space delimited |
| 26 |
list of eclasses that are guaranteed by the API. so in distutils.eclass, we'd |
| 27 |
add: |
| 28 |
# @INHERITED-API: python |
| 29 |
|
| 30 |
and repoman would use this to build a tree of implicit funcs to allow w/out a |
| 31 |
direct inherit. |
| 32 |
-mike |
Archives