Re: [Nix-dev] Problem compiling a rust program without fetchFromGitHub

This is _exactly_ the reason why I moved all rust machinery into fractalide before I deprecated it completely. The upstream nixpkgs rustRegistry wasn't keeping up with my newly published rustfbp crate. By having the machinery in fractalide I could bump the registry without making week long turn

Re: [Nix-dev] Problem compiling a rust program without fetchFromGitHub

I mean rustRegistry now ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Problem compiling a rust program without fetchFromGitHub

Okay, progress. No it's not exactly the same as it's not hermetically sealed. You need to update the rustIndex in nixpkgs. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Problem compiling a rust program without fetchFromGitHub

$ nix-garbage-collect then retry ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Rust prebuilt package overlay.

Great stuff Nicolas, much appreciated! ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Why having releases if you break things in it often

Welcome Stefan, Put all that stuff aside for the moment, just a moment, and work your way through this tutorial https://nixcloud.io/tour/?id=1. If once done, you decide nix isn't for you then drop it. If something switches on in your head keep at it cause you'll now have all the tools needed to

Re: [Nix-dev] purescript takes 4+ hours to build a hello world app on nixos

On Mon, Jan 30, 2017 at 1:02 AM, Sergei Trofimovich wrote: > On Sun, 29 Jan 2017 18:48:14 +0800 > Your system time > > real22m21.918s > user13m49.982s > sys 23m1.702s > > suggests something is seriously off on your system. > Perhaps machine is swapping

[Nix-dev] purescript takes 4+ hours to build a hello world app on nixos

I'm confounded by this issue, I'd like to know if anyone on nixos can reproduce this behaviour. https://github.com/purescript/purescript/issues/2598 There are easy steps to reproduce on the issue description. Note it doesn't seem to exhibit when using nix on ubuntu etc. If you can repoduce the

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

see https://github.com/NixOS/hydra/issues/444 On Thu, Jan 19, 2017 at 1:53 AM, Christian Theune wrote: > Hi, > > On 18 Jan 2017, at 18:33, Jean-Pierre wrote: > > New version of hydra (2016-12-09) override gcc to gcc6 > >

Re: [Nix-dev] Hydra: infinite CPU and RAM consumption in evaluator

The next problem you will have is this: https://github.com/NixOS/hydra/issues/445 remove those changes and you will be able to add jobsets. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Call For Maintainers - Fractalide BETA release

Reusable Functions - They're great, they're just great, you'll love them. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Call For Maintainers - Fractalide BETA release

On Thu, Jan 12, 2017 at 8:46 PM, Herwig Hochleitner wrote: > ... Nix's very existence revolves around solving an insanely hard problem, that of reproducibility, it's the only project that actually gets it right. Reproducible monolith apps have _everything_ to do with

Re: [Nix-dev] Call For Maintainers - Fractalide BETA release

So let me understand this clearly. Reusable and reproducible functions have nothing to do with Nix/NixOS? What about reproducible libraries? What about reproducible monolith apps? This is a _new_ concept to the Nix/NixOS ___ nix-dev mailing list

Re: [Nix-dev] Call For Maintainers - Fractalide BETA release

On Thu, Jan 12, 2017 at 7:03 PM, Profpatsch wrote: > Not sure what this has to do with nix-dev? tough crowd, tough crowd. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] Call For Maintainers - Fractalide BETA release

Greetings all, So after some 946 commits a number of rewrites starting in 2014 when Fractalide was implemented in a neat programming language called Mozart Oz, we've gone BETA. At that stage Fractalide was the subject of a Master thesis for Denis Michiels under Professor Peter Van Roy of UCL

Re: [Nix-dev] permission problems

Oh great, look forward to that landing. On Wed, Jan 11, 2017 at 7:00 PM, Domen Kožar wrote: > https://github.com/NixOS/nixpkgs/issues/20156 ___ nix-dev mailing list nix-dev@lists.science.uu.nl

