On 1.9.2011 13.51, Michał Górny wrote: > On Thu, 01 Sep 2011 13:44:47 +0300 > Petteri Räty <betelge...@gentoo.org> wrote: > >> On 1.9.2011 12.03, Michał Górny wrote: >>> Hello, >>> >>> A quick idea. Right now eclasses sometimes do API changes and start >>> yelling at users merging ebuilds using outdates APIs. This often >>> means users start filling bugs about outdated ebuilds requiring >>> maintainers either to ignore that or start updating old ebuilds >>> retroactively. >>> >>> Maybe we should add some kind of devqawarn() function to >>> eutils.eclass, which would trigger special QA warnings only when >>> ebuild is merged by a developer? This could be triggered e.g. by >>> some kind of voluntary make.conf setting. >>> >> >> What's wrong with eqawarn that's already provided by eutils? > > The first paragraph? >
Have Portage defaults so that users only see if them if they read the merge logs and then developer profiles can set the settings to log them? Regards, Petteri
