Gentoo Archives: gentoo-dev

From: Mart Raudsepp <leio@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/hachoir-parser: ChangeLog hachoir-parser-1.3.4.ebuild
Date: Sun, 12 Sep 2010 14:06:17
Message-Id: 1284300060.21256.11.camel@localhost
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/hachoir-parser: ChangeLog hachoir-parser-1.3.4.ebuild by "Petteri Räty"
On L, 2010-09-11 at 23:18 +0300, Petteri Räty wrote:
> On 09/11/2010 11:14 PM, Ryan Hill wrote: > > On Sat, 11 Sep 2010 22:10:51 +0300 > > Petteri Räty <betelgeuse@g.o> wrote: > > > >>> + > >>> +*hachoir-parser-1.3.4 (10 Sep 2010) > >>> + > >>> + 10 Sep 2010; Arfrever Frehtes Taifersar Arahesis <arfrever@g.o> > >>> + -hachoir-parser-1.3.3.ebuild, +hachoir-parser-1.3.4.ebuild: > >>> + Version bump. > >>> > >> > >> Deleting an older version is relevant so it should also be mentioned in > >> the ChangeLog message. > > > > It says -hachoir-parser-1.3.3.ebuild. What exactly do you think would be > > gained by adding "Remove old" in this case? > > > > Following your logic we should not write "Version bump" either (as > that's what happens by default when you add a new ebuild).
That's why I tend to spend the time to briefly summarize what the version bump actually improves for users by upstream (see my gstreamer bumps for example). I spend the time once, thousands of users get the information handily with emerge --changelog and the like, without digging into /usr/share/doc/*/NEWS* _after_ upgrading and already having had to do the work to decide if its important upgrade for them or not (in case of conservative upgrading). -- Mart Raudsepp

Replies