On Mon, 10 Apr 2017 16:01:55 -0400 "William L. Thomson Jr." <wlt...@o-sinc.com> wrote:
> You still have > adding new, and the end user experience. You're running ~arch, I recall. This means adding new is slow for arch users. But it also means there's a clear line in the sand when something can be stabilized. ~arch is not great here, but that's why arch exists: ~arch is the buffer zone where the horrors are supposed to be exorcised. But as annoying as "oh, doesn't support new target yet" is, its much less annoying than "oh, it says it supports the new target, but actually doesn't, and now I have portage screaming at me to toggle use flags while I report this, and then some poor gentoo developer is going to have to recursively find all the broken dependents and remove their use flags" Its the same hell of keywording. Its much easier to *add* new keywords/useflags as repoman can trivially tell you if you made any mistakes, because repoman can only see how your package is, and how your dependencies are. *removing* useflags/keywords is much messier, because repoman can't tell you what you broke. Not without doing a full tree check, which takes 30 minutes+ on my hardware. Hence, that's the sort of problem I'm more inclined to throw grep at and then run it through an automated test PR to make sure I didn't break anything if I was really concerned.
pgpC6jElve2z7.pgp
Description: OpenPGP digital signature
