On Tue, Nov 17, 2015 at 3:37 PM, Raymond Jennings <shent...@gmail.com> wrote: > As a possibly relevant side note, I've observed how api changes are handled > in the linux kernel: > > You can change whatever you want if it's a good idea, but as part of proving > it, you have to be willing to take over the warranty for anything you break. > > So basically you change what you please ONLY if you also take the burden of > fixing everything that depended on what you screwed with. > > Is this how things are handled by gentoo as well? >
For the most part, yes, though sometimes changes are posted well in advance with the goal of getting everybody to pitch in. This is why a change like this was implemented with an EAPI change. There is no retroactive impact of the change, so nothing in the tree is affected. Developers just have to fix their ebuilds before they move to the new EAPI. -- Rich
