mirror/nixpkgs - Nix packages collection

Age	Commit message (Collapse)	Author	Files	Lines
2024-06-09	treewide: Remove the definite article from meta.description	Alexis Hildebrandt	1	-1/+1
	nix run nixpkgs#silver-searcher -- -G '\.nix$' -0l 'description."([Tt]he)? ' pkgs \ \| xargs -0 nix run nixpkgs#gnused -- -i '' -Ee 's/(description.")[Tt]he (.)/\1\U\2/'
2024-05-24	openjfx: mark EOL releases as vulnerable	Infinidoge	1	-0/+3

2024-05-24	openjfx: build openjfx20 with openjdk20	Infinidoge	1	-4/+4

2024-05-24	Merge pull request #313920 from wegank/openjdk-bump-split-1	Weijia Wang	1	-4/+4
	openjdk{16,18,19,20}, openjfx{20,22}: update
2024-05-24	pkgs/development: remove unused fetchpatch arguments	Sigmanificient	1	-1/+1

2024-05-23	openjfx: 20+19 -> 20.0.2-ga	Infinidoge	1	-4/+4

2024-04-08	openjfx{11,17,19,20,21,22}: fix build when withWebKit is enabled	TomaSajt	1	-3/+21

2023-10-15	openjfx: respect NIX_BUILD_CORES in nested cmake	Artturin	1	-0/+1
	Building `openjfx11` or `openjfx12` on a machine with many cores can consume huge amounts of RAM. With 24 cores, the memory usage exceeded `25GB` per build for me. Using `NIX_BUILD_CORES` to reduce the number of parallel tasks doesn't help, because a script invoking `cmake` does not respect `NIX_BUILD_CORES` and passes `-j <number of cores>`. Setting `NUMBER_OF_PROCESSORS` overrides the automatic core count detection in the script. https://github.com/search?q=repo%3Aopenjdk%2Fjfx%20NUMBER_OF_PROCESSORS&type=code Co-authored-by: Fabian Möller <fabianm88@gmail.com>
2023-07-02	openjdk: init at 20+36 and openjfx: init at 20+19	sohalt	1	-0/+113