On Mon, 10 Apr 2017 22:51:35 +0300 Mart Raudsepp <l...@gentoo.org> wrote: > > After testing they actually work with the new version, instead of > throwing known breakages onto ~arch users.
Ebuilds cannot use the new version till it is added to their PYTHON_COMPAT correct? There does not seem to be any way around touching all ebuilds when adding a new version. > > 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. Ok I concede on removing older versions. Lets put old version aside. What about adding new? You still have to add the new version to PYTHON_COMPAT in each ebuild right? What about users? Do they need do anything if they have specific targets set? Or all should just use Wildcard and if in ~arch have 3-4+ pythons. Even if house cleaning, removing old is not an issue. You still have adding new, and the end user experience. -- William L. Thomson Jr.
pgp_B43QIoO_4.pgp
Description: OpenPGP digital signature
