1 |
On 03/20/2010 02:56 AM, Jean-Marc Hengen wrote: |
2 |
> Duncan wrote: |
3 |
>> ... |
4 |
> |
5 |
> ++ - I can only add the saying "With freedom comes great responsibility.". |
6 |
> |
7 |
> Maybe the python herd could maintain a little status page which covers |
8 |
> informations like: |
9 |
> - Estimated python 3 compatibility in respect to the packages in the |
10 |
> main tree. |
11 |
|
12 |
That would be easy enough to generate from dependencies. Surely |
13 |
there are some dependencies that need to be updated, but that |
14 |
shouldn't be much work. For example, I've already updated the |
15 |
cracklib and libxml2 deps to indicate lack of python3 support. |
16 |
|
17 |
> - Recommendations if installing makes sense or not (e.g. package X gains |
18 |
> feature Y with python 3). |
19 |
> - Recommendations if setting python 3 as system engine makes already |
20 |
> sense or not. |
21 |
> This way gentoo can give its users the tools needed to make a good |
22 |
> decision if python 3 makes sense on his system. For me as a user I need |
23 |
> more time to study if an action makes sense than implementing said |
24 |
> action (e.g. locally masking python 3 - It would not be the first time |
25 |
> masking a package). If one isn't into python, it gets even more complicated. |
26 |
|
27 |
I would advise people to go ahead and install it as long as they can |
28 |
spare a little disk space and cpu time. Anybody who is tight on |
29 |
those resources should feel free to mask it (and the dependency |
30 |
resolver will certainly notify you if this is not feasible in your |
31 |
case). Honestly, I don't see a need for lots of data analysis here, |
32 |
but maybe some people just like that kind of thing. |
33 |
-- |
34 |
Thanks, |
35 |
Zac |