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