On Thu, 3 Nov 2011 01:33:38 +0100 "Andreas K. Huettel" <[email protected]> wrote:
> Dear all, > > > 2) I'd like to suggest that for changelogs that grow beyond a > > certain size (e.g. profiles/ChangeLog) the file is "rotated" > > similar to /var/log logfiles. I.e. the current file is renamed with > > a date extension and a new file is started. This has the benefit > > that the archived file is static and will never be retransmitted by > > rsync. > > to prevent that this becomes a victim of general ChangeLog > bikeshedding (we must rotate at a logical point, how could it be > automatized even if it is relevant for only a few files, then how do > we prevent epmty files...) I suggest the following procedure: > > In a week's time I personally, manually, will "rotate" all ChangeLog > files larger than 100k in the tree, by splitting them at > 31/12/2010-1/1/2011. The old entries file will in each case be named > ChangeLog-2010 in the same directory. (PMS: "A package directory may > contain other files or directories, whose purpose is not covered by > this specification.") Maybe we should keep old changelogs in a separate directory to decrease ebuilddir pollution? > The new ChangeLog file will be identical to the current ChangeLog > file except for being truncated at 1/1/2011. Maybe it'd be a good idea to add some kind of footer saying 'for further entries, please inquiry ChangeLog-2010 file'. -- Best regards, Michał Górny
signature.asc
Description: PGP signature
