Gentoo Archives: gentoo-dev

From: Rich Freeman <rich0@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: Remove eclass/ChangeLog
Date: Wed, 23 May 2012 16:30:57
In Reply to: Re: [gentoo-dev] Re: Remove eclass/ChangeLog by Samuli Suominen
On Wed, May 23, 2012 at 4:02 AM, Samuli Suominen <ssuominen@g.o> wrote:
> On 05/23/2012 05:36 AM, Ryan Hill wrote: >> One person doesn't do entries.  OMG let's remove it! >> > > absolutely because inconsitency renderess the file useless >
Well, for now the solution is to enforce following policy. For the future, perhaps the policy's time has ended. Sure, Changelogs can be handy, but they are increasingly redundant and scm comments have the potential to be far more useful. By all means require meaningful scm commit comments, but if Changelog files are holding us back either auto-generate them or ditch them. And, to add my own to cents to this chain about the only thing worse than failing to directly inherit an eclass dependency is to break the tree fixing the problem on personal initiative. When a dev messes up the solution is to talk to them or if necessary talk to devrel/QA - not to break end-user systems. Rich


Subject Author
Re: [gentoo-dev] Re: Remove eclass/ChangeLog "Michał Górny" <mgorny@g.o>