Skip to content
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

Maintain our own derivations of ports where necessary #240

Open
getchoo opened this issue Jun 23, 2024 · 2 comments · May be fixed by #384
Open

Maintain our own derivations of ports where necessary #240

getchoo opened this issue Jun 23, 2024 · 2 comments · May be fixed by #384
Milestone

Comments

@getchoo
Copy link
Member

getchoo commented Jun 23, 2024

this should help resolve issues where changes in modules are made to address package updates that have reached unstable, but not stable yet. it will also prevent release blockers due to nixpkgs PRs such as those mentioned in #65 (comment)

@getchoo getchoo added this to the 2.0.0 milestone Jun 23, 2024
@isabelroses
Copy link
Member

Would we be using nixpkgs as a flake input or via nvfetcher?

@getchoo
Copy link
Member Author

getchoo commented Oct 23, 2024

I think we'll just use the nixpkgs from the system in the module

@getchoo getchoo linked a pull request Nov 25, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants