[gentoo-dev] Re: [Council] ChangeLog generation within Gentoo

[Fabian Groffen <grobian@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1525 bytes --]

On 27-10-2011 03:28:33 +0000, Duncan wrote:
> Fabian Groffen posted on Wed, 26 Oct 2011 23:00:22 +0200 as excerpted:
> > On 26-10-2011 14:02:12 -0400, Rich Freeman wrote:
> >> Well, if the desire to trim changelogs is generally agreed upon we
> >> could always just count the lines and post a top-100 list or something
> >> and let package maintainers go in and truncate things as seems bet to
> >> them, with the guideline to keep the file intact up to a year before
> >> the last commit.  Eventually the files will be cleaned up.
> > 
> > Don't you think it's much more sensical to remove all entries for
> > ebuilds that are no longer in the tree then?
> 
> 1) Given the irregularity of older entries, that could be difficult to 
> automate, tho it could be done going forward, once a log has been 
> manually trimmed once.

a) take the set of available ebuilds
b) forward scan through the ChangeLog for entries that affect any of the
   files
c) copy those entries to a new ChangeLog

Technically, you could do it on the machine that generates the rsync
image, but that brings the problem that the Manifest file gets broken,
hence an update + resign is necessary.  E.g. all developer signs are
replaced with a generic one.  Same issue when generating the ChangeLogs
from VCS with the current Manifests.

Upside of doing it on rsync0 is that the full log is stored in
sources.g.o, and the short/most relevant one is on rsync to the users.


-- 
Fabian Groffen
Gentoo on a different level

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]