1 |
On 12/03/2010 07:05 AM, Michał Górny wrote: |
2 |
> On Fri, 03 Dec 2010 11:35:14 +0100 |
3 |
> Sebastian Pipping <sping@g.o> wrote: |
4 |
> |
5 |
>> to better communicate USE_PYTHON we could use: |
6 |
> |
7 |
> The first question that comes into my mind is -- why do we need |
8 |
> to communicate that? I think that USE_PYTHON is a pretty specific |
9 |
> variable which should be used only if specially required (i.e. to keep |
10 |
> multiple Python versions ready for use). |
11 |
|
12 |
I tend to agree. For a user who doesn't actually USE python, but just |
13 |
has it installed because half of the rest of the system doesn't work |
14 |
without it, python is just another dependency. If a package only works |
15 |
with python v1.2, then it should depend on the appropriate slot/etc. |
16 |
|
17 |
If a user actually USES python, then they should have a mechanism to |
18 |
tell the system what versions of python to keep around. If you could |
19 |
put slots in the world file that might do the trick, but this variable |
20 |
seems like a reasonable way to do it as well. |
21 |
|
22 |
> |
23 |
> What needs to be fixed IMO is the default value of that variable. |
24 |
> If you already disabled switching the active Python version by default, |
25 |
> you should also make the Python eclass base its' USE_PYTHON defaults |
26 |
> on the active Python version. |
27 |
|
28 |
I tend to agree here as well. The distro should manage the version used |
29 |
for distro packages. Maybe a user wants to do cutting-edge development |
30 |
work in python-v12. The system should still use a sane version of |
31 |
python to run portage/etc, unless the user specifically tells it to do |
32 |
otherwise. |
33 |
|
34 |
Rather than hard-coding this in every package a distro-wide default |
35 |
probably makes sense. When new versions of python are deemed acceptable |
36 |
for distro-wide use the default can be updated. |
37 |
|
38 |
Gentoo has to work reasonably well without having to micro-manage python |
39 |
versions. Users shouldn't have to figure out what version of python |
40 |
they want to run to do an install. |
41 |
|
42 |
Rich |