1 |
> On Jul 11, 2018, at 4:43 PM, Rich Freeman <rich0@g.o> wrote: |
2 |
> |
3 |
>> On Wed, Jul 11, 2018 at 4:34 PM Richard Yao <ryao@g.o> wrote: |
4 |
>> |
5 |
>> On my system, /usr/portage is a separate mountpoint. There is no need to have on,h top level directories be separate mountpoints. |
6 |
> |
7 |
> It makes sense to follow FHS. Sure, I can work around poor designs by |
8 |
> sticking mount points all over the place, or manually setting my |
9 |
> config to put stuff in sane locations. It makes more sense to put all |
10 |
> the volatile stuff in /var, than to mix it up all over the place and |
11 |
> get users to set up separate mountpoints to make up for it. |
12 |
|
13 |
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. |
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 |
> If somebody is doing a new Gentoo install, why would they want to put |
18 |
> the repository in /usr, and nest a few GB of distfiles inside of the |
19 |
> repo? Why should that be the place we direct them? There is no |
20 |
> history for them. A brand new install should put things in the most |
21 |
> logical place. |
22 |
> |
23 |
> By all means let existing users decide whether to move stuff. I'm |
24 |
> sure we have plenty of users with make.conf in /etc/. |
25 |
> |
26 |
> -- |
27 |
> Rich |
28 |
> |