| 1 |
Am 06.06.2010 09:37, schrieb Michał Górny: |
| 2 |
> On Sun, 06 Jun 2010 04:19:28 +0200 |
| 3 |
> Sebastian Pipping <sping@g.o> wrote: |
| 4 |
> |
| 5 |
>> Thomas, |
| 6 |
>> |
| 7 |
>> |
| 8 |
>> On 06/06/10 04:01, Thomas Sachau wrote: |
| 9 |
>>> Since python-3* is currently useless and not required for any |
| 10 |
>>> package, the dependency should by default only pull in python-2* |
| 11 |
>>> like this: |
| 12 |
>>> |
| 13 |
>>> =dev-lang/python-2* |
| 14 |
>>> |
| 15 |
>>> With that, the default way would not pull in a package, which is |
| 16 |
>>> not needed or used. And if there will be any package, which really |
| 17 |
>>> requires python-3*, it simply requests it in (R)DEPEND of the |
| 18 |
>>> ebuild, which then would overwrite the default value of the eclass |
| 19 |
>>> and pull in python-3*. |
| 20 |
>> |
| 21 |
>> That's an interesting idea. |
| 22 |
> |
| 23 |
> It sounds quite pointless to me. Forcing the packages to assume they |
| 24 |
> don't support the newer version just because nothing requires it yet? |
| 25 |
|
| 26 |
This is not about forcing a python-2* dependency, it is just about setting a sane default. We still |
| 27 |
have many python related packages, which dont work with python-3, but i dont know of packages, which |
| 28 |
dont work with python-2. So a sane default would be to require python-2, when nothing else is set in |
| 29 |
the ebuild instead of assuming, that it works for every version including python-3. |
| 30 |
|
| 31 |
You can always overwrite this dependency in the ebuild, so you dont force anything. |
| 32 |
|
| 33 |
> |
| 34 |
>>> Are there any reasons to pull in a package, which is not requested |
| 35 |
>>> by the user, not required by any package and by default not used by |
| 36 |
>>> any package? |
| 37 |
>> |
| 38 |
>> That a question I haven't seen answered before, either. Arfrever? |
| 39 |
> |
| 40 |
> It _is_ requested by user. User requested upgrade of all dependant |
| 41 |
> packages, and here it goes. |
| 42 |
|
| 43 |
Before python-3 got introduced, packages, which only support python-2, did just inherit python or |
| 44 |
distutils eclass and did not depend on python, because this dependency was in the eclass. Now with |
| 45 |
the introduction of python-3, this dependency string will introduce python-3, also those packages |
| 46 |
where not tested with python-3 and probably wont work with it. |
| 47 |
|
| 48 |
As a user, i expect a world update to update/install all needed and required packages. python-3 is |
| 49 |
neither required, nor needed or used, it is a complete optional dependency and should be handled |
| 50 |
like that, see my other mail with a possible way to handle it. |
| 51 |
|
| 52 |
-- |
| 53 |
Thomas Sachau |
| 54 |
|
| 55 |
Gentoo Linux Developer |
Archives