Hi All,
Eelco has merged the systemd upgrade, so I've created the 14.04 branch.
Now it's time to start seriously testing this, so if you haven't yet
please try building your systems against the branch[2]! Aside from
#1665[2], which just needs to be brought up to date, only bug fixes
should now be
And there's now a jobset:
http://hydra.nixos.org/jobset/nixos/release-14.04
On Mon, Apr 21, 2014 at 05:32:34AM -0400, Shea Levy wrote:
Hi All,
Eelco has merged the systemd upgrade, so I've created the 14.04 branch.
Now it's time to start seriously testing this, so if you haven't yet
please
Greetings,
I have been planning to move to NixOS for quite a few months now but
only yesterday I finally clobbered my old /. Like many others, I'm a
Haskeller looking for a better development environment than we can
sanely achieve with cabal sandboxes.
Anyway, to the point. I have a few
If you want to do a lot of changes or always want to use the newest
versions of things without waiting for them to appear in the channel
(which may take a few days), you probably want to use a checkout
instead of the channel. This can be achieved with an environment
variable:
$ echo $NIX_PATH
On 04/21/2014 02:35 PM, Aristid Breitkreuz wrote:
If you want to do a lot of changes or always want to use the newest
versions of things without waiting for them to appear in the channel
(which may take a few days), you probably want to use a checkout
instead of the channel. This can be
Remove the symlink channels_root from your ~/.nix-defexpr/ directory
and add a new symlink to your nixpkgs checkout. Like this:
$ ll ~/.nix-defexpr/pkgs
lrwxrwxrwx 1 aristid users 10 22. Mär 18:22
/home/aristid/.nix-defexpr/pkgs - ../nixpkgs
To use 32-bit software, do NOT change your entire
Hi all,
I missed that kde hadn't been merged yet, so please ignore this for now.
We will be force pushing to release-14.04 when it is actually ready, so
please continue treating master as we have been for the past few weeks.
Sorry!
~Shea
On Mon, Apr 21, 2014 at 05:40:31AM -0400, Shea Levy
On Mon, Apr 21, 2014 at 4:23 PM, Mateusz Kowalczyk
fuuze...@fuuzetsu.co.ukwrote:
nix-channel --add http://nixos.org/channels/nixos-unstable nixos
seems to work but is probably not what I want (getting few-minutes-old
fixes from nixpkgs git repository).
There is a thing called Hydra. It
On Mon, Apr 21, 2014 at 4:44 PM, Mateusz Kowalczyk
fuuze...@fuuzetsu.co.ukwrote:
How can I get it to affect nix-env too? What is the way to set this
globally, for all users? Namely, for my use-case, I'd like both root and
my own user to use this checkout.
Just set NIX_PATH system-wide
And the man tells us that `nix-env` uses `~/.nix-defexpr` as the default
expression, so adjust it accordingly.
--
Кирилл Елагин
On Mon, Apr 21, 2014 at 5:04 PM, Kirill Elagin kirela...@gmail.com wrote:
On Mon, Apr 21, 2014 at 4:44 PM, Mateusz Kowalczyk
fuuze...@fuuzetsu.co.uk wrote:
How
On 21 April 2014 14:56, Kirill Elagin kirela...@gmail.com wrote:
On Mon, Apr 21, 2014 at 4:23 PM, Mateusz Kowalczyk fuuze...@fuuzetsu.co.uk
wrote:
[...]
* How can I find out more about packages? For example, I'd like to query
a package of a license, or to see its .nix file. Someone told me on
If there was a way to
1. run nix-repl non-interactively,
2. list variables in scope
that would be a fine replacement for grepping and opening files…
Something like `nix-repl ':l nixpkgs; :scope' | grep foo` and `nix-repl
':l nixpkgs; :p foo.meta`.
--
Кирилл Елагин
On Mon, Apr 21, 2014 at
On 21 April 2014 15:35, Kirill Elagin kirela...@gmail.com wrote:
If there was a way to
1. run nix-repl non-interactively,
2. list variables in scope
that would be a fine replacement for grepping and opening files…
Something like `nix-repl ':l nixpkgs; :scope' | grep foo` and `nix-repl
':l
Right, pretty cool, but still needs a sane frontend. I mean, JSON is way
better than, say, XML, but…
And the problem with nix-env is that it's damn slow (not as slow as
`emerge` of course, but way slower than `eix`).
I was going to write something like `eix` for Nix but unfortunately I don't
have
On 04/21/2014 04:34 PM, Kirill Elagin wrote:
Right, pretty cool, but still needs a sane frontend. I mean, JSON is way
better than, say, XML, but…
And the problem with nix-env is that it's damn slow (not as slow as
`emerge` of course, but way slower than `eix`).
I was going to write
Just rebooted.
kirrun@kirPC ~ [1001]% time nix-env -qa /dev/null
nix-env -qa /dev/null 1,66s user 0,49s system 7% cpu 29,789 total
kirrun@kirPC ~ [1003]% time nix-env -qa | /dev/null
nix-env -qa | /dev/null 1,42s user 0,28s system 99% cpu 1,706 total
30 seconds just to list available
On Mon, Apr 21, 2014 at 07:01:02PM +0400, Kirill Elagin wrote:
30 seconds just to list available packages. I guess, then files got
buffered and things become better.
Well that's comparable to eix except that when you are looking for a
specific package it is not necessary to go through _all_ of
Attached are 2 patches to update the version of texlive (old version files are
not available on Debian server anymore) and correct the patch hash in
libarchive.
From 3120977aac2c55707e4413d3d21f15c5851ccdb1 Mon Sep 17 00:00:00 2001
From: Karn Kallio kkal...@skami.org
Date: Mon, 21 Apr 2014
On 04/21/2014 05:52 PM, Karn Kallio wrote:
correct the patch hash in libarchive.
Unfortunately, github periodically changes output even for raw diffs
(not just raw patches). I'm including the patch in nixpkgs. (f3ec500)
I was unable to do it without hash change. Even if I added binary equal
19 matches
Mail list logo
