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