-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
Distributing an overlay with nur #10
Comments
I would propose to put nixos modules and overlays in a seperate namespace within the repository. This helps later to make overlays/modules discoverable in a search engine: let
nixpkgs = import <nixpkgs> { overlays = [
nixpkgs.nur.repos.mpickering.overlays.haskell-plugins
]; };
in |
I will extend the documentation for that. |
Merged
The current solution is a bit problematic, because nixpkgs is required to get the nix source for the overlay. This needs a better solution. |
this pull request will solve the problem: #27 |
milahu
pushed a commit
to milahu/NUR
that referenced
this issue
Aug 5, 2023
milahu
pushed a commit
to milahu/NUR
that referenced
this issue
Aug 6, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have recently released a project I would like to distribute in a
NUR
like manner.https://github.com/mpickering/haskell-nix-plugin
It is currently packaged as an overlay. The intended usage is something like..
Could I instead add the "overlay" to NUR and a user would instead write,
Can you think of a nicer overall packaging strategy for this project?
The text was updated successfully, but these errors were encountered: