puck/lix
0
0
Fork 0
forked from lix-project/lix
Code Pull requests Activity
12764 commits 19 branches 0 tags 68 MiB
C++ 80.2%
Shell 7.9%
Nix 6%
Meson 1.4%
Makefile 1.1%
Other 3.4%
Find a file
John Ericson 752f967c0f "valid signature" -> "trustworthy signature" 
I just had a colleague get confused by the previous phrase for good
reason. "valid" sounds like an *objective* criterion, e.g. and *invalid
signature* would be one that would be trusted by no one, e.g. because it
misformatted or something.

What is actually going is that there might be a signature which is
perfectly valid to *someone else*, but not to the user, because they
don't trust the corresponding public key. This is a *subjective*
criterion, because it depends on the arbitrary and personal choice of
which public keys to trust.

I therefore think "trustworthy" is a better adjective to use. Whether
something is worthy of trust is clearly subjective, and then "trust"
within that word nicely evokes `trusted-public-keys` and friends.
2022-09-22 10:49:31 -04:00
.github issue template: fill 'about' field 2022-09-19 10:05:29 +02:00
config Run autoupdate 2021-06-01 11:42:38 +02:00
contrib function-trace: always show the trace 2019-09-18 23:23:21 +02:00
doc/manual release-notes/rl-next.md: note new argument to fetchurl.nix 2022-09-16 01:59:24 -07:00
m4 autoconf: Fix C++17 detection not working on Ubuntu 16.04. 2019-07-03 04:32:25 +02:00
maintainers Integrate push-docker.sh into the release script 2022-02-18 13:58:01 +01:00
misc Apply suggestions from code review 2022-09-02 10:50:02 -05:00
mk Fix incremental static builds 2022-06-22 17:53:58 +02:00
perl Remove std::string alias (for real this time) 2022-02-25 16:13:02 +01:00
scripts Add fish suport to installer 2022-09-13 12:56:16 -04:00
src "valid signature" -> "trustworthy signature" 2022-09-22 10:49:31 -04:00
tests "valid signature" -> "trustworthy signature" 2022-09-22 10:49:31 -04:00
.dir-locals.el .dir-locals.el: Set c-block-comment-prefix 2020-07-10 11:21:06 +02:00
.editorconfig Add .editorconfig 2017-06-05 22:57:28 +01:00
.gitignore Add fish suport to installer 2022-09-13 12:56:16 -04:00
.version Bump version 2022-08-25 11:50:14 +02:00
boehmgc-coroutine-sp-fallback.diff Update boehmgc-coroutine-sp-fallback.diff for darwin 2022-09-01 11:48:50 -05:00
bootstrap.sh bootstrap: Simplify & make more robust. 2011-09-06 12:11:05 +00:00
configure.ac Don't use -load_all on darwin 2022-08-03 10:27:25 +02:00
COPYING * Change this to LGPL to keep the government happy. 2006-04-25 16:41:06 +00:00
default.nix Remove url literals 2022-01-24 13:28:21 +01:00
docker.nix docker.nix: Provide boolean for whether to bundle nixpkgs 2022-08-09 23:21:27 -04:00
flake.lock curl: patch for netrc regression in Nix 2022-07-14 17:45:02 -05:00
flake.nix Installer: Reset the timestamps in the tarball 2022-09-05 14:44:01 +02:00
local.mk Remove 'dist' target 2020-12-03 16:17:58 +01:00
Makefile Merge branch 'master' into lto 2022-05-25 11:55:13 +00:00
Makefile.config.in Embed the sandbox shell into the statically linked 'nix' binary 2022-06-23 04:08:28 +02:00
precompiled-headers.h Config: Use nlohmann/json 2020-08-20 11:02:16 +02:00
README.md Fix link to hacking doc 2022-07-30 09:12:50 -07:00
shell.nix Remove url literals 2022-01-24 13:28:21 +01:00

README.md

Nix

Open Collective supporters Test

Nix is a powerful package manager for Linux and other Unix systems that makes package management reliable and reproducible. Please refer to the Nix manual for more details.

Installation

On Linux and macOS the easiest way to install Nix is to run the following shell command (as a user other than root):

$ curl -L https://nixos.org/nix/install | sh

Information on additional installation methods is available on the Nix download page.

Building And Developing

See our Hacking guide in our manual for instruction on how to build nix from source with nix-build or how to get a development environment.

Additional Resources

License

Nix is released under the LGPL v2.1.