-
Notifications
You must be signed in to change notification settings - Fork 25
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
DerivationParseError around ca-derivations #122
Comments
I think this might be a bug in the nix-derivation library. |
Bumping as I just ran into this -- @maralorn any ideas on how deep a refactor would be required to drop the dependency on EDIT: Maybe it's not too bad; I made a PR which just vendors the relevant portion of the library: #127. Although, I'm not sure what the implications are of that license-wise (or if that's a direction you had in mind). |
Taking some BSD-licensed code and republishing under GPL is not an issue, I think. But I’d rather not go down this route. Either we contribute to maintaining nix-derivation (or a fork of it) or we don’t use it. I plan to stop relying on parsing derivations at all. I plan to use the However I haven’t tried that out yet, so I am not certain that it will be an improvement. It would however make us less dependent on the derivation format to be stable. |
Any progress on this? would really like to build content-addressed derivations with nom! :) |
I am testing ca-derivations for things that frequently rebuild but don't always change like the configuration.nix man page.
I think the usage of this is triggering the following bug in nom:
I did another run with debug loggin through tee and captured the following message:
The text was updated successfully, but these errors were encountered: