| 1 |
On Thu, 2012-12-20 at 18:27 +0100, Ulrich Mueller wrote: |
| 2 |
> The FHS says: |
| 3 |
> |
| 4 |
> /var/cache is intended for cached data from applications. Such data |
| 5 |
> is locally generated as a result of time-consuming I/O or |
| 6 |
> calculation. The application must be able to regenerate or restore |
| 7 |
> the data. |
| 8 |
> |
| 9 |
> Now I wonder: After removal of e.g. the Portage tree from a system, it |
| 10 |
> is generally not possible to restore it. (It can be refetched, but not |
| 11 |
> to its previous state.) |
| 12 |
> |
| 13 |
> Same is true for distfiles, at least to some degree. They may have |
| 14 |
> vanished upstream or from mirrors. |
| 15 |
> |
| 16 |
> Maybe /var/lib would be a better choice? It would also take care of |
| 17 |
> the issue with fetch-restricted files. |
| 18 |
|
| 19 |
Due to fetch-restricted files, /var/lib does make sense for distfiles. |
| 20 |
And of course /var/lib should be used for the default personal overlay |
| 21 |
(currently in /usr/local/portage). |
| 22 |
|
| 23 |
But I think that the main portage and overlay checkouts are already |
| 24 |
cache-like in the sense that any manual user changes are automatically |
| 25 |
overwritten by "emerge --sync" / "layman -S", which the users are |
| 26 |
supposed to run on a sufficiently regular basis. So /var/cache does seem |
| 27 |
like a reasonable place for them. |
Archives