History

Niklas Gollenstede df8c451050 add hardware config for Raspberry PIs, start making scripts more robust, improve compatibility with containers		2022-11-30 13:41:21 +01:00
..
default.nix	many small fixes/improvements, and:	2022-06-28 22:30:07 +02:00
gptfdisk-move-secondary-table.patch	modularize setup scripts, make hibernation safe with ZFS, apply noexec FS option everywhere	2022-07-29 12:49:55 +02:00
nixpkgs-add-extlinud-ui.patch	add hardware config for Raspberry PIs, start making scripts more robust, improve compatibility with containers	2022-11-30 13:41:21 +01:00
nixpkgs-fix-systemd-boot-install.patch	init	2022-05-09 14:36:47 +02:00
nixpkgs-fix-zfs-import-keys.patch	add hardware config for Raspberry PIs, start making scripts more robust, improve compatibility with containers	2022-11-30 13:41:21 +01:00
nixpkgs-grub-part.patch	add hardware config for Raspberry PIs, start making scripts more robust, improve compatibility with containers	2022-11-30 13:41:21 +01:00
nixpkgs-test.patch	init	2022-05-09 14:36:47 +02:00
README.md	modularize setup scripts, make hibernation safe with ZFS, apply noexec FS option everywhere	2022-07-29 12:49:55 +02:00

README.md

Some Patches

... for nixpkgs or programs therein.

A patch <name>-*.patch is generally for the open source software <name> which is added/modified by the nixpkgs overlay in ../overlays/<name>.nix.md. Patches for nixpkgs are applied in ../flake.nix.

To create/"commit" a patch of the current directory vs its latest commit:

 git diff >.../patches/....patch

To test a patch against the repo in CWD, or to "check it out" to edit and then "commit" again:

 git reset --hard HEAD # destructively reset the working tree to the current commit
 patch --dry-run -p1 <.../patches/....patch # test only
 patch           -p1 <.../patches/....patch # apply to CWD

License

Patches included in this repository are written by the direct contributors to this repository (unless individually noted otherwise; pre-existing patches should be referenced by URL).

Each individual patch shall be licensed by the most permissive license (up to common domain / CC0) that the software it is for (and derived from) allows. Usually that would probably be the license of the original software itself, which should be mentioned in the respective overlay and/or the linked source code.