From: Michael Orlitzky <mjo@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] install-qa-check.d: Support QA{,_STRICT}_INSTALL_PATHS variables (bug 670902)
Date: Tue, 13 Nov 2018 01:57:47 -0500 [thread overview]
Message-ID: <a5121e34-8bd5-d388-1c0c-e6dbe672ee58@gentoo.org> (raw)
In-Reply-To: <56c1caef-048c-9f75-9e31-d009d934bce5@gentoo.org>
On 11/13/2018 01:21 AM, Zac Medico wrote:
>
> What's inherently wrong about nix having a file store under /nix? Is
> this purely about FHS?
>
It goes against not only the FHS, but against our existing policies and
common sense. There's no reason to expect that path to even be writable.
And nix stores everything there, so if you have / mounted on a smaller
partition with e.g. /home and /var mounted elsewhere, then it's going to
fill the disk up with junk that emerge won't remove for you.
But it's also just absurd how much trouble we go to to wind up right
back where we started:
* Spend years developing a FHS so that people can get the most out
of their storage hardware and know where to find stuff on their
computers.
* Adopt a bunch of policies in Gentoo for where ebuilds should store
things.
* Add QA checks to ensure that packages abide by said policies.
* Add package-manager-specific variables that sidestep the QA checks.
* Begin adding exceptions to every package that puts things in the
wrong place so that people don't see warnings about things being in
the wrong place...
All to achieve the end result, that nothing is where it's supposed to be
and you can't plan anything.
I think I'm just tired. I'll stop.
next prev parent reply other threads:[~2018-11-13 6:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 20:33 [gentoo-dev] [PATCH] install-qa-check.d: Support QA{,_STRICT}_INSTALL_PATHS variables (bug 670902) Zac Medico
2018-11-12 20:57 ` Michael Orlitzky
2018-11-12 21:06 ` Zac Medico
2018-11-12 22:34 ` Michael Orlitzky
2018-11-12 23:47 ` Zac Medico
2018-11-13 5:44 ` Michael Orlitzky
2018-11-13 6:21 ` Zac Medico
2018-11-13 6:57 ` Michael Orlitzky [this message]
2018-11-13 21:21 ` William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a5121e34-8bd5-d388-1c0c-e6dbe672ee58@gentoo.org \
--to=mjo@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox