mirror/nixpkgs - Nix packages collection

Age	Commit message (Collapse)	Author	Files	Lines
2024-06-09	treewide: Remove indefinite article from meta.description	Alexis Hildebrandt	2	-2/+2
	nix run nixpkgs#silver-searcher -- -G '\.nix$' -0l 'description."[Aa]n?' pkgs \ \| xargs -0 nix run nixpkgs#gnused -- -i '' -Ee 's/(description.")[Aa]n? (.)/\1\U\2/'
2024-03-19	treewide: add meta.mainProgram to packages with a single binary	stuebinm	2	-0/+2
	The nixpkgs-unstable channel's programs.sqlite was used to identify packages producing exactly one binary, and these automatically added to their package definitions wherever possible.
2023-11-09	lib.systems: elaborate Rust metadata	Alyssa Ross	1	-4/+2
	We need this stuff to be available in lib so make-derivation.nix can access it to construct the Meson cross file. This has a couple of other advantages: - It makes Rust less special. Now figuring out what Rust calls a platform is the same as figuring out what Linux or QEMU call it. - We can unify the schema used to define Rust targets, and the schema used to access those values later. Just like you can set "config" or "system" in a platform definition, and then access those same keys on the elaborated platform, you can now set "rustcTarget" in your crossSystem, and then access "stdenv.hostPlatform.rustcTarget" in your code. "rustcTarget", "rustcTargetSpec", "cargoShortTarget", and "cargoEnvVarTarget" have the "rustc" and "cargo" prefixes because these are not exposed to code by the compiler, and are not standardized. The arch/os/etc. variables are all named to match the forms in the Rust target spec JSON. The new rust.target-family only takes a list, since we don't need to worry about backwards compatibility when that name is used. The old APIs are all still functional with no warning for now, so that it's possible for external code to use a single API on both 23.05 and 23.11. We can introduce the warnings once 23.05 is EOL, and make them hard errors when 23.11 is EOL.
2023-10-18	mrustc: 0.10 -> 0.10.1	Emily Trau	1	-3/+3

2023-04-16	mrustc-bootstrap: Document workarounds	Val Lorentz	2	-1/+4

2023-04-16	mrustc-bootstrap: Recompile minicargo	Val Lorentz	1	-1/+2

2023-04-16	mrustc: Remove obsolete patches	Val Lorentz	4	-67/+0

2023-04-06	mrustc: 0.9 -> 0.10	Val Lorentz	4	-38/+43
	And switch from Rust 1.29 to 1.54, as this is the top version supported by mrustc
2022-09-11	mrustc-bootstrap: pin to openssl_1_1	Anthony Roussel	1	-1/+2

2022-04-17	mrustc: fixup build	Vladimír Čunát	1	-0/+1
	Probably after gcc update. Anyway, including standard headers should be safe even if not utilized (and they do seem here).
2021-05-08	mrustc: fix llvm_config path	Jonathan Ringer	1	-1/+1

2021-04-23	mrustc: init at 0.9	Valentin Lorentz	7	-0/+312
	mrustc is mostly patched to use shared LLVM sources but still uses in-tree source for compiler-rt from LLVM 7. This needs to be patched to compile under glibc 2.31 or later. It's easy enough to reapply all our compiler-rt patches here.