[Nix-dev] RFC: three dying pull requests (let's keep them alive)

Shea Levy shea at shealevy.com
Wed Aug 27 19:38:55 CEST 2014


We've been using the fully-modular branch + modular nixops at zalora
for months: github.com/zalora/nixpkgs github.com/zalora/nixops.

Recursive nix is unused because it was unfinished and it was too much
potential work to keep going without some sign it would be merged.

On Wed, Aug 27, 2014 at 12:32:26PM -0500, John Wiegley wrote:
> >>>>> Daniel Peebles <pumpkingod at gmail.com> writes:
> 
> > I've noticed a bit of a pattern recently on the nix github and wanted to try
> > to stop it before Shea Levy decided this sort of work wasn't worth his time
> > anymore. I'm not proposing that we insta-merge all his changes, but can
> > anyone interested at least chime in with feedback so that these pull
> > requests don't die on the vine?
> 
> I heartily agree.
> 
> Shae, would you be willing to create an experimental-shlevy branch that
> contains these three changes merged against current master?  Then perhaps
> Joel, Daniel and I can switch to using it for couple weeks, and if everything
> looks good and remains working, we simply merge it to master.
> 
> Sadly, I'm not qualified yet to judge the merits of these changes -- although
> they sound like something I might want in future -- so I say we bring them in
> solely based on all the work you've done, and because you think they will
> improve Nix as a platform.  I'm willing to trust your judgment in lieu of
> having time to work through them in detail.
> 
> That is, of course, unless Eelco or others think they lack technical merit.
> 
> John
> _______________________________________________
> nix-dev mailing list
> nix-dev at lists.science.uu.nl
> http://lists.science.uu.nl/mailman/listinfo/nix-dev


More information about the nix-dev mailing list