| 1 |
Dnia 2013-09-12, o godz. 10:20:18 |
| 2 |
Patrick McLean <chutzpah@g.o> napisał(a): |
| 3 |
|
| 4 |
> On Thu, 12 Sep 2013 10:49:00 +0200 |
| 5 |
> Michał Górny <mgorny@g.o> wrote: |
| 6 |
> |
| 7 |
> > Anyone has a better idea? |
| 8 |
> > |
| 9 |
> |
| 10 |
> You could make sure that python-exec:2 is marked ~arch and in the |
| 11 |
> eclass check the version installed and switch according to that. For |
| 12 |
> stable users everything will stay the same, and for ~arch users all new |
| 13 |
> installs/upgrades will be switched to the new system. This will even |
| 14 |
> work if we want to mask it for a bit, so developers can test before |
| 15 |
> letting it into ~arch. |
| 16 |
|
| 17 |
Ok, it's ready for testing on python-script-location-r2 branch. |
| 18 |
|
| 19 |
https://bitbucket.org/mgorny/gx86-working-tree/commits/branch/python-script-location-r2 |
| 20 |
|
| 21 |
-- |
| 22 |
Best regards, |
| 23 |
Michał Górny |
Archives