1 |
On Wed, Jul 11, 2018 at 6:11 PM Richard Yao <ryao@g.o> wrote: |
2 |
> |
3 |
> Is it a violation of the FHS? /usr is for readonly data and the portage tree is generally readonly, except when being updated. The same is true of everything else in /usr. |
4 |
> |
5 |
|
6 |
It is application metadata. It belongs in /var. No other packages |
7 |
write to /usr when they're doing internal updates. Obviously you need |
8 |
a writable /usr to actually install package changes, but that |
9 |
shouldn't be necessary just to sync the repository. |
10 |
|
11 |
I was asking around and it seems like most distros stick their |
12 |
repositories in /var/lib. I can't imagine that too many would have |
13 |
even considered sticking them in /usr. |
14 |
|
15 |
> I am confused as to how we only now realized it was a FHS violation when it has been there for ~15 years. I was under the impression that /usr was the correct place for it. |
16 |
|
17 |
It has certainly been pointed out in the past. Nothing was changed |
18 |
for the same reason that nothing will probably be changed this time - |
19 |
people don't like change and the people who know better just slowly |
20 |
patch around Gentoo's oddities. Somebody was just posting a manifesto |
21 |
about deploying more experimental technologies, and here we can't move |
22 |
a repository out of /usr. |
23 |
|
24 |
And if nothing else, can we at least move /usr/portage/distfiles |
25 |
someplace else? Surely you have to agree that this doesn't belong in |
26 |
usr, or nested in the middle of a repository? |
27 |
|
28 |
-- |
29 |
Rich |