Been using nix for a while for bookkeeping my development environments and it's been nice. The config syntax just is a bit unfamiliar so I'd be happy to check out Guix. The problem is that I
also use non-free software and I haven't yet figured out how to set up my own Guix repo for that. Anyone got any luck with that?
That's nice, but why stop at being a package manager? Why not also replace the build tool (make et al.)?<p>If all the functional machinery is in place, this would be perfect for a build tool.
What's the benefit of Guix compared to tools like Chef (<a href="https://www.getchef.com/" rel="nofollow">https://www.getchef.com/</a>) or Puppet(<a href="https://puppetlabs.com/" rel="nofollow">https://puppetlabs.com/</a>)?
A similar project, using docker and pexpect for dynamic and programmable - but auditable and deterministically built - images:<p><a href="http://ianmiell.github.io/shutit/" rel="nofollow">http://ianmiell.github.io/shutit/</a>