search

nix-community / nixpkgs-wayland

Automated, pre-built packages for Wayland (sway/wlroots) tools for NixOS. [maintainers=@colemickens, @Artturin]
510 stars 47 forks source link

discussion: pipeline to get packages into nixpkgs #385

Open edrex opened 1 year ago

edrex commented 1 year ago

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 commented 1 year ago

Reasons not to / difficulties?

this repo contains unreleased versions of packages instead of releases

edrex commented 1 year ago

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 commented 1 year ago

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 commented 1 year ago

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. https://github.com/artempyanykh/marksman/issues/118#issuecomment-1339734583

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

:+1: 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 commented 1 year ago

drat! I tried! https://github.com/nix-community/nixpkgs-wayland/commit/30ca5a097a9f78005b303f2e723d6d986b554686

open to suggestions!