| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 20/12/12 12:27 PM, Ulrich Mueller wrote: |
| 5 |
> The FHS says: |
| 6 |
> |
| 7 |
> /var/cache is intended for cached data from applications. Such |
| 8 |
> data is locally generated as a result of time-consuming I/O or |
| 9 |
> calculation. The application must be able to regenerate or restore |
| 10 |
> the data. |
| 11 |
> |
| 12 |
> Now I wonder: After removal of e.g. the Portage tree from a system, |
| 13 |
> it is generally not possible to restore it. (It can be refetched, |
| 14 |
> but not to its previous state.) |
| 15 |
> |
| 16 |
> Same is true for distfiles, at least to some degree. They may have |
| 17 |
> vanished upstream or from mirrors. |
| 18 |
> |
| 19 |
> Maybe /var/lib would be a better choice? It would also take care |
| 20 |
> of the issue with fetch-restricted files. |
| 21 |
> |
| 22 |
|
| 23 |
I had asked more or less the same thing a few days ago. The cases |
| 24 |
where this would matter are few, however, and those users that need |
| 25 |
the state preserved could ensure it by including these specific paths |
| 26 |
in their backups and/or ensuring any cache-cleaner scripts (and AFAIK |
| 27 |
there aren't any that wouldn't be custom-installed) do not remove them. |
| 28 |
-----BEGIN PGP SIGNATURE----- |
| 29 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 30 |
|
| 31 |
iF4EAREIAAYFAlDTUkgACgkQ2ugaI38ACPDgAwEAhFH3Jc8E56WfePr3W1396+Jk |
| 32 |
65q7X8eEwNAYr8eJLwQA/1Xi7E42004M3frMDCDDBVZeD1EYmKkvXA8POhQUZc36 |
| 33 |
=JMod |
| 34 |
-----END PGP SIGNATURE----- |
Archives