| 1 |
On Sun, 6 Dec 2015 20:03:19 +0100 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> Hi, |
| 5 |
> |
| 6 |
> Here's another patchset. Mostly fixups inspired by multilib-build.eclass |
| 7 |
> changes with a few little additions. |
| 8 |
> |
| 9 |
> Changes: |
| 10 |
> |
| 11 |
> 1. eclass-set variables are now read-only, |
| 12 |
> 2. 'unset -f' is used to unset temporary & local functions, |
| 13 |
> 3. implementations are reordered for sane order. |
| 14 |
> |
| 15 |
> I've tested this with a few dozen random distutils-r1, python-r1, |
| 16 |
> python-any-r1 and python-single-r1 packages. However, for |
| 17 |
> the implementation reorder a larger tinderbox run would be appreciated. |
| 18 |
> |
| 19 |
> As explained in the commit, the reorder may influence files installed by |
| 20 |
> a package, and implementation selected by python_setup(). This should |
| 21 |
> not cause issues for correctly written ebuilds, and should help us find |
| 22 |
> those that are not correctly written ;-). |
| 23 |
> |
| 24 |
> In other words, we're finally considering Python 3.x preferred over |
| 25 |
> Python 2.x. |
| 26 |
|
| 27 |
Merged now. |
| 28 |
|
| 29 |
-- |
| 30 |
Best regards, |
| 31 |
Michał Górny |
| 32 |
<http://dev.gentoo.org/~mgorny/> |
Archives