| 1 |
On Fri, Mar 05, 2010 at 04:19:36PM -0800, Zac Medico wrote: |
| 2 |
> No, it won't. To prove it, I've just tested with a stable stage3 |
| 3 |
> containing portage-2.1.7.x. Here are the steps: |
| 4 |
> |
| 5 |
> 1) extract stable stage3 and chroot into it |
| 6 |
> 2) mkdir /etc/portage && echo "dev-lang/python ~*" >> |
| 7 |
> /etc/portage/package.keywords |
| 8 |
> 3) Run `emerge -pu --deep=1 portage`: |
| 9 |
> These are the packages that would be merged, in order: |
| 10 |
> |
| 11 |
> Calculating dependencies... done! |
| 12 |
> [ebuild UD] sys-apps/sandbox-1.6-r2 [2.2] |
| 13 |
> [ebuild UD] app-shells/bash-4.0_p35 [4.0_p37] |
| 14 |
> [ebuild U ] dev-lang/python-2.6.4-r1 [2.6.4] |
| 15 |
> |
| 16 |
> If you try `emerge -puD world` then you will see |
| 17 |
> dev-lang/python-3.1.1-r1 pulled in by the unspecific dev-lang/python |
| 18 |
> atoms in the cracklib and libxml2 dependencies. However, in |
| 19 |
> portage-2.1.7.x (current stable), there is support for |
| 20 |
> pseudo-version-ranges in dependencies. This allows you use a |
| 21 |
> dependency like <dev-lang/python-3 in a package that doesn't support |
| 22 |
> python3, and that will prevent it from getting pulled into the |
| 23 |
|
| 24 |
According to this, we can fix all of the dependencies in the tree then |
| 25 |
stabilize python3 without having any issues, so I would vote for this |
| 26 |
route, because it still oinsures that the stable tree will work |
| 27 |
together. |
| 28 |
|
| 29 |
William |
Archives