Re: [Nix-dev] permission problems

Peter, Bas, Thank you so much for this information. :-) Is anybody working on bringing in the new systemd? Can I get started on it? kr/sjm On Wed, Jan 11, 2017 at 6:26 PM, Peter Hoeg wrote: > Hi Stewart, > >> I don't suppose there is some sort of convention, i.e. for

Re: [Nix-dev] permission problems

On Wed, Jan 11, 2017 at 4:11 PM, Bas van Dijk wrote: > Hi Stewart, > > config.ids.uids.workbench doesn't seem to exist in: > > https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/misc/ids.nix > > Why do you assume it's there? Which revision of nixpkgs are you using?

[Nix-dev] permission problems

greetings, If I enable this: https://github.com/fractalide/fractal_workbench/blob/master/service.nix#L72 I get $ sudo nixos-rebuild test -I fractalide=/home/stewart/dev/fractalide/fractalide [sudo] password for stewart: building Nix... building the system configuration... error: attribute

Re: [Nix-dev] Remapping Console Key Bindings

services.xserver.xkbOptions = "grp:alt_space_toggle, ctrl:swapcaps"; ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Introducing Nixpkgs Overlays

Hello Nicolas, I support this work. It would make layering of fractalide on nixpkgs easier, also the layering of a developer's set of agents on top of fractalide would be easier and cleaner. I really hope this lands. kudos kr/sjm ___ nix-dev mailing

Re: [Nix-dev] Usability: Nixpkg > NixOS

For me the crux is the nix expression language, everything revolves around this, this is where real tangible value (read as eye opening, toe curling power) is obtained. It might be a good idea creating a nixmake.com or xmake.com site which has a page for most popular languages detailing

Re: [Nix-dev] Reproducibility testing in Hydra

Massive achievement! Congrats to all involved! ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] getting dependencies

okay this bit of code did it: ... propagatedBuildInputs = importedContracts; installPhase = '' runHook preInstall mkdir -p $out/src mkdir -p $out/nix-support for i in $importedContracts; do echo $i >> $out/nix-support/propagated-build-inputs done propagated=""

[Nix-dev] getting dependencies

Greetings, The actual code in question is here: https://github.com/fractalide/fractalide/blob/master/contracts/list/command/default.nix Notice all the duplication! My problem: Achieve Contract Composition! This is where Command should be - without the Tuple duplication!:

Re: [Nix-dev] svanderburg/disnix migrate to nixos/disnix

I'm exploring this software now and it excites me, I'm currently trying to get dysnomia installed, would be perfect if there was a disnix/default.nix that'll just automate all that away (for those nixos users). I keep shying away from building subnets that are services in

[Nix-dev] svanderburg/disnix migrate to nixos/disnix

Hi Sander + all, Disnix looks like a very interesting piece of software, would it be a good idea to move disnix to the main nixos/ organization? kr/sjm ___ nix-dev mailing list nix-dev@lists.science.uu.nl

Re: [Nix-dev] obtaining the drv from an imported object

ah yes, this is my solution: https://github.com/fractalide/frac_example_wrangle { fractalide ? import {} , pkgs ? fractalide.pkgs , support ? fractalide.support , contracts ? fractalide.contracts , components ? fractalide.components}: let publicComponentOrSubnet =

[Nix-dev] obtaining the drv from an imported object

Greetings, I have a specialization repo for fractalide i.e. the repos may import each others components and contracts. They are just specializations / experimental places (https://github.com/fractalide/fractalide_external_opensource_example) I want the specialization repo to be importable by

[Nix-dev] error: stack overflow (possible infinite recursion) && builtins.match isn't documented

Hello, I've just stumbled on a treasure: https://github.com/NixOS/nix/blob/master/src/libexpr/primops.cc#L1937 I'm curious to know why such an important builtin isn't documented here: http://nixos.org/nix/manual/ I'm unusually excited about find, as demonstrated by opening the email with this

Re: [Nix-dev] pass a text file on the internet through <>

Yes you're right a separate arg should be used. Still the <> seems like a wonderful tool and limiting it just to tarballs seems a bit of a waste. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] pass a text file on the internet through <>

Greetings, In my nix code I make use of a <>, when executing the nix-build command I use `-I fractalide_user=https://keybase.io/iElectric/key.asc` (I chose iElectric cause it was convenient) [stewart@rivergod:~/dev/fractalide/fractalide]$ nix-build --argstr debug true --argstr cache

[Nix-dev] Rust: "error: failed to load source for a dependency on ..."

Hi, I've `sudo nixos-rebuild --upgrade switch` 'ed and things stopped working. steps to reproduce: $ nix-build --argstr debug true --argstr cache $(./support/buildCache.sh) -A components.nucleus_find_contract (this command currently won't work on HEAD as Please note there is no mention git

Re: [Nix-dev] 6 month C4 adoption period

Aye, generally one hopes he rests in peace, but if the cryonics option was chosen then resting in piece is preferable. (I've interacted with him enough to know that he'd laugh like a drain at that and he really wouldn't want us getting all soppy on him.) Domen, just studying the C4 might be

Re: [Nix-dev] NixOS 16.09 released

Congratulations! ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] hydra.cryp.to will go offline by the end of this year

Never used it, but it very much inspired me! Well done on this work! /sjm ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOps usage survey.

Yes, you're deliberately breaking purity, but if you're going to be using it as part of the development infrastruction (he could mean many things, does he mean *code deployment infrastructure* or implicitly implying CDI and explicitly mentioning part of the development infrastructure.) If he

Re: [Nix-dev] NixOps usage survey.

On 6 Sep 2016 00:01, "Aloïs Cochard" wrote: > We do plan to use it for our development infrastructure You'll need to implement incremental recompilation (IR) to reduce compilation times. It's not too difficult to implement if you know _not_ to set nix.useSandbox = true;

Re: [Nix-dev] 6 month C4 adoption period

Was that offensive? Sorry I thought it was funny. Forgive me I shan't mention nipples again. On 1 Sep 2016 03:51, "Jookia" <166...@gmail.com> wrote: > On Thu, Sep 01, 2016 at 01:17:02AM +0800, stewart mackenzie wrote: > > Throw beers at Garbas! Shower him

Re: [Nix-dev] typed nix

P "Nix won't be complete until it has static typing." Nice. > highly nontrivial... No doubt, but having that speed up would be quite nice. Especially when using nix as a 'replacement' for make. It's the future! What would the language even look like? On 1 Sep 2016 03:29, "Vladimír Čunát"

Re: [Nix-dev] 6 month C4 adoption period

Just one? A lunatic, now two? A crowd? Three? A rebellion!? Resist your hatred for SJWs and wear the teeshirt for an email in support please. On 1 Sep 2016 01:48, "obadz" <obadz-...@obadz.com> wrote: > On Wed, Aug 31, 2016 at 6:13 PM, stewart mackenzie <setor

Re: [Nix-dev] 6 month C4 adoption period

Throw beers at Garbas! Shower him in the best beer possible! *Garbas rubs his nipples* On 1 Sep 2016 01:06, "zimbatm" wrote: > > Related to the original rust frustration, Garbas has started the https://github.com/garbas/nixpkgs-mozilla repo where Mozilla stuff is being

Re: [Nix-dev] 6 month C4 adoption period

I'm the canary in this goldmine, and this canary is dead. What I'm about to describe is Amdahl's law biting the ass harder of maintainers as nixpkgs grows in size. It's the reason why maintainers are rudely closing PRs, it's the reason why maintainers are cutting corners themselves yet expect

Re: [Nix-dev] rustc failure on nix only?

On 31 Aug 2016 02:01, "Matthias Beyer" wrote: > We fixed that in [650] which allowed beta to fail and we reverted that > patch in [655] as beta was updated and builds now. okay, thanks. Seems like the new parsers for semver were throwing a tantrum? I'll take a closer look

Re: [Nix-dev] 6 month C4 adoption period

On Tue, Aug 30, 2016 at 8:02 AM, Shea Levy wrote: > globin missed the fact that the naming convention is messing up the > lowPrio logic, and your original PR had nothing to do with that. If rust > were named properly, your fix would be wrong. What is the exact naming scheme

Re: [Nix-dev] Including "beta" or "unstable" identifiers in package names?

Trying to understand your email: in development/compilers/rust beta.nix: current behaviour: the name "beta" is already part of the version -> see "shortVersion" "... rustc = callPackage ./rustc.nix { shortVersion = "beta-2016-08-17"; ..."

Re: [Nix-dev] 6 month C4 adoption period

rust is a fast moving target, I don't want too much breakage. Recently upstream decided to shove experimental features into nightly releases (ie the allocator we're using which broke our build), this would cause huge breakage and annoyance ameliorating issues. It's better to keep lockstep with

Re: [Nix-dev] 6 month C4 adoption period

Sorry guys for showing my anger. Shea, you're doing a great job and I rely on your great work all the time. Thanks ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

Okay, then I'm absolutely boggled as to why each and every time I update I have recompile rustBeta.rustc then rustUnstable.rustc. I've literally been using nix-build ... -I nixpkgs=https://github.com/NixOS/nixpkgs-channels/archive/125089b6bd360c82cf986d8cc9b17fc2e8ac.tar.gz for more than a

Re: [Nix-dev] 6 month C4 adoption period

I just want this issue resolved. Every time I update / upgrade I recompile rustBeta then rustUnstable and it results in 1/2 day lost. This has happened frequently, recently as rustUnstable and rustBeta have been broken for a long time. (ie days have been lost finding working revs then compiling

Re: [Nix-dev] 6 month C4 adoption period

> adversely affect nix-env users in that case. How? ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

1+1=2 ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

Why is it like pulling teeth getting a simple pull request into nixpkgs? Something is _very_very_ broken people. Can we please fix this asap? No I don't want to hear bullshit reasons about keeping X Y Z maintainer's powers. ___ nix-dev mailing list

Re: [Nix-dev] 6 month C4 adoption period

in the beginning Shea... where it says "Goals" ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

On Tue, Aug 30, 2016 at 7:36 AM, Shea Levy wrote: > Perhaps they are not random if you know their origin or justification, > neither is given at the link though. Backtrack? Are you kidding me? ___ nix-dev mailing list

Re: [Nix-dev] 6 month C4 adoption period

*me ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

Sigh, random rules? Are you kidding me? Nevermind ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

due to multiple causes, but the latest straw on the camel's back is this pull request: https://github.com/NixOS/nixpkgs/pull/18101 ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] 6 month C4 adoption period

http://rfc.zeromq.org/spec:42/C4/ ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] 6 month C4 adoption period

Dear Nixers, Please may we start a C4 adoption period of 6 months then do a review after this? Kind regards Stewart ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] typed nix

per chance, is there work underway to make nix a typed language? kr/sjm ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Cross development for STM32

I'd really like to see a simple nix way to retarget derivations. So maybe `buildRustPackageForAndroid` or `buildRustPackageForSTM32`. or maybe buildRustPackage rec { name = "habitat-${version}"; version = "0.8.0"; target = "android"; ... } kr/sjm

Re: [Nix-dev] Hardening flags enabled by default

Huge kudos for this work guys! Excellent job and much appreciated! kr/sjm ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] bring into scope only required deps

