| 1 |
On Mon, 10 Apr 2017 22:51:35 +0300 |
| 2 |
Mart Raudsepp <leio@g.o> wrote: |
| 3 |
> |
| 4 |
> After testing they actually work with the new version, instead of |
| 5 |
> throwing known breakages onto ~arch users. |
| 6 |
|
| 7 |
Ebuilds cannot use the new version till it is added to their |
| 8 |
PYTHON_COMPAT correct? |
| 9 |
|
| 10 |
There does not seem to be any way around touching all ebuilds when |
| 11 |
adding a new version. |
| 12 |
|
| 13 |
> > Am I missing something? |
| 14 |
> |
| 15 |
> You are missing the fact that this is pure janitorial in case of |
| 16 |
> removal of a python3 SLOT, which can be done with scripts in one big |
| 17 |
> commit. |
| 18 |
|
| 19 |
Ok I concede on removing older versions. Lets put old version aside. |
| 20 |
|
| 21 |
What about adding new? You still have to add the new version to |
| 22 |
PYTHON_COMPAT in each ebuild right? |
| 23 |
|
| 24 |
What about users? Do they need do anything if they have specific targets |
| 25 |
set? Or all should just use Wildcard and if in ~arch have 3-4+ pythons. |
| 26 |
|
| 27 |
Even if house cleaning, removing old is not an issue. You still have |
| 28 |
adding new, and the end user experience. |
| 29 |
|
| 30 |
-- |
| 31 |
William L. Thomson Jr. |
Archives