[gentoo-dev] Re: Deprecation of python_version(), python_mod_exists(), python_tkinter_exists(), distutils_python_version() and distutils_python_tkinter() in EAPI <=2

[Duncan <1i5t5.duncan@cox.net>]

Peter Hjalmarsson posted on Fri, 05 Mar 2010 10:54:23 +0100 as excerpted:

> I have start to question why should we care about overlays more then the
> actual portage tree?
> 
> Take for example the kernel or Xorg.
> They give themselves a period of time to clean up their own code (i.e.
> kernel-modules, xorg-drivers) and then they release it as stable and
> tell users/distributors to upgrade.
> They do not wait for nVidia/AMD/other out-of-tree drivers/modules to
> catch up.
> 
> Now if we say we have someone managing an overlay, and this person do
> miss this warning/die for half an year, then I would say they have nott
> done their homework and they are on their own. I do not see why we
> should wait unreasonable long periods of time because there may be
> someone broken somewhere.

While I didn't mention overlays in my earlier reply, that's exactly why I 
proposed four months each in warning and die, before removal altogether.  
That gives the once-per-quarter updaters a bit of extra time to catch it 
at each stage, and if they've not done so by four or even eight months 
out... waiting a full year, or two, or three... isn't necessarily going to 
help matters much.

Besides, if they're /that/ far behind the main tree, what sort of overlay 
maintainer are they anyway?  Hardly one that should be basing on Gentoo, 
which has always been a "rolling" distribution.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman