1 |
On Mon, 2012-12-10 at 01:52 +0100, Peter Stuge wrote: |
2 |
> Brian Dolbec wrote: |
3 |
> > > > remove entries in profiles/updates for tree-cleaned packages... |
4 |
> > > |
5 |
> > > What's the advantage of doing that? |
6 |
> > |
7 |
> > None |
8 |
> .. |
9 |
> > FYI... Currently there are updates files in profiles/updates/ |
10 |
> > dating back to 2004 |
11 |
> |
12 |
> Do they take up significant storage space or transfer time, compared |
13 |
> to the rest of the tree? |
14 |
> |
15 |
> If not, I can't think of a reason to remove them. |
16 |
> |
17 |
> |
18 |
> //Peter |
19 |
|
20 |
|
21 |
No, once they are downloaded, they don't change ever after the quarterly |
22 |
rollover which starts a new updates file. Nor do they take up |
23 |
significant storage space. They probably take up a higher percentage of |
24 |
your fs's inodes than % diskspace. |
25 |
|
26 |
But they do take time to process and verify every time emerge initiates |
27 |
a fixpackages call after every sync. That will save time more than it |
28 |
will space. |
29 |
|
30 |
Also, (taking it a bit to extremes ;) ) why would a new user with a 2 |
31 |
month old system and up-to-date tree want 8 year old update cruft |
32 |
lingering about their filesystem...taking time to check they've been |
33 |
processed? |
34 |
Do you? |
35 |
|
36 |
Let's just do an annual tree-cleaning and be done with them. |
37 |
-- |
38 |
Brian Dolbec <dolsen@g.o> |