Exotic Nix Targets - Public Room Timeline

	Exotic Nix Targets	335 Members
		101 Servers

Sender	Message	Time
2 Sep 2023
rhelmot	my question was more of the form of "is there a better way to verify self-sufficiency than manually deleting the bootstrap tools from the store and seeing if it needs to rebuild"	05:00:26
trofi	you asked where `/bin/sh` comes from on `NixOS`. That is the easy way to inspect.	06:43:57
trofi	Otherwise if you want to make sure bootstrapTools are not used anywhere it's a bit harder question. You can assert that there are no bootstraoTools references in the stdenv, like : `disallowedRequisites = [ bootstrapTools.out ];` https://github.com/NixOS/nixpkgs/blob/master/pkgs/stdenv/linux/default.nix#L631C7-L631C53	06:46:18
trofi	Generally it's not so easy to make sure that your stdenv does not copy sneakily bits of files from `bootstrapTools`. I usually abuse `strings` to search for a `GCC` string: `$ find $(nix build nixpkgs#stdenv; nix path-info -r ./result) -type f -exec strings '{}' + \| fgrep 'GCC: (GNU)' \| sort -u AGCC: (GNU) 12.3.0 GCC: (GNU) 12.3.0` Does not look too bad. No 8.3.0 references from bootstrapTools.	06:52:55
ash (it/its) 🏳️‍⚧️	why is `pkgsCross` so inconsistently named?	21:51:14
3 Sep 2023
@rick:matrix.ciphernetics.nl	It's theoretically meant as a set of examples	07:05:36
trofi	Would be nice to clean it up and all at least all `nixpkgs` targets as is (instead of examples that sometimes match and sometimes don't).	07:48:19