| 1 |
On Вск, 2006-01-01 at 21:35 +0100, Francesco Riosa wrote: |
| 2 |
> We have currently 10371 ChangeLog files, > 25 MB totally . |
| 3 |
> 1365 == 13% with size >= 4096 B, 12 MB totally |
| 4 |
> |
| 5 |
> rsync from "emerge --sync" has "--whole-file" between its options, that |
| 6 |
> mean transfer the whole file if changed. |
| 7 |
|
| 8 |
> 2) "rotate" Changelogs, keeping only the last changes, until a size |
| 9 |
> of 4000 or [choose a preferred size here] bytes. |
| 10 |
> This would save only about 7Mb of data (max size < 4096). |
| 11 |
|
| 12 |
ChangeLog is the only source of information on upgrade reasons and IMO |
| 13 |
users are interested only in recent information there. Another |
| 14 |
suggestion is to combine rotate like and exclude list solutions. |
| 15 |
|
| 16 |
When ChangeLog size reaches above maximum allowed size echangelog should |
| 17 |
create ChangeLog.old file and copy tail of ChangeLog there, in order to |
| 18 |
keep ChangeLog size. Then using excludes list one may drop really old |
| 19 |
entries in ChangeLog.old, whereas keeping recent information in portage |
| 20 |
tree. |
| 21 |
|
| 22 |
Peter. |
Archives