| 1 |
Ciaran McCreesh wrote: |
| 2 |
|
| 3 |
>On Fri, 10 Feb 2006 10:14:26 -0500 Chris Gianelloni |
| 4 |
><wolf31o2@g.o> wrote: |
| 5 |
>| Interesting, yes... but ebuilds are read by humans and it is necessary |
| 6 |
>| to be comprehensible a lot more than the Manifest files are. |
| 7 |
> |
| 8 |
>Sure. But the comparison would show whether or not it's going to make a |
| 9 |
>substantial difference. And if it does, there're other things that can |
| 10 |
>be done in the Manifest file that'll save a whole load of space too |
| 11 |
>(e.g. using $ to represent $PN, ! to represent files/, * to represent |
| 12 |
>ChangeLog and so on, since these characters aren't allowed in any |
| 13 |
>filename in the tree). |
| 14 |
> |
| 15 |
> |
| 16 |
> |
| 17 |
When you have thousands of small files (1-4 blocks), the space saved by |
| 18 |
removing all unnecessary whitespaces is minimal at best. |
| 19 |
Minimizing the number of files is another story. Unifying manifests with |
| 20 |
digest files will save a considerably amount of disk space. |
Archives