1 |
> * Even though python-2.3.2 requires portage-2.0.49-r16, I can't put a |
2 |
> dep in otherwise it may create a circular dependency. Probably the best |
3 |
> solution would be to have a pkg_setup check before it goes ahead. |
4 |
|
5 |
That might be acceptable. python and portage will always be present |
6 |
on a Gentoo system. It's a litle weird, but may benefit everyone in |
7 |
this situation. I'll get around to testing this soon. I'd prefer |
8 |
that portage be ~arch before you make python ~arch, as it'll cause |
9 |
headaches otherwise. The only reason I haven't yet is that it can |
10 |
break the GUI's for portage. I'll be notifing the authors to be |
11 |
sure that they are up to date, as soon as I have internet access |
12 |
again. It's down as I'm writing this email. |
13 |
|
14 |
> * Maybe we should think about using a non version specific directory for |
15 |
> Python modules to ease upgrade. |
16 |
|
17 |
I agree. |
18 |
|
19 |
--NJ |
20 |
|
21 |
-- |
22 |
gentoo-dev@g.o mailing list |