Ühel kenal päeval, E, 10.04.2017 kell 16:17, kirjutas William L. Thomson Jr.: > On Mon, 10 Apr 2017 16:01:55 -0400 > "William L. Thomson Jr." <wlt...@o-sinc.com> wrote: > > > > 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. > > What about dependencies? Their slots must be increased as well right? > > In fact that effects removal. You cannot remove an old version if any > depend on that slot specifically.
The USE dep requirement on the old python target will go away with the removal of it in eclass and I don't know what slots have to do with it. This circles back to first gathering the basic knowledge of how these things work right now and why, even if I don't necessarily agree with the way this was pointed out. > Rather in Java's case. If an older is removed, the ebuild does not > need > to be modified ever.... Nor if a new one is added unless it breaks. Nor does in python, it's just a janitorial process to reduce the ebuilds by 2 bytes or something. One which can be scripted and rather easily pushed thanks to not CVS anymore.
