| 1 |
On 27-10-2011 03:28:33 +0000, Duncan wrote: |
| 2 |
> Fabian Groffen posted on Wed, 26 Oct 2011 23:00:22 +0200 as excerpted: |
| 3 |
> > On 26-10-2011 14:02:12 -0400, Rich Freeman wrote: |
| 4 |
> >> Well, if the desire to trim changelogs is generally agreed upon we |
| 5 |
> >> could always just count the lines and post a top-100 list or something |
| 6 |
> >> and let package maintainers go in and truncate things as seems bet to |
| 7 |
> >> them, with the guideline to keep the file intact up to a year before |
| 8 |
> >> the last commit. Eventually the files will be cleaned up. |
| 9 |
> > |
| 10 |
> > Don't you think it's much more sensical to remove all entries for |
| 11 |
> > ebuilds that are no longer in the tree then? |
| 12 |
> |
| 13 |
> 1) Given the irregularity of older entries, that could be difficult to |
| 14 |
> automate, tho it could be done going forward, once a log has been |
| 15 |
> manually trimmed once. |
| 16 |
|
| 17 |
a) take the set of available ebuilds |
| 18 |
b) forward scan through the ChangeLog for entries that affect any of the |
| 19 |
files |
| 20 |
c) copy those entries to a new ChangeLog |
| 21 |
|
| 22 |
Technically, you could do it on the machine that generates the rsync |
| 23 |
image, but that brings the problem that the Manifest file gets broken, |
| 24 |
hence an update + resign is necessary. E.g. all developer signs are |
| 25 |
replaced with a generic one. Same issue when generating the ChangeLogs |
| 26 |
from VCS with the current Manifests. |
| 27 |
|
| 28 |
Upside of doing it on rsync0 is that the full log is stored in |
| 29 |
sources.g.o, and the short/most relevant one is on rsync to the users. |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
Fabian Groffen |
| 34 |
Gentoo on a different level |
Archives