Hello, The fractalide repository consists of N components that can be combined in Z different ways, called a subnet. A subnet represents a normal application you are used to executing. one tells the repository to build Z subnet via this command: $ nix-build [other args] --argstr subnet test_sjm

Re: [Nix-dev] Troubleshooting boot failures & rollbacks

Hi, try using `$ nixos-rebuild boot` to test out your system first. $ man nixos-rebuild ... boot Build the new configuration and make it the boot default (as with nixos-rebuild switch), but do not activate it. That is, the system continues to run the previous

Re: [Nix-dev] Windows updates

Aye, couldn't agree more with you. Kudos Eelco + contributors. On 7 Aug 2016 06:44, "zimbatm" wrote: > I'm staring at a spinning update indicator right now and all I wanted to > do is play a game on Windows. My wife purposely ignores the Windows updates > because it never

Re: [Nix-dev] Too many open issues

On 26 Jul 2016 22:22, "Wout Mertens" wrote: > Anybody up for C4? Finally some sanity! Yes! (FFS!) ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] nix as a library

Hmm on second thoughts, it's probably best to expose a nix-repl... it would be much more powerful. Thanks for than Vladimir! The user interface (ie compile button, whatever) could just write strings directly into the repl then linefeed, or you could just type it yourself. This would simplify

