| 1 |
On Wed, 26 October 2011 Pacho Ramos <pacho@g.o> wrote: |
| 2 |
> El mié, 26-10-2011 a las 19:33 +0200, Bruno escribió: |
| 3 |
> > On Wed, 26 October 2011 Fabian Groffen <grobian@g.o> wrote: |
| 4 |
> > > However, this also allows to do all kinds of other actions to the |
| 5 |
> > > ChangeLog file, without actually adding an entry for the current change |
| 6 |
> > > being committed, as we've already seen in practice. |
| 7 |
> > > The Council would like to remind developers that it is still a |
| 8 |
> > > requirement that all actions are documented in the ChangeLog and that it |
| 9 |
> > > is hence the responsibility of the committing developer to make sure |
| 10 |
> > > this requirement is met. |
| 11 |
> > |
| 12 |
> > Is there some guideline about old entries in the ChangeLog? |
| 13 |
> > |
| 14 |
> > Over the past months ChangeLogs represent a big part of the tree, some |
| 15 |
> > of them being pretty big and going back many changes (hundreds of them) |
| 16 |
> > and years (even for actively maintained ebuilds). |
| 17 |
> > |
| 18 |
> > In order to not bloat the tree I would like to see old entries purged |
| 19 |
> > when there are more than 25-50 of them, especially if they refer to |
| 20 |
> > ebuilds gone since more than 3-6 months. |
| 21 |
> > Someone in need for long gone ebuild would have to look at VCS anyhow, so |
| 22 |
> > looking at ChangeLog/history over there would seem logical. |
| 23 |
> > |
| 24 |
> > On a compressed tree (squashfs) dropping all ChangeLogs reduces size from |
| 25 |
> > ~55MiB to around 35MiB which is quite a lot! |
| 26 |
> |
| 27 |
> Personally, I want to have full ChangeLog easily accessible, I remember |
| 28 |
> to need to look for really old entries when becoming a new maintainer |
| 29 |
> for an old package previously maintained by others. |
| 30 |
|
| 31 |
That seems fair, though I guess old ebuilds are needed as well in that case |
| 32 |
so the not-trimmed ChangeLog probably rather should be a feature of VCS GUI |
| 33 |
that would take all the changes to ChangeLog and assemble all the additions |
| 34 |
ignoring the removed lines, possibly connecting that to the history of the |
| 35 |
individual ebuilds. |
| 36 |
|
| 37 |
> What I don't know is the reasons for not compressing ChangeLogs by |
| 38 |
> default (well, I don't have a compressed tree, this probably won't be a |
| 39 |
> gain for people using it) |
| 40 |
|
| 41 |
Compressing the ChangeLogs in the tree would not help rsync as the beginning |
| 42 |
of the file changes and thus the compressed binary result is all but a stream |
| 43 |
to which data got appended. |
| 44 |
|
| 45 |
Bruno |
Archives