On Wed, 2008-01-09 at 15:11 +0000, Ciaran McCreesh wrote: > Heck, most of the repoman messages people are moaning about are caused > by developers doing exactly this.
No, most of the ones we're complaining about have nothing to do with KEYWORDS, at all, and everything to do with changes to policy and such that have been enacted since the ebuild was last touched. See, repoman doesn't care if you're just making a KEYWORD change or if you're making coding changes to an ebuild. It still will fail if something fails a QA check, even if the failure is on an ebuild you're not touching. As such, it is a serious pain in the ass for architecture teams and developers who are *not* slacking when one particular architecture only has ebuilds that are ancient marked stable. It increases the support burden for *EVERYONE* else to keep this one architecture's stable tree as it currently sits. -- Chris Gianelloni Release Engineering Strategic Lead Alpha/AMD64/x86 Architecture Teams Games Developer
signature.asc
Description: This is a digitally signed message part
