| 1 |
mån 2010-03-08 klockan 10:53 +0100 skrev Antoni Grzymala: |
| 2 |
|
| 3 |
> Sorry guys if I missed something crucial in this lengthy thread, but |
| 4 |
> from what I'm understanding: |
| 5 |
> |
| 6 |
> if python-3 goes stable (and unmasked): |
| 7 |
> |
| 8 |
> - it is a separate, slotted version |
| 9 |
> - it generally shouldn't get pulled in (current portage non-greedy |
| 10 |
> behaviour on slots) |
| 11 |
> - if it does get pulled in by, say, and old portage version, or a |
| 12 |
> package with badly defined deps, it shouldn't do any harm because it |
| 13 |
> will just sit quietly in its slot and old packages will still |
| 14 |
> compile/run against (already installed) python-2.x |
| 15 |
> |
| 16 |
> or not? |
| 17 |
> |
| 18 |
> PS. one thing I realize I may be missing is the /usr/bin/python symlink |
| 19 |
> and the /usr/bin/python-wrapper to which it points. Will the default |
| 20 |
> change to python31 upon python-3 installation? |
| 21 |
> |
| 22 |
> best, |
| 23 |
> |
| 24 |
|
| 25 |
AFAICS you are right (and that is also why I have a hard time |
| 26 |
understanding the flames here, are people so against fixing the deps in |
| 27 |
their packages and/or filing bugs and/or contacting devrel about those |
| 28 |
maintainers who refuse to fix their packages?). |
| 29 |
|
| 30 |
about your ps: pyhon-3 is absolutely harmless in its current form, and |
| 31 |
that is partly because it does not take over the role as the system |
| 32 |
python unless you do something stupid/uninformed. |
Archives