Re: [Nix-dev] nix as a library

Ohh exciting, I'll investigate :-) On Sun, Jul 10, 2016 at 12:25 AM, Vladimír Čunát wrote: > I think there are some APIs, but without guarantees of their stability: > libnixexpr.so libnixformat.so libnixmain.so libnixstore.so libnixutil.so

Re: [Nix-dev] nix as a library

Yeah, doable, but undesirable. Anyway, there is no API, i'll roll with calling executables. cheers Vladimír and zimbatm. On Sat, Jul 9, 2016 at 8:53 PM, Vladimír Čunát wrote: > Communication with a single instance of nix-repl might be more efficient > for some use cases, as it

Re: [Nix-dev] nix as a library

to hear if anyone else has this use case. On 9 Jul 2016 05:52, "Vladimír Čunát" <vcu...@gmail.com> wrote: > On 07/08/2016 12:53 PM, stewart mackenzie wrote: > > Are there any plans to make nix's functionality into a library so that > > a programmer could include th

[Nix-dev] nix as a library

Are there any plans to make nix's functionality into a library so that a programmer could include these libraries and affect change to the system via a program they made? (keeping a C ABI so that it'll work with libffi) kind regards /sjm ___ nix-dev

Re: [Nix-dev] hydra and nixos versions/commits at hydra.nixos.org

On 20 Jun 2016 17:53, "Domen Kožar" wrote: > I do agree it's additional work, but it's better than current state where we all maintain our Hydra from carefully picked commits and that's REALLY some additional work. Completely agree, it's kind of annoying going through the commits

Re: [Nix-dev] wordpress

I would switch in a heartbeat, using ubuntu, docker+virtualbox(inside virtualbox), virtualbox screen size issues, something called docker-machine I have to install manually into /usr/local/bin/ is not fun, and I'm actively suppressing grumpiness ... it's times like this I really appreciate nix. My

Re: [Nix-dev] wordpress

Naa time critical nature, just decided to spin up an ubuntu virtualbox. Ah I recognize the email address from the code you wrote :-) It would seem it's very centered around deploying stock releases not amenable for developing on wordpress. But I didn't get that far. Is there a faster route? On

Re: [Nix-dev] wordpress

Ah I see this: https://nixos.org/wiki/Wordpress I'll need to override the src of wordpress with my own version of wordpress. ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] wordpress

Hi, I see there's a wordpress package: https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/web-servers/apache-httpd/wordpress.nix There are no available wordpress attributes. How do I install wordpress? Kind regards Stewart ___

