-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Extrct patches from patch.sh #730
Comments
@noonien you can create another script that sources the patch.sh script and read/lookup the Line 57 in 26db5e7
This script for example did something similar https://github.com/arcnmx/nixexprs/blob/36583070152bb7bed68e56feeff29889a227ef01/pkgs/public/linux/default.nix#L161 (on an older version of the patch.sh script which had two dictionaries) |
While this solves the issue, sourcing |
@noonien I understand your concern, in fact I too had to write ugly bash scripts for automating updating the The only reason I am not switching away to keeping the actual bytecode outside the bash script is that many people do:
or similar without ever cloning the github repository. If it becomes a big headache I might break this particular workflow, but it's workable for now. To avoid polluting the environment you can try a multi-line grep or similar to extract only the |
I think something that might work is keeping just the Patches welcome if you want to implement something like that. |
Hello!
I would like to add NixOS support for
nvidia-patch
, however, NixOS works completely differently from other OSs, the patch script would not work, even though patching the driver is very easy.The problem is that the
patch.sh
has code to do more than just patch the driver, it searches for the driver, identifies versions, etc. This is not something that's needed for NixOS. All that's ended is a script that takes as arguments the version and path of the file to be patched, and patches it.An alternative would be to also have the patches as a separate, more parseable file.
The text was updated successfully, but these errors were encountered: