From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Michael Orlitzky <mjo@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] install-qa-check.d: Support QA{,_STRICT}_INSTALL_PATHS variables (bug 670902)
Date: Mon, 12 Nov 2018 22:21:27 -0800 [thread overview]
Message-ID: <56c1caef-048c-9f75-9e31-d009d934bce5@gentoo.org> (raw)
In-Reply-To: <d2ee8bdb-9ca6-804a-7422-882aea1fe347@gentoo.org>
[-- Attachment #1.1: Type: text/plain, Size: 2493 bytes --]
On 11/12/18 9:44 PM, Michael Orlitzky wrote:
> On 11/12/2018 06:47 PM, Zac Medico wrote:
>>>
>>> The idea being, to put it in the right place by default, and let people
>>> override it with EXTRA_ECONF if they really want to download random
>>> binaries from strangers and run them.
>>
>> I recommend to add /nix to the whitelist because this is the default
>> location for all operating systems, as shown consistently throughout the
>> installation instructions found at
>> https://nixos.org/nix/manual/#chap-installation.
>
> I mean... I know... my argument is not that they don't tell you to do
> something dumb. If you really want the official experience, you can
> close your eyes, cross your fingers, say a prayer to RMS, and then
> follow their installation instructions:
>
> $ curl https://nixos.org/nix/install | sh
>
> The fact that some people choose to use portage to install it probably
> means that they were looking for something a little less yee-haw.
The benefit of using the ebuild is the same as always, it allows for
automated upgrade, uninstall, etc.
> We
> trust the package manager to not let ebuilds do dumb things to our
> systems: no surprise network access, no random filesystem reads/writes,
> reliable uninstalls, things installed in sensible paths, etc. We
> shouldn't make exceptions to those policies without a good reason.
What does any of this have to do with the nix having a file store under
/nix?
>> The nix manual also has this explicit warning in the "Building Nix from
>> Source" section found at https://nixos.org/nix/manual/#sec-building-source:
>>
>>> Warning: It is best not to change the Nix store from its default,
>> since doing
>>> so makes it impossible to use pre-built binaries from the standard Nixpkgs
>>> channels — that is, all packages will need to be built from source.
>
> Do I have to be that guy who suggests that if people don't want to build
> from source, then maybe they took a wrong turn back at distrowatch?
They're able to choose between building from source or using prebuilt
packages, and changing the location of the /nix file store is unnecessary.
> You can override the nix store location with EXTRA_ECONF if you really
> want to dump stuff in /nix. At which point the warning is just telling
> you what's up: you're doing something wrong.
What's inherently wrong about nix having a file store under /nix? Is
this purely about FHS?
--
Thanks,
Zac
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2018-11-13 6: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 [this message]
2018-11-13 6:57 ` Michael Orlitzky
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=56c1caef-048c-9f75-9e31-d009d934bce5@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mjo@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