News for hackers. Stuff that matters.
Re:Reflections on NixOS by radarsat1 on Monday August 22, 2016 @10:06AM (#12336391)
> Packaging the Nix way does require patching upstream and that's probably inevitable.

Not to familiar with Nix, can you explain why? Anything that can't be handled simply by applying small patches to the upstream during packaging?

Re:Reflections on NixOS by jorams on Monday August 22, 2016 @10:24AM (#12336516)
"patching upstream" in this context means "applying patches to the upstream during packaging".

Nix and Guix require programs to work with a directory layout that differs significantly from the standard. Simple things like `#!/bin/python` don't work anymore, because they aren't explicit enough.

Re:Reflections on NixOS by mbrock on Monday August 22, 2016 @11:48AM (#12337161)
Yeah, thanks. To add to that, the Nixpkgs "standard library" includes lots of convenient tools for patching like this, and much of the common stuff is done automatically by the standard package function. The #nixos IRC channel is a good place to ask if you run into trouble when packaging something.

Generally, making NixOS packages is really delightful. Even the patching stuff is straightforward and easy to use. Now that I've learned the basics, I routinely make small packages.

With many typical packages the only thing you need to do is specify how to fetch the source, plus the list of build dependencies, and there are built-in functions for fetching from HTTPS or Git.

Re:Reflections on NixOS by radarsat1 on Monday August 22, 2016 @01:12PM (#12337785)
Ah ok, that clarifies things. Thanks.