The attached patch fixes the build of the pgadmin3 expression, which is
failing on the current master branch.
>From 6825999504000776df263aae4a0de9427be553af Mon Sep 17 00:00:00 2001
From: Karn Kallio
Date: Sat, 23 Apr 2016 23:05:43 -0430
Subject: [PATCH] pgadmin3 : fix the
Several phonon include paths reference the nonexistent include
directory "Phonon" which breaks the kde5 build. The attached patch
fixes these replacing them with the correct "phonon" include directory.
The phonon expression itself produces a "phonon" include directory, so
I have used that as
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:
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
On 04/23/2016 04:22 PM, Marc Weber wrote:
>> IIRC the wiki is read-only now on purpose. Its content is being (slowly)
>> reviewed and integrated into our documentation.
>> https://github.com/NixOS/nixpkgs/milestones/Move%20the%20wiki!
>
> It would not hurt adding comments to a wiki template:
>
>
> IIRC the wiki is read-only now on purpose. Its content is being (slowly)
> reviewed and integrated into our documentation.
> https://github.com/NixOS/nixpkgs/milestones/Move%20the%20wiki!
It would not hurt adding comments to a wiki template:
The wiki is readonly and will be integrated into
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
>On 04/23/2016 01:35 PM, Michael Raskin wrote:
>>> That’s what they always say right before they make a 10 person team
>>> work fulltime on a project. ;)
>>
>> Well, they have Bazel… And I have grounds to believe they are not going
>> to use Nix this year.
>
>Bazel's focus seems a little lower,
On 04/23/2016 01:35 PM, Michael Raskin wrote:
>> That’s what they always say right before they make a 10 person team
>> work fulltime on a project. ;)
>
> Well, they have Bazel… And I have grounds to believe they are not going
> to use Nix this year.
Bazel's focus seems a little lower, similar
>> - And I don't suppose I can deny being at Google, no, but this isn't a
>> Google project; I've just ended up using NixOS *everywhere* in my personal
>> life, so now I want monitoring. ;-)
>That’s what they always say right before they make a 10 person team
>work fulltime on a project. ;)
Well,
On 16-04-22 02:08pm, Svein Ove Aas wrote:
> - And I don't suppose I can deny being at Google, no, but this isn't a
> Google project; I've just ended up using NixOS *everywhere* in my personal
> life, so now I want monitoring. ;-)
That’s what they always say right before they make a 10 person team
On 16-04-22 06:33pm, Oliver Charles wrote:
> It's certainly possible, because I just did it with Haskell ;)
>
> https://gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab
Why do you need to put the atime two hours in the past?
Does cabal recompilation check for it in order to find out
On 04/23/2016 12:14 PM, Marc Weber wrote:
> I tried fixing the article but can no longer login.
IIRC the wiki is read-only now on purpose. Its content is being (slowly)
reviewed and integrated into our documentation.
https://github.com/NixOS/nixpkgs/milestones/Move%20the%20wiki!
--Vladimir
Those are my results
- python27.buildEnv worked
- nixos wiki: still contained the myEnv solution on the python page. I
guess that should be replaced by buildEnv for "my use case".
I tried fixing the article but can no longer login.
Trying to reset password yields "Error sending mail:
A completely different approach would be to somehow break up your big
build into multiple derivations. This thread reminded me of nix-make:
https://github.com/edolstra/nix-make/blob/master/examples/not-so-simple-header-auto/default.nix
--Vladimir
smime.p7s
Description: S/MIME Cryptographic
On 04/22/2016 08:33 PM, Oliver Charles wrote:
> It's certainly possible, because I just did it with Haskell ;)
>
> https://gist.github.com/ocharles/cbd5d7ce63bb570abb86e655f36435ab
Hehe, the classic Haskell approach: make the impurity explicit in order
not to actually break purity...
16 matches
Mail list logo