| 1 |
Am Montag, 17. Dezember 2012, 11:23:00 schrieb Diego Elio Pettenò: |
| 2 |
> On 17/12/2012 11:19, Tomáš Chvátal wrote: |
| 3 |
> > I've always myself override these defaults in make.conf to point for |
| 4 |
> > /var/portage/ (not /var/lib because I never bothered enough how to |
| 5 |
> > make world and config files to be put elsewhere :P). |
| 6 |
> |
| 7 |
> I would say let's work on that so that portage can keep them there. |
| 8 |
> Although I'm more for /var/cache/portage myself, as both distfiles and |
| 9 |
> tree can be re-generated. |
| 10 |
|
| 11 |
What about setups where portage tree is mounted via NFS to reduce traffic and |
| 12 |
disk space? |
| 13 |
|
| 14 |
FHS states[1] that /var/cache is *locally* generated. Which aould not be the |
| 15 |
case for such setups... |
| 16 |
|
| 17 |
I prefer /var as well, but I am not such if /var/cache would be the right |
| 18 |
place... |
| 19 |
|
| 20 |
|
| 21 |
[1] |
| 22 |
From FHS 2.3: |
| 23 |
"/var/cache is intended for cached data from applications. Such data is |
| 24 |
locally generated as a result of time-consuming I/O or calculation." |
| 25 |
|
| 26 |
-Marc |
| 27 |
-- |
| 28 |
0x35A64134 - 8AAC 5F46 83B4 DB70 8317 3723 296C 6CCA 35A6 4134 |
Archives