| 1 |
On 11/12/18 9:44 PM, Michael Orlitzky wrote: |
| 2 |
> On 11/12/2018 06:47 PM, Zac Medico wrote: |
| 3 |
>>> |
| 4 |
>>> The idea being, to put it in the right place by default, and let people |
| 5 |
>>> override it with EXTRA_ECONF if they really want to download random |
| 6 |
>>> binaries from strangers and run them. |
| 7 |
>> |
| 8 |
>> I recommend to add /nix to the whitelist because this is the default |
| 9 |
>> location for all operating systems, as shown consistently throughout the |
| 10 |
>> installation instructions found at |
| 11 |
>> https://nixos.org/nix/manual/#chap-installation. |
| 12 |
> |
| 13 |
> I mean... I know... my argument is not that they don't tell you to do |
| 14 |
> something dumb. If you really want the official experience, you can |
| 15 |
> close your eyes, cross your fingers, say a prayer to RMS, and then |
| 16 |
> follow their installation instructions: |
| 17 |
> |
| 18 |
> $ curl https://nixos.org/nix/install | sh |
| 19 |
> |
| 20 |
> The fact that some people choose to use portage to install it probably |
| 21 |
> means that they were looking for something a little less yee-haw. |
| 22 |
|
| 23 |
The benefit of using the ebuild is the same as always, it allows for |
| 24 |
automated upgrade, uninstall, etc. |
| 25 |
|
| 26 |
> We |
| 27 |
> trust the package manager to not let ebuilds do dumb things to our |
| 28 |
> systems: no surprise network access, no random filesystem reads/writes, |
| 29 |
> reliable uninstalls, things installed in sensible paths, etc. We |
| 30 |
> shouldn't make exceptions to those policies without a good reason. |
| 31 |
|
| 32 |
What does any of this have to do with the nix having a file store under |
| 33 |
/nix? |
| 34 |
|
| 35 |
>> The nix manual also has this explicit warning in the "Building Nix from |
| 36 |
>> Source" section found at https://nixos.org/nix/manual/#sec-building-source: |
| 37 |
>> |
| 38 |
>>> Warning: It is best not to change the Nix store from its default, |
| 39 |
>> since doing |
| 40 |
>>> so makes it impossible to use pre-built binaries from the standard Nixpkgs |
| 41 |
>>> channels — that is, all packages will need to be built from source. |
| 42 |
> |
| 43 |
> Do I have to be that guy who suggests that if people don't want to build |
| 44 |
> from source, then maybe they took a wrong turn back at distrowatch? |
| 45 |
|
| 46 |
They're able to choose between building from source or using prebuilt |
| 47 |
packages, and changing the location of the /nix file store is unnecessary. |
| 48 |
|
| 49 |
> You can override the nix store location with EXTRA_ECONF if you really |
| 50 |
> want to dump stuff in /nix. At which point the warning is just telling |
| 51 |
> you what's up: you're doing something wrong. |
| 52 |
|
| 53 |
What's inherently wrong about nix having a file store under /nix? Is |
| 54 |
this purely about FHS? |
| 55 |
-- |
| 56 |
Thanks, |
| 57 |
Zac |
Archives