1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 19/12/12 08:56 AM, Diego Elio Pettenò wrote: |
5 |
> |
6 |
> That's why my suggestion is to use /var/cache: it makes it clear |
7 |
> that there is no definitive reason to back it up (as Justin said |
8 |
> there is an issue with distfiles you can't re-download but that's a |
9 |
> different story I'd say — maybe setting a default read-only distdir |
10 |
> for said packages might make sense, but I don't want to get there |
11 |
> at all). |
12 |
|
13 |
|
14 |
In terms of the fact that a current copy of the portage tree is always |
15 |
available, no it isn't necessary to back it up. However, if one isn't |
16 |
constantly maintaining their system via -uDN and doing say, updates on |
17 |
a monthly cycle (ie, production systems), then it is very useful to |
18 |
maintain the same portage tree snapshot as the system's last -uDN ... |
19 |
As such I would argue that it is worthwhile to back it up. |
20 |
Similarly, 'packages' should probably stay synchronized with the tree. |
21 |
|
22 |
So in terms of the above, would that mean /var/lib is a better fit? |
23 |
or would that mean /var/cache and it is up to the user to add their |
24 |
own backup of /var/cache/portage ? |
25 |
|
26 |
|
27 |
Distfiles, imo, are definitely just cache and can be discarded at any |
28 |
time. There are issues if one has a very old tree that some distfiles |
29 |
disappear from the mirrors (especially gentoo patchset tarballs) but |
30 |
such is life -- personally I'd like to see all such files stored on a |
31 |
dev's webspace in perpetuity so that SRC_URI could grab it from there |
32 |
after it's dropped from the mirrors. As for "special" distfiles |
33 |
(fetch-restricted etc), these would need to be downloaded manually |
34 |
anyways and if they are of value they should be backed up elsewhere |
35 |
(ie, not rely on the distfiles dir to keep them). |
36 |
|
37 |
|
38 |
Either of i.e. /var/cache/{distfiles,packages,portage} or |
39 |
/var/cache/portage/{distfiles,packages,tree} works for me; i can see |
40 |
the extra directory level keeping all portage bits together as looking |
41 |
nicer for the end user but meh. |
42 |
|
43 |
-----BEGIN PGP SIGNATURE----- |
44 |
Version: GnuPG v2.0.19 (GNU/Linux) |
45 |
|
46 |
iF4EAREIAAYFAlDRy8kACgkQ2ugaI38ACPAiLQD9HeENg+cPrkQcHhPF54h1AaPG |
47 |
hvTvaq4GaghMNXCKV7sBAKz8cKR6LD8grvuTnftWVJiRYYbhYM+HANTaE5xWs6f+ |
48 |
=WPmW |
49 |
-----END PGP SIGNATURE----- |