| 1 |
On Mon, Jul 9, 2018 at 1:40 PM Ulrich Mueller <ulm@g.o> wrote: |
| 2 |
> |
| 3 |
> >>>>> On Mon, 9 Jul 2018, William Hubbs wrote: |
| 4 |
> |
| 5 |
> > is there a tracker for when the portage tree can be moved out of |
| 6 |
> > /usr/portage by default? |
| 7 |
> |
| 8 |
> > If not, what is the status of us being able to do this? |
| 9 |
> |
| 10 |
> Please remind me, what was the plan for the new location? |
| 11 |
> Somewhere under /var/db or /var/lib, IIRC? |
| 12 |
> |
| 13 |
|
| 14 |
I'd also consider /var/cache here as well. FHS specifically suggests |
| 15 |
using it for web caches and the like (let's set aside the issue with |
| 16 |
making that global), though for the most part it is more metadata |
| 17 |
caching. A key principle is that it can be wiped without loss of |
| 18 |
data, and I think that is generally true for the repository since it |
| 19 |
can be synced. |
| 20 |
|
| 21 |
Stuff in /var/lib can't be deleted without some kind of loss of |
| 22 |
application state. /var/db isn't in FHS, and I note that even mysql |
| 23 |
sticks its stuff in /var/lib. |
| 24 |
|
| 25 |
-- |
| 26 |
Rich |
Archives