On Tue, May 16, 2017 at 12:20 PM, Michał Górny <mgo...@gentoo.org> wrote:
> Mike, > > I would really appreciate if you cared to follow procedures for eclass > changes. Most notably, if you at least bothered to either ping us *or* > sent the patch to the mailing list beforehand. > > This eclass is used by almost 6700 ebuilds. I am trying *hard* to commit > changes in large patchsets to reduce cache updates. Of course it is all > pointless if a random Mike Frysinger, developer on special rights, goes > ahead and commits whatever he wants to whatever eclasses he wants to > commit to, whatever time he pleases. > > Normally, I would revert it but I don't feel like causing third huge > cache update today. > Just out of curiosity, and for the curious: 1. How often do cache updates happen? 2. How long do they take? 3. Is there any downside to only having one such update running at a time and just skipping them if there's already an update pending? > > -- > Best regards, > Michał Górny >
