|
|
| Line 31: |
Line 31: |
|
| |
|
| == Modifying a Package == | | == Modifying a Package == |
| In LSB distributions, after installing a package, you would go to /usr/whatever and edit the files you want to change. | | In LSB distributions, files installed under {{ic|/usr}} can be edited by the user as needed. |
|
| |
|
| With Nix, any files inside the store (/nix/store, where all nix installed files end up; ~/.nix-profile is a symlink to a store path), are meant to be read-only. That is, nix expects those files only under her control, and it is a requirement to allow rollbacks and reproducibility. Of course the owner of the nix store can change files there, but then you cannot expect rollbacks or reproducibility. "nix-store --verify --check-contents" will tell you if there are files modified in the store (since the creation of each store path). Although modifying a file in the store seems like an easy quick fix, it should be regarded as bad as modifying the memory of a running process, because it has almost all the analogous downsides.
| | Files in the Nix store ({{ic|/nix/store}}) are meant to be read-only and changes are only done using the {{ic|nix}} commands. {{ic|nix-store --verify --check-contents}} can be used to ensure integrity of the store data. |
|
| |
|
| For a discussion of methods to make (durable) changes to Nix packages, see [[Modifying a Package]]
| | To make changes to Nix packages properly, see [[Modifying a Package]]. |
|
| |
|
| == See also == | | == See also == |
