[Nix-dev] Idris packages in nixpkgs

Hi all, I've just added [1] rudimentary support for building Idris packages and composing the packages with the compiler to nixpkgs. Details can be found in the idris-modules directory [2], including potential future work [3]. Idris's lack of any mechanism to have multiple library paths is

Re: [Nix-dev] Design Patterns for Achieving what Nix is Advertized for

On 11/27/2015 08:32 PM, joach...@fastmail.fm wrote: >> > https://github.com/NixOS/nix/issues/718 > A single bug report is hardly evidence of the "instability of Nix". Note that the "issue" was raised by the one who ask this question... Perhaps many of the properties are possible to achieve with

Re: [Nix-dev] NixOS/Nixpkgs repository labels

On 11/27/2015 05:00 PM, Tomasz Kontusz wrote: > GitHub should already know about that, is a label useful? It will always be > at least a bit out of date too. Yes github knows about this, but I couldn't find a way to access this information. e.g. filter pull unmergable pull request.

Re: [Nix-dev] NixOS/Nixpkgs repository labels

GitHub should already know about that, is a label useful? It will always be at least a bit out of date too. Dnia 27 listopada 2015 11:56:04 CET, Matthias Beyer napisał(a): >On 27-11-2015 11:37:54, Pascal Wittmann wrote: >> On 11/22/2015 11:06 PM, Nicolas Pierron wrote:

Re: [Nix-dev] Design Patterns for Achieving what Nix is Advertized for

On Fri, Nov 27, 2015, at 03:09 AM, Martin Vahi wrote: > > In the light of the instability of the Nix > > https://github.com/NixOS/nix/issues/718 A single bug report is hardly evidence of the "instability of Nix". For many (most?) of us, Nix works as advertised and has done so for a long time.

Re: [Nix-dev] Design Patterns for Achieving what Nix is Advertized for

> which is too complex to describe in this small contemplation. “I have discovered a truly remarkable proof which this margin is too small to contain.” Regarding first workaround: You are right, package names won't collide, however package purposes will and files created on the file system will.

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

I did, and it's a terrific resource for learning the Nix language. In my experience, the pills were helpful at an earlier stage. Before writing any Nix myself beyond copying & pasting into my configuration.nix, I needed to develop a basic understanding of how NixOS works & how to use it. On Sat,

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

did you have a look at https://nixcloud.io/tour/?id=1 already? On 27.11.2015 22:40, Anand Patil wrote: > Hi everyone, > > I've been learning NixOS over the last few days, and Luca Bruno's NixOS > pills > series, > http://lethalman.blogspot.com/2014/07/nix-pill-1-why-you-should-give-it-try.html

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

Hi everyone, I've been learning NixOS over the last few days, and Luca Bruno's NixOS pills series, http://lethalman.blogspot.com/2014/07/nix-pill-1-why-you-should-give-it-try.html , have helped me progress much more quickly than I would have done without them. It took me a surprisingly long time

Re: [Nix-dev] Design Patterns for Achieving what Nix is Advertized for

I just wanted to say thank You for the answers. As of 2015_11_28 it seems to me that one of the main contributions of the Nix project is a systematic and proper description of the problem that arises from the fact that different software components depend on each other and the fact that due to

Re: [Nix-dev] Real documentation, aka "Let's kill the wiki"

Perhaps this could work even nicer with literate programming. Source files could be then exported as manual chapters or extra reference, and the source code displayed next to text would fill gaps for curious readers without having to search github or download a whole nixpkgs repository. That

Re: [Nix-dev] [RFC] buildPythonPackage refactoring

The PR has been merged into master as of yesterday, please report any problems to github issues. The upstream PR has also been merged so we won't need any patches with next pip release: https://github.com/pypa/pip/pull/3252 Domen On Mon, Nov 23, 2015 at 11:18 AM, Tomasz Czyż

Re: [Nix-dev] NixOS/Nixpkgs repository labels

On 11/22/2015 11:06 PM, Nicolas Pierron wrote: > I invite other contributors to join me on this triaging effort, such > that this system is not only made for me. I have just added the label "2.status: merge conflict", to indicate which PRs are unmergable. signature.asc Description: OpenPGP

Re: [Nix-dev] NixOS/Nixpkgs repository labels

On 27-11-2015 11:37:54, Pascal Wittmann wrote: > On 11/22/2015 11:06 PM, Nicolas Pierron wrote: > > I invite other contributors to join me on this triaging effort, such > > that this system is not only made for me. > > I have just added the label "2.status: merge conflict", to indicate > which