| 1 |
On 11/13/2018 01:21 AM, Zac Medico wrote: |
| 2 |
> |
| 3 |
> What's inherently wrong about nix having a file store under /nix? Is |
| 4 |
> this purely about FHS? |
| 5 |
> |
| 6 |
|
| 7 |
It goes against not only the FHS, but against our existing policies and |
| 8 |
common sense. There's no reason to expect that path to even be writable. |
| 9 |
And nix stores everything there, so if you have / mounted on a smaller |
| 10 |
partition with e.g. /home and /var mounted elsewhere, then it's going to |
| 11 |
fill the disk up with junk that emerge won't remove for you. |
| 12 |
|
| 13 |
But it's also just absurd how much trouble we go to to wind up right |
| 14 |
back where we started: |
| 15 |
|
| 16 |
* Spend years developing a FHS so that people can get the most out |
| 17 |
of their storage hardware and know where to find stuff on their |
| 18 |
computers. |
| 19 |
|
| 20 |
* Adopt a bunch of policies in Gentoo for where ebuilds should store |
| 21 |
things. |
| 22 |
|
| 23 |
* Add QA checks to ensure that packages abide by said policies. |
| 24 |
|
| 25 |
* Add package-manager-specific variables that sidestep the QA checks. |
| 26 |
|
| 27 |
* Begin adding exceptions to every package that puts things in the |
| 28 |
wrong place so that people don't see warnings about things being in |
| 29 |
the wrong place... |
| 30 |
|
| 31 |
All to achieve the end result, that nothing is where it's supposed to be |
| 32 |
and you can't plan anything. |
| 33 |
|
| 34 |
I think I'm just tired. I'll stop. |
Archives