1 |
Thomas Sachau <tommy@g.o> writes: |
2 |
|
3 |
> Since python-3* is currently useless and not required for any package, the dependency should by |
4 |
> default only pull in python-2* like this: |
5 |
> |
6 |
> =dev-lang/python-2* |
7 |
> |
8 |
> With that, the default way would not pull in a package, which is not needed or used. And if there |
9 |
> will be any package, which really requires python-3*, it simply requests it in (R)DEPEND of the |
10 |
> ebuild, which then would overwrite the default value of the eclass and pull in python-3*. |
11 |
|
12 |
That would not work. For example if package 'bar' supports both python-2 |
13 |
and python-3, your mechanism will only build in python-2 support. That |
14 |
is fine until package 'foo' comes along which uses 'bar' but also |
15 |
requires python-3 - thus not only must python-3 be pulled in as a result |
16 |
of foo's (R)DEPEND but also 'bar' must be rebuilt with python-3 support. |
17 |
|
18 |
This could be done by adding python2 and python3 USE flags to packages |
19 |
which support both and only have python2 enabled by default. Then 'foo' |
20 |
could have a conditional (R)DEPEMD on 'bar[python3]', but that would |
21 |
require the user to change the USE flags whereas the current system |
22 |
handles everything automatically. |