Apparently it's because I'm running KDE.
KDE sets environment.pathsToLink = [ "/share" ];
https://github.com/NixOS/nixpkgs/blob/788800e437c4a0a25d95e217540bded68804b25e/nixos/modules/services/x11/desktop-managers/kde4.nix#L156
{:akward penguin:}
I feel like we should give in a make "/share" pa
On Thu, Oct 15, 2015 at 3:58 AM, Peter Simons wrote:
> But how many people understand "callPackage"?
Interesting question. The commit logs suggest between 10-20 people could
write it themselves.
Arguably everyone who has read
http://lethalman.blogspot.com/2014/09/nix-pill-13-callpackage-design-p
Pushed in 07372d04a24cd431a4694e6a4182b91396482806.
___
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
---
pkgs/tools/networking/ripmime/default.nix | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pkgs/tools/networking/ripmime/default.nix
b/pkgs/tools/networking/ripmime/default.nix
index d9445b7..fd5964c 100644
--- a/pkgs/tools/networking/ripmime/default.nix
+++ b/pkgs/tool
The Problem
---
A lot of effort goes into curated package sets like Stackage, but even
so we can compile only ~50% of the packages available from Hackage. It
appears to be the nature of the game: when lens 2.x comes out with a
fundamentally new API, then some packages will adopt the new ve
I tried the approach you linked, though neovim doesn't get any plugins
or RC linked in...
On 15-10-2015 11:34:19, Rok Garbas wrote:
>
> the neovim expression already supports this via more general '.override'
> function. my example is here:
> https://github.com/garbas/dotfiles/blob/master/pk
Mathnerd314 writes:
>> "haskellPackages" provides the foundation that other package sets
>> override according to their needs. As of today, this approach
>> requires approximately 25,000 overrides.
>
> The vast majority are [...] auto-generated and repeated in each LTS
> file. Excluding thos
the neovim expression already supports this via more general '.override'
function. my example is here:
https://github.com/garbas/dotfiles/blob/master/pkgs/default.nix#L83
Quoting Matthias Beyer (2015-10-14 20:40:15)
> Hi,
>
> the neovim derivation seems to be customizable like the
> vim_co
Hi William,
>> We still don't have convincing answers to questions like: how do I
>> compile my package with profiling support?
>
> I thought we already have fairly straightforward support for this via
> overrides? I have been using this method:
>
> https://gist.github.com/jb55/af8b095b3ad9
