From: William Hubbs <williamh@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 15:21:38 -0600 [thread overview]
Message-ID: <20181113212138.GA28564@whubbs1.gaikai.biz> (raw)
In-Reply-To: <a5121e34-8bd5-d388-1c0c-e6dbe672ee58@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 777 bytes --]
On Tue, Nov 13, 2018 at 01:57:47AM -0500, Michael Orlitzky wrote:
> 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.
I'm with Zac on this, we should install the way upstream directs, or if
we have that strong of an aversion to it, we should open a bug upstream
to fix it.
Thanks,
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2018-11-13 21:21 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
2018-11-13 21:21 ` William Hubbs [this message]
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=20181113212138.GA28564@whubbs1.gaikai.biz \
--to=williamh@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