On 04/09/2017 08:58 PM, William L. Thomson Jr. wrote:
I am NOT talking about stabilization at all. Simple reducing the burden of adding targets to ebuild, and users having to fiddle with targets as they come and go.
You are: when you find out that a stable package doesn't work with the next version of python, you have to figure out who the maintainer of that package is, and file a bug. Then, whenever he decides to fix it, you have to wait 30 days and file a stabilization request. Wait another few months for that to go through, and repeat however many times to fix every broken package.
You can either spend months/years doing that for all affected packages and every new version of python, or just commit the new version of python and let things break. Neither option is an improvement over the way things work now.
We have it your way for PHP packages, and I wish it was like Python/Ruby instead.
