Michael Orlitzky posted on Tue, 17 Nov 2015 17:45:49 -0500 as excerpted: > On 11/17/2015 05:09 PM, Michał Górny wrote: >> >> I have the pleasure to announce that portage-2.2.25 has just been >> committed and it comes with complete EAPI 6 support. This effectively >> means that from this moment forward Gentoo developers are permitted to >> commit EAPI 6 ebuilds to ~arch. > > Is it really safe to start committing ~arch ebuilds that don't work with > stable portage? Might not things get wonky for stable users who have a > few keyworded packages?
Gentoo has never really guaranteed the stability of a mostly-stable system with a few ~arch accept-keyworded packages as that's simply not a properly testable setup. All-stable is testable and pains are taken not to break it, tho of course bugs do happen on occasion. Similarly, ~arch is testable and known-broken ebuilds aren't to be committed, tho it's accepted as part of running ~arch that previously unknown breakage might happen from time to time. But there, the assumption is that people are running full-~arch, and individual ~arch packages aren't generally expected or tested to work on a generally arch- stable system, so people trying to run individual ~arch packages are accepting that they're generally not tested on arch-stable and may in fact be known to break it. Tho for EAPIs, PMs are supposed to mask packages in EAPIs they don't understand, so in theory at least, even EAPI-6 ~arch accept-keyworded packages shouldn't break systems with stable PMs, because the PMs should mask EAPI-6 ebuilds if they don't understand EAPI-6 yet. So it shouldn't be a problem, but if it is, it's still only a problem to the extent already written on the label for people accepting the risk of ~arch accept-keywording specific packages. -- 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
