Re: [Nix-dev] haskell structure for all of nixpkgs

Understood. The comments regarding name finding in this post are interesting: http://www.tweag.io/blog/stack-nix-portable-reproducible-builds seems like a common issue. (a lot of weight just to support incremental recompilation for Haskell!) ___

Re: [Nix-dev] haskell structure for all of nixpkgs

I am not arguing against that kind of categorization at all. Its just that it only works where you have a directory structure. The Haskell approach does not, so it wont work there. Its a problem with the Haskell approach. Sent from [ProtonMail](https://protonmail.com), encrypted email based

Re: [Nix-dev] haskell structure for all of nixpkgs

Ah I see, Haskell grepping is quite useless. Categorization using hierarchy generally is a good idea and makes sense for large amounts of information. This naturally ties in with a folder hierarchy. I personally find it refreshing information is stored in the directory structure aka the

Re: [Nix-dev] haskell structure for all of nixpkgs

Stewart, As I was formulating a reply, I think this crystallized for me. At the moment Nix encodes a lot of information in the file system/directory structure. Grep naturally surfaces that information. Due to this, In the haskell packages that information doesn't exist and so is not

Re: [Nix-dev] haskell structure for all of nixpkgs

Stewert, I did the majority of the Erlang/Beam packaging and I followed the Haskell model for two main reasons. 1. It worked so well in Haskell - why deviate? 2. Expression generation was much easier. I think these strongly win out, at at least for the Erlang/Beam world. The downside is that

Re: [Nix-dev] haskell structure for all of nixpkgs

I see, What would that tooling look like? Can anyone else see any other drawbacks of this approach? How do Haskellers deal with searching for packages? ___ nix-dev mailing list nix-dev@lists.science.uu.nl

Re: [Nix-dev] haskell structure for all of nixpkgs

On Tue, Apr 26, 2016 at 2:02 AM, Ericson, John wrote: > I'd say https://github.com/NixOS/nixpkgs/pull/14000 was the first big step > in this direction, and hopefully > https://github.com/NixOS/nixpkgs/issues/10874 will lead to the second. Thanks John for the links,

Re: [Nix-dev] haskell structure for all of nixpkgs

Well, besides working on other langauges' integration, I think there are some Petisms™ that all of nixpkgs could benefit from. A good example is pervasive use of `self: super: ...` and fix+extend rather than ad-hoc hacks and the scary reflection used in `lib/customization.nix`. I'd say

[Nix-dev] [JOB] Fullstack web developer

Hi folks, Hope this isn’t off-topic for the list. My company is looking for a mid-level or senior engineer to work on a sophisticated web application. It’s a pretty simple stack - React, Node and Postgres. We package everything with nix and deploy it to NixOS using Nixops. Note that we’re

Re: [Nix-dev] haskell structure for all of nixpkgs

Okay Domen's a +1, maybe the guys and girls who implemented haskell like PL level package systems could weigh in with insight. For example ICIUC, Erlang packages adopts the same approach. The gained knowledge could be helpful to start with this document. Could someone with experience please

Re: [Nix-dev] haskell structure for all of nixpkgs

I agree - someone should start a tutorial how new language support is added and the infrastructure should be based on Haskell as it's most advanced and yet simple. On Mon, Apr 25, 2016 at 10:47 AM, stewart mackenzie wrote: > Hi Tomasz, > > On Sun, Apr 24, 2016 at 6:12 PM,

Re: [Nix-dev] dosbox

Hi, This has already been fixed in 3db3355c835622123245515cdba65edb274e9e7b. Thanks anyway! On 04/25/2016 10:31 AM, Karn Kallio wrote: > > The attached patch fixes the dosbox build by adding mesa. > > > > ___ > nix-dev mailing list >

Re: [Nix-dev] phonon adjustment

On Mon, Apr 25, 2016 at 2:30 AM, Karn Kallio wrote: > > The attached patch to phonon adds a fragment of the change from > staging sufficient to fix the kde5 build in current master, without > patching paths in includes. > > This will make kde5 components (eg dolphin,

Re: [Nix-dev] pgadmin

It appears this issue was fixed in 9ad2832b1bf6897d already. Peter ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] dosbox

The attached patch fixes the dosbox build by adding mesa. >From 29934ae6570cf1c6e884d3a9364a9eeaeeaddfdc Mon Sep 17 00:00:00 2001 From: Karn Kallio Date: Mon, 25 Apr 2016 01:36:38 -0430 Subject: [PATCH] dosbox : add mesa to fix build ---

[Nix-dev] phonon adjustment

The attached patch to phonon adds a fragment of the change from staging sufficient to fix the kde5 build in current master, without patching paths in includes. This will make kde5 components (eg dolphin, gwenview) build in master until the staging arrives. >From