1 |
Am 04.12.2010 21:23, schrieb Sebastian Pipping: |
2 |
> On 12/04/10 16:38, Thomas Sachau wrote: |
3 |
>>> Proposed new situation |
4 |
>>> ====================== |
5 |
>>> If I have a version of Python installed, it should be usable well. |
6 |
>>> So USE_PYTHON is derived from the list of all available Python slots. |
7 |
>>> Excluded are ABIs restricted by an ebuild, say by a line like |
8 |
>>> |
9 |
>>> RESTRICT_PYTHON_ABIS="3.*" |
10 |
>>> |
11 |
>>> for software that does not build with Python 3.x. |
12 |
>> |
13 |
>> I am against this proposal. I already masked python-3* on my system, because no package actually |
14 |
>> needs it, but the current behaviour installs completly useless code for those versions. |
15 |
> |
16 |
> Does it? I assume when you say you masked it you also mean that you |
17 |
> don't have Python 3.x installed? |
18 |
|
19 |
Exactly. |
20 |
|
21 |
> |
22 |
> Packages are installed against an ABI iff: |
23 |
> 1) The ABI is know to the python eclass - granted |
24 |
> 2) The build is not restricting the ABI |
25 |
> 3) The related version of python is actually installed |
26 |
> |
27 |
> Let's do this check: Please run this command: |
28 |
> |
29 |
> # equery f dev-python/pyinotify | fgrep site-packages |
30 |
> |
31 |
> If you don't have any Python 3.x installed you should see no files for it. |
32 |
> |
33 |
> |
34 |
>> Same would |
35 |
>> happen for all other, not active versions of python. |
36 |
> |
37 |
> See above, please re-check if that happens for you. |
38 |
> |
39 |
> |
40 |
>> One default active version should be enough, if |
41 |
>> i want more, i can select and set it. |
42 |
> |
43 |
> Please elaborate in more detail on that so I'm sure I reply to the |
44 |
> comment you actually had in mind. |
45 |
|
46 |
You only need one active python around, in this case, python-2.6. |
47 |
|
48 |
But you also get newer versions, like python-2.7 and python-3.1. While there is no big issue with |
49 |
python-2.7 (it is masked, until most packages depending on it are fixed), since when it gets stable, |
50 |
you can select it, update your depending packages, remove python-2.6 and be done with it. And as |
51 |
long, as you dont select python-2.7, you wont get anything into the site-packages dir of python-2.7. |
52 |
|
53 |
But with python-3*, it is different. You dont select it, it cannot even be the main or only python |
54 |
version around. But by default, all packages working with it additionally install their files for |
55 |
python-3*. This is some black magic behind the scene and invisible to the user. Imho nothing should |
56 |
be installed for anything else except the main selected version, unless you request it. So while you |
57 |
want to enable the installation for all versions currently installed, i request the other way round: |
58 |
Only install for the current main active version and nothing else by default. |
59 |
|
60 |
-- |
61 |
Thomas Sachau |
62 |
|
63 |
Gentoo Linux Developer |