| 1 |
Ühel kenal päeval, E, 10.04.2017 kell 15:38, kirjutas William L. |
| 2 |
Thomson Jr.: |
| 3 |
> On Mon, 10 Apr 2017 21:57:10 +0300 |
| 4 |
> Mart Raudsepp <leio@g.o> wrote: |
| 5 |
> |
| 6 |
> > Ühel kenal päeval, E, 10.04.2017 kell 14:44, kirjutas William L. |
| 7 |
> > Thomson Jr.: |
| 8 |
> > > Again go modify a few hundred python packages to remove say 3.4. |
| 9 |
> > > I |
| 10 |
> > > think about 10-20 ebuilds in. You will be scripting and looking |
| 11 |
> > > for |
| 12 |
> > > another way.... |
| 13 |
> > |
| 14 |
> > No, for that you simple remove python3_4 from _PYTHON_ALL_IMPLS in |
| 15 |
> > python-utils-r1.eclass and call it a day. Some other day you might |
| 16 |
> > make a mass commit to remove 3_4 from PYTHON_COMPAT of all in-tree |
| 17 |
> > ebuilds, but that's just janitorial and no other effect. |
| 18 |
> |
| 19 |
> Ebuilds still must be touched right? Even if just for house cleaning. |
| 20 |
> That is some 1600+ ebuilds right? What about when a new version is |
| 21 |
> added? Re-touch all those same ebuilds right? |
| 22 |
|
| 23 |
After testing they actually work with the new version, instead of |
| 24 |
throwing known breakages onto ~arch users. |
| 25 |
|
| 26 |
> Am I missing something? |
| 27 |
|
| 28 |
You are missing the fact that this is pure janitorial in case of |
| 29 |
removal of a python3 SLOT, which can be done with scripts in one big |
| 30 |
commit. The effective change is all done in one touch of some eclass |
| 31 |
and then any 3_4 in PYTHON_COMPAT just doesn't have any effect. So |
| 32 |
removal of old stuff is not a concern whatsoever. The janitorial part |
| 33 |
doesn't have to be done, but because there are scripts that can do it |
| 34 |
mostly automatically one evening, it can get done after it's sure it |
| 35 |
won't have to be re-added for some reason in the eclass. |
Archives