-
Notifications
You must be signed in to change notification settings - Fork 19
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
Repackage liberaforms without mach-nix #40
Comments
Merged
This was referenced Nov 15, 2023
Merged
Closed by #194 |
github-project-automation
bot
moved this from under mobsideration
to mobleted
in Summer of Nix
Apr 25, 2024
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue #39 identifies how the use of mach-nix for liberaforms (which uses an IDF) depended on an old version of nixpkgs as a workaround to a bug a with mach-nix DavHau/mach-nix#549 which made it incompatible with newer versions of nixpkgs. That is documented here: https://github.com/ngi-nix/ngipkgs/blob/main/pkgs/liberaforms/env.nix#L9-L16 it was from back in June when we set up ngipkgs with liberaforms as the initial test service.
Since then, I see that in early July a new PR was merged for mach-nix DavHau/mach-nix#563 that apparently fixes the incompatibility with newer nixpkgs. Assuming this fix works, then in theory this issue could be resolved by sourcing the import of mach-nix for liberaforms from its master branch (to include the fix) and then removing the old nixpkgs workaround. I tried this here: https://github.com/ngi-nix/ngipkgs/tree/remove-old-nixpkgs but ran into the following error (which was also problematic in earlier iterations of packaging liberaforms):
As discussed in #24, the use of an IFD by mach-nix for the liberaforms package is already a problem for CI performance, and there are likely going to continue to be problems with mach-nix since it doesn't seem to be very actively maintained anymore. Therefore this new issue with mach-nix raised in issue #39 is adding to a growing list of reasons to disable liberaforms in ngipkgs until further work can be done on it to transition away from the use of mach-nix and IFDs, perhaps also as part of updating the packaging to a new version 3.0 of liberaforms which looks like it could come out sometime in the next year.
Tracking issue: #12
The text was updated successfully, but these errors were encountered: