[Nix-dev] Implement a process for maintaining simple package updates?

[Matthias Beyer]

On 05-02-2017 13:40:40, Graham Christensen wrote:
> Matthias Beyer <mail at beyermatthias.de> writes:
> > I would like to ask whether it would be of any help if someone 
> > (for example me) would take all package-update PRs and cherry-pick 
> > these commits on a "package-update" branch which gets merged 
> > every... 7 days for example?
> 
> I don't have any real opinions about this, but do have some questions:
> 
>  - Can you describe the advantages of this process?

Less noise on master, less to worry about by others, thus reducing 
overhead for others.

>  - Will you be vetting the correctness of the changes, or simply
>    aggregating them?

I will simply aggregate them.

I could, as long as I'm with my university, do a `nix-build` for each 
package, as long it is for x86_64 linux (the machines I have access to 
are debian with nix installed).

But initially, the "I open PR on Saturday and ping pkg maintainers to 
review" step is meant for review/testing.

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

Consider switching to free software.
It adds value to your life.
https://www.gnu.org/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.science.uu.nl/pipermail/nix-dev/attachments/20170205/4843cdd7/attachment.sig>