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

discussion: pipeline to get packages into nixpkgs #385

Open
edrex opened this issue Dec 10, 2022 · 5 comments
Open

discussion: pipeline to get packages into nixpkgs #385

edrex opened this issue Dec 10, 2022 · 5 comments

Comments

@edrex
Copy link
Contributor

edrex commented Dec 10, 2022

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?

@Artturin
Copy link
Member

Reasons not to / difficulties?

this repo contains unreleased versions of packages instead of releases

@edrex edrex changed the title automation: submit new/updated package PRs to nixpkgs discussion: pipeline to get packages into nixpkgs Dec 10, 2022
@edrex
Copy link
Contributor Author

edrex commented Dec 10, 2022

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)

@Artturin
Copy link
Member

Artturin commented Dec 10, 2022

Does it seem worthwhile to y'all to brainstorm ways to streamline getting released versions of packages here into nixpkgs?

nixpkgs has their own auto-update bots and tools (see passthru.updateScript)

Once the initial PR for a package is in

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)
the process could be added to the readme

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)

already done by nixpkgs update bots

@edrex
Copy link
Contributor Author

edrex commented Dec 11, 2022

nixpkgs has their own auto-update bots and tools (see passthru.updateScript)

Ya.. I finally learned that in a way that I'm unlikely to unforget a few days ago. artempyanykh/marksman#118 (comment)

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)

This makes total sense, yes.

the process could be added to the readme

👍 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.

@colemickens
Copy link
Member

drat! I tried! 30ca5a0

open to suggestions!

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

No branches or pull requests

3 participants