-
Notifications
You must be signed in to change notification settings - Fork 45
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
discussion: pipeline to get packages into nixpkgs #385
Comments
this repo contains unreleased versions of packages instead of releases |
ohhhh that makes sense. Does it seem worthwhile to y'all to brainstorm ways to streamline getting released versions of packages here into nixpkgs? Once the initial PR for a package is in, nixpkgs' update checker will handle updates. How about just stating a policy that once a package here sees a release, a PR should be submitted to nixpkgs? (presumably by whoever touched it last) |
nixpkgs has their own auto-update bots and tools (see
it's better to get the package in nixpkgs first and then add a override here (create a issue or a pr here linking to the nixpkgs pr)
already done by nixpkgs update bots |
Ya.. I finally learned that in a way that I'm unlikely to unforget a few days ago. artempyanykh/marksman#118 (comment)
This makes total sense, yes.
👍 Also I think something could be done to make this project's raison d'etre clearer to skimmers like myself. I'm pretty ok at docs and would like to take a look. |
drat! I tried! 30ca5a0 open to suggestions! |
On the surface of it, seems like a GH action could automate submitting a nixpkgs PR for each new/updated package.
As a packager, this would remove any reluctance about submitting here VS directly to nixpkgs since I would get a nixpkgs PR for free.
Reasons not to / difficulties?
The text was updated successfully, but these errors were encountered: