1 |
> On Jul 11, 2018, at 6:23 PM, Michał Górny <mgorny@g.o> wrote: |
2 |
> |
3 |
> W dniu śro, 11.07.2018 o godzinie 18∶11 -0400, użytkownik Richard Yao |
4 |
> napisał: |
5 |
>>>> On Jul 11, 2018, at 4:43 PM, Rich Freeman <rich0@g.o> wrote: |
6 |
>>>> |
7 |
>>>> On Wed, Jul 11, 2018 at 4:34 PM Richard Yao <ryao@g.o> wrote: |
8 |
>>>> |
9 |
>>>> On my system, /usr/portage is a separate mountpoint. There is no need to have on,h top level directories be separate mountpoints. |
10 |
>>> |
11 |
>>> It makes sense to follow FHS. Sure, I can work around poor designs by |
12 |
>>> sticking mount points all over the place, or manually setting my |
13 |
>>> config to put stuff in sane locations. It makes more sense to put all |
14 |
>>> the volatile stuff in /var, than to mix it up all over the place and |
15 |
>>> get users to set up separate mountpoints to make up for it. |
16 |
>> |
17 |
>> 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. |
18 |
>> |
19 |
>> 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. |
20 |
>>> |
21 |
> |
22 |
> And we're back to the usual Gentoo argument of 'it was like this for |
23 |
> N years'. So FYI, something 'being there for ~15 years' doesn't make it |
24 |
> right. It only means that: |
25 |
> |
26 |
> a. Gentoo devs were wrong 15 years ago. |
27 |
> |
28 |
> b. Gentoo devs are still wrong today. |
29 |
> |
30 |
> c. Gentoo devs can't manage to make such a simple change because they're |
31 |
> too concerned about hurting somebody's feelings about a path. |
32 |
This does not answer my question. Is it really a FHS violation? The contents of /usr changes when doing updates using the system package manager. When not doing updates, it really is readonly and the FHS says that /usr is for readonly things. I do not see how it is different from anything else in /usr. |
33 |
|
34 |
I have been thinking that having it there was compliant for years and honestly, I don’t see how it is not complaint. Saying it is not compliant is not an explanation. |
35 |
> |
36 |
> -- |
37 |
> Best regards, |
38 |
> Michał Górny |