[Nix-dev] Contributing to nixpkgs and maintainers burden

Matthias Beyer mail at beyermatthias.de
Tue Apr 12 12:42:27 CEST 2016


On 12-04-2016 12:14:08, Vladimír Čunát wrote:
> On 04/12/2016 12:04 PM, Matthias Beyer wrote:
> > IMHO we should have a workflow for package updates. Like a dedicated branch [...]
> 
> We have label:"8.has: package (update)". People without push access
> can't set labels, but they also wouldn't be able to do anything with the
> proposed branch... (except to file PRs against it)

I meant something more radically:

If we have a branch for this, we can crawl github for PRs with
"foo: version -> version" Pull requests, test-build them and apply them to the
update-packages branch.

(possibly the other way round, first apply the patch, test build the package and
if that fails remove the commit from the branch again)

PRs on github can then be auto-closed if the build succeeds.

I put something together in this gist:

    https://gist.github.com/matthiasbeyer/6f7b08729c35cd86265feba0ea577205

It does build-first and then applies the patch and the mass-update.sh script is
a helper to call the other script in a loop for all lines in a file with

    <remote> <pr number> <package name which is updated> <branch the PR should be committed onto>

The git repository for this has to be set up to contain PRs in
<remote>/pr/<number>.

I tested this with 4 PRs from nixpkgs (build still running here, but it works)

OF COURSE this sould only be done for small package updates, not for something
like haskell-updates where thousands of packages are updated in a single
PR/commit. This is something to reduce the noise for small package updates as I
publish them: Like "khal: 0.8.0 -> 0.8.1" and "sqlitebrowser: 0.2.0 -> 0.3.0" or
something like this.

-- 
Mit freundlichen Grüßen,
Kind regards,
Matthias Beyer

Proudly sent with mutt.
Happily signed with gnupg.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
Url : http://lists.science.uu.nl/pipermail/nix-dev/attachments/20160412/b638436b/attachment.bin 


More information about the nix-dev mailing list