В Вск, 12/09/2010 в 17:01 +0300, Mart Raudsepp пишет: > 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 <betelge...@gentoo.org> wrote: > > > > > >>> + > > >>> +*hachoir-parser-1.3.4 (10 Sep 2010) > > >>> + > > >>> + 10 Sep 2010; Arfrever Frehtes Taifersar Arahesis > > >>> <arfre...@gentoo.org> > > >>> + -hachoir-parser-1.3.3.ebuild, +hachoir-parser-1.3.4.ebuild: > > >>> + Version bump.
> 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). This ether should became common practice or it'll stay useless and even harmful. It's hard to anticipate upstream NEWS in our ChangeLogs since very few packages do this and as I see logic behind our ChangeLogs they are intended for changes in our package (ebuilds), not for upstream changes. At the same time this additional information makes our ChangeLogs harder to read and find out what was changed in ebuild and why. That said I think it's really useful to have this information with rsync but it's better come with different solution instead of utilizing package's ChangeLogs... -- Peter.
