Re: [Nix-dev] NixON initiative

You mean you don't like naming it after everyone's favorite US president? :) > On Feb 28, 2016, at 09:54, deCube.net | Danny Wilson wrote: > > How about NEON > > Nix Expression Object Notation > >> On 28 feb. 2016, at 15:49, stewart mackenzie wrote: >>

Re: [Nix-dev] Signed git

For anyone not following the issue tracker, there's a related discussion going on there: https://github.com/NixOS/nix/issues/613 On Fri, Feb 26, 2016 at 7:06 AM, Eelco Dolstra wrote: > Hi, > > On 26/02/16 11:06, Vladimír Čunát wrote: > > > That is, assuming the ISOs

Re: [Nix-dev] NixOS 16.03 branch-off time in 10 days

I'll take anything that will get closure-size merged in ASAP :) On Fri, Feb 19, 2016 at 8:01 AM, Thomas Strobel < 4ZKTUB6TEP74PYJOPWIR013S2AV29YUBW5F9ZH2F4D5UMJUJ6S@hash.domains> wrote: > Hi, > > what about branching off 16.03 by merging the closure-size branch, and > then taking the commit just

Re: [Nix-dev] NixCon St. Petersburg 2016

First off, thanks for offering to organize it. It's a big undertaking and you're offering a huge gift to the community. Unfortunately, my big concern (outside of my own enthusiasm for being a tourist in Russia) is around the LGBT situation there. I'm sure there are many people in our community who

Re: [Nix-dev] nodejs 5.x failing on darwin

about this. Until then, thanks for your > swift response. > > br, > Tobi > > Sent from my iPhone > > On 18 Jan 2016, at 22:51, Daniel Peebles <pumpkin...@gmail.com> wrote: > > I think Jude Taylor (@pikajude) and I have historically been the main > "darwin

Re: [Nix-dev] nodejs 5.x failing on darwin

I think Jude Taylor (@pikajude) and I have historically been the main "darwin fixer-uppers", but it's a bit tiring when everything's shifting under us all the time. Anyway, I'll try to take a look at how to fix the patch later tonight, but in the longer run the bottleneck on the two of us isn't

Re: [Nix-dev] Flattening pkgs tree in nixpkgs/pkgs

Adding another -1 to flattening all directories. I think the categories/directories could make more sense than they do today, and that all-packages.nix should be abolished (use builtins.readDir by default and a manual overrides file where necessary), but throwing away all structure because it

Re: [Nix-dev] Preference for building from source

As far as the particular examples of Eclipse and Gradle, I think the issue is that building java packages (especially big complicated ones like those) is currently rather painful in Nix. Unlike many other language ecosystems, we don't have a wealth of prepackaged libraries and dependencies for the

Re: [Nix-dev] How can we make import-from-derivation more useful?

.@shealevy.com> wrote: > >> https://github.com/NixOS/nix/pull/31 may be relevant. >> >> On 2015-12-28 11:10, Daniel Peebles wrote: >> > A few days ago, I proposed importing from a derivation [1] to save us >> > from having to manually manage autogenera

Re: [Nix-dev] Hydra builds for Mac OS X

They're so fast that they emptied the queue immediately! :) On Mon, Jan 4, 2016 at 4:02 PM, Christian Theune wrote: > Sweet! > > Although I’m surprised that the Mac OS X queue is empty right now =) > > Christian > > On 04 Jan 2016, at 19:40, Rob Vermaas

[Nix-dev] How can we make import-from-derivation more useful?

A few days ago, I proposed importing from a derivation to save us from having to manually manage autogenerated firefox/thunderbird fixed-output derivaiton hash files and junk up the nixpkgs repository with them. In response,

Re: [Nix-dev] Set up a Sufficiently Powerful Build Farm

y need to recompile the world if they get anywhere near master. On Tue, Dec 22, 2015 at 9:16 AM, Christian Theune <c...@flyingcircus.io> wrote: > Hi, > > On 22 Dec 2015, at 14:57, Daniel Peebles <pumpkin...@gmail.com> wrote: > > I spoke with Rob Vermaas about donati

Re: [Nix-dev] Publish All of Hackage

> > The downside of this approach is that generating the entire Haskell > package set is actually kind of expensive, and we probably wouldn't want > to impose those costs onto random users who just wants to have XMonad > for their window manager > Couldn't the derivation we're importing from be

Re: [Nix-dev] Feature request: replace the Darwin stdenv with the pure Darwin stdenv

with the pure one. Yes, there will be some short- and medium-term pain during the switch, but there already is with the El Capitan upgrade. On Fri, Oct 2, 2015 at 3:01 AM, Michael Sperber <sper...@deinprogramm.de> wrote: > > Daniel Peebles <pumpkin...@gmail.com> writes: >

Re: [Nix-dev] Feature request: replace the Darwin stdenv with the pure Darwin stdenv

Probably obvious, but I'm in favor of switching/merging :) Given how badly this 10.11 change affected Homebrew too, this might be enough of a kick to get a bigger and more active Darwin constituency in Nix. On Wed, Sep 30, 2015 at 3:48 PM, Jude wrote: > Hi all, pikajude here,

Re: [Nix-dev] Logo improvement ideas

Does anyone feel like the S in the NixOS typeface in the new logos is too narrow? I love the new graphical logo proposals, but the typeface bothers me a little. On Fri, Sep 11, 2015 at 10:14 AM, Tim Cuthbertson wrote: > I've now updated this form with the remaining options, so

[Nix-dev] Jar files

Hi all, We don't have much of a Java presence in Nixpkgs, but I was thinking of growing it. This leads to what seems like a bit of a thorny issue: most java code is distributed in jars, which are glorified zip files. Can anyone see the problem? The one I'm afraid of is one of runtime

Re: [Nix-dev] Problem when running some JVM librairies under NixOS

Yeah, I'm pretty sure the dynamic linker is the issue here. Alois, you'll probably have to unpack the jar, patchelf it to point at the proper one, and then repack the jar. Or just have it the whole thing depend explicitly on a proper Nix store path :) On Fri, Aug 28, 2015 at 8:47 AM,

Re: [Nix-dev] What is the end game?

. On 25.08.2015 17:42, Daniel Peebles wrote: Hi all, Let's say for a moment that Nix has taken over the world, and every open source project now includes a default.nix or release.nix in its repo root. What does nixpkgs look like in this world? Does it duplicate the individual package .nix

[Nix-dev] Ideas for systematically avoiding unwanted runtime dependencies

Hi all, As I build more and more images with Nix, I'm becoming acutely aware of our awkwardly large runtime closures (often filled with irrelevant packages), and I'm wondering if people have ideas for how to avoid it. I've posted an issue[1] related to this in the past but figured I'd ask on the

[Nix-dev] What is the end game?

Hi all, Let's say for a moment that Nix has taken over the world, and every open source project now includes a default.nix or release.nix in its repo root. What does nixpkgs look like in this world? Does it duplicate the individual package .nix files in their respective repositories? Does it

Re: [Nix-dev] i686 Builds?

Is there a way to get stats on which binary cache hashes are being retrieved? Would be interesting to see what percentage is i686 and scale build shares accordingly. On Mon, May 11, 2015 at 6:36 PM, Shea Levy s...@shealevy.com wrote: Hi all, Do we still have users running 32-bit machines? It

Re: [Nix-dev] modularize all-packages?

I thought that at some point there was an effort to autogenerate (dynamically, so not nix codegen) the list from readDir. If not, it seems like the majority of packages could work that way, along with room to override where necessary. On May 7, 2015, at 08:10, Wout Mertens

Re: [Nix-dev] modularize all-packages?

, 2015 at 2:29 PM Daniel Peebles pumpkin...@gmail.com wrote: I thought that at some point there was an effort to autogenerate (dynamically, so not nix codegen) the list from readDir. If not, it seems like the majority of packages could work that way, along with room to override where necessary

Re: [Nix-dev] modularize all-packages?

What went wrong? I think that's what I was thinking of On May 7, 2015, at 08:50, Eelco Dolstra eelco.dols...@logicblox.com wrote: On 07/05/15 14:29, Daniel Peebles wrote: I thought that at some point there was an effort to autogenerate (dynamically, so not nix codegen) the list from

Re: [Nix-dev] symbola font expression

