On 04/09/2017 07:15 PM, William L. Thomson Jr. wrote:
If the package failed, all that would need to be done kinda like now is a given variable modified in the ebuild. Just marking what ever it did not work with. As mentioned that could be done via my ebuild-batcher[1], though same functionality is easily replicated.
How do you plan to test a thousand packages against the new version of python, and then revision/stabilize all of the broken ones immediately? Or is the plan to just break everyone's systems, and ask them to report bugs for the things that stopped working?
I think what you will actually get as a result is that nobody will ever add a new version of python to the tree, because you've just made it a huge ordeal to do so.