[Nix-commits] [NixOS/nixpkgs] 6b9c67: elm: 0.16.0 -> 0.17.0 (#15383)

Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: 6b9c67333fe62c38f1231dd5339b776c7c3d7172 https://github.com/NixOS/nixpkgs/commit/6b9c67333fe62c38f1231dd5339b776c7c3d7172 Author: Stewart Mackenzie <setor...@gmail.com> Date: 2016-05-11 (Wed, 11 Ma

Re: [Nix-dev] Nixbot - a little helper for pull requests

Hi Louis, I really hope the community rolls this out! Great work! /sjm On Fri, May 6, 2016 at 12:27 PM, Louis Taylor wrote: > code talks a lot louder than words: > > https://github.com/kragniz/nixbot ___ nix-dev mailing list

Re: [Nix-dev] Incremental recompilation

Isn't the simplest solution this: declare an output `outputs = ["out" "cache"];` now the word cache is hardcoded to create a directory /tmp/${derivation-name}-cache/ this name doesn't change. Now, in your derivation you can set the build tool (via env var if it supports that) to use this cache

Re: [Nix-dev] Incremental recompilation

It would be great to deploy the build product without the caches. Preferably expose the API as part of mkDerivation. This way I could pass in a 'develop' flag and if true, switch the cache on, else leave it off. Now I'll be able to deploy without caches. i.e.: if develop == true then cache =

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

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

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

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] break purity

Hi Oliver, Here is a minimal example stripped of all the other crap: https://github.com/fractalide/recompilation Cheers! /sjm ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] break purity

Okay, I'm having a few problems implementing this, if you wouldn't mind taking a look at this please: This is the package level default.nix which calls `buildFractalideComponent`: http://nixpaste.lbr.uno/ZTwRzV0-?nix Typically found here:

[Nix-dev] haskell structure for all of nixpkgs

Every time I come into contact with Peter Simon's work on Haskell I find myself growing green with envy. This approach seems to be a much better way of structuring nixpkgs in general. Now closure-size, a monumental job was undertaken successfully, what's the feasibility of implementing the

Re: [Nix-dev] break purity

Oliver, what is in prelude/shell.nix? (nix-build -E '(import prelude/shell.nix { nixpkgs = import /home/ollie/nixpkgs {}; }).dist') /sjm ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] break purity

/gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab > > On Fri, Apr 22, 2016 at 7:16 PM stewart mackenzie <setor...@gmail.com> > wrote: > >> Yeah, I'm not so sure it's possible because one cannot copy from a >> precompiled derivation output to a new derivation output, ie copy >> cros

Re: [Nix-dev] break purity

Yeah, I'm not so sure it's possible because one cannot copy from a precompiled derivation output to a new derivation output, ie copy cross derivation. As these multiple outputs (outputs = [x y z]) are seen as different derivations, this cannot happen right? Have you actually managed to make

Re: [Nix-dev] break purity

Ah, okay, I get your drift, I'll think how to make it succinct and tidy in the code :-) ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] break purity

Interesting Oliver, though this sounds like it'll throw a recursive error. I'll investigate! cheers! ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] break purity

Hi, I've got a bunch of artifacts being built in the /tmp/nix-build-component_name.drv-0 now I want to point the build manager, in this case cargo using the CARGO_TARGET_DIR env var to put the artifacts into a directory I make directly in the /tmp/target_${name} This way any further

Re: [Nix-dev] ANN: closure-size hitting master

On Wed, Apr 13, 2016 at 4:02 PM, Vladimír Čunát wrote: > What kind of numbers? (on what?) numbers on closure size reduction ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] ANN: closure-size hitting master

*rub hands together* great job! /sjm ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] Did we just get windows support for free?

Does windows support symlinks in non-administrator mode? ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

Re: [Nix-dev] NixOps rasta ;-)

Forgive my ignorance, but why does this brighten your day? ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev

[Nix-dev] download-from-binary-cache.pl: still waiting for ... is chewing time.

This is quite annoying, I'm waiting about 30 seconds or more each time I want to recompile the project and the network is flaky. Is there a way to disable this cache.nixos.org/.narinfo seek? ``` $ nix-build --argstr debug true --argstr subnet example_wrangle download-from-binary-cache.pl: still

  1   2   3   >