A little concerning that the tarball is changing under a given URL, since this means that at some point in the future this will break again (and that we lose history). Can we mirror it elsewhere or ask upstream to adopt a more packaging-friendly approach to releases? On Sun, Feb 8, 2015 at 2:27

Re: [Nix-dev] Please test NixOS/nixpkgs.git on darwin

I think we can pull it off this or next week, with a few people contributing to testing the semantically meaningful PRs we break into chunks. Fully agree on your proposed workflow, but I've been pretty undisciplined so far. For the current big merge, my plan was to break my history into major

Re: [Nix-dev] Please test NixOS/nixpkgs.git on darwin

, Shea Levy s...@shealevy.com wrote: Sure, tonight works. This sounds great! Besides the patches to cc-wrapper, are there any changes you expect to hit linux stdenv? On Feb 3, 2015, at 5:07 PM, Daniel Peebles pumpkin...@gmail.com wrote: I think we can pull it off this or next week

Re: [Nix-dev] Use Haskell for Shell Scripting

If only we had a way to produce multiple outputs from a single package... :) On Jan 31, 2015, at 07:22, Ertugrul Söylemez ert...@gmx.de wrote: There should be a pure library derivation and a separate compiler derivation. The former should be as small as possible. Ideally there would be

Re: [Nix-dev] Use Haskell for Shell Scripting

Yeah, was kidding around! On Jan 31, 2015, at 10:47, Ertugrul Söylemez ert...@gmx.de wrote: If only we had a way to produce multiple outputs from a single package... :) We have. The `derivation` function supports producing multiple outputs, and I'm sure that `mkDerivation` forwards this

Re: [Nix-dev] nix, Maven and JAR-files

Charles O'Farrell and I did some initial scoping out of what it would take to have a nice Java ecosystem in nix a few months ago but the efforts died down when I caught the nix-on-Darwin bug. I plan on getting back to it when I'm done and have a lot of ideas in the space. I'm on my phone now so

Re: [Nix-dev] Use Haskell for Shell Scripting

You linked to something from 2011. Since 7.8 (or perhaps earlier?), it's dynamically linked by default. On Fri, Jan 30, 2015 at 7:52 PM, Raahul Kumar raahul.ku...@gmail.com wrote: At this current point in time, GHC is packaged in a poor manner, with GHC being unbelievably huge. Dynamic linking

Re: [Nix-dev] FreeBSD Support

Our darwin nix efforts currently have a clang-based stdenv. There are vague plans to factor out the clang-ness from the darwin-ness, but apart from that, we've already made most of the changes to nixpkgs (in our fork, which we're merging back slowly) that allow it to build with clang. On Sat,

Re: [Nix-dev] clang-based stdenv for OSX Yosemite

Anyone interested in this project should join ##nix-darwin on freenode. There's still lots to do! On Mon, Nov 3, 2014 at 9:31 PM, Joel m...@joelt.io wrote: Daniel Peebles, John Wiegley, Eric Seidel, and myself have been working on a clang-based stdenv for OSX for the past few weeks. It is fully

Re: [Nix-dev] Package archeology in nixpkgs

/08/2014 04:31, Daniel Peebles wrote: I've had a sudden urge to do some Haskell archeology and that led me to a question about how we feel philosophically about keeping abandoned projects and old versions of live projects in nixpkgs. I think it could be valuable to preserve important pieces

[Nix-dev] Package archeology in nixpkgs

Hi all, I've had a sudden urge to do some Haskell archeology and that led me to a question about how we feel philosophically about keeping abandoned projects and old versions of live projects in nixpkgs. I think it could be valuable to preserve important pieces of Haskell history (and perhaps

[Nix-dev] RFC: three dying pull requests (let's keep them alive)

I've noticed a bit of a pattern recently on the nix github and wanted to try to stop it before Shea Levy decided this sort of work wasn't worth his time anymore. I'm not proposing that we insta-merge all his changes, but can anyone interested at least chime in with feedback so that these pull

[Nix-dev] NixOps targeting machines that only have Nix (not NixOS) on them?

I'm an extreme newbie, so apologies if this is already possible, but I couldn't find anything about it in the manual. Currently NixOps seems heavily geared (or designed around?) administering NIxOS boxes, which it's great at, but I need to deal with other OSes too. To support this, it seems like

<    1   2