- Sep 16, 2014
-
-
Eelco Dolstra authored
-
Eelco Dolstra authored
-
Eelco Dolstra authored
-
- Aug 28, 2014
-
-
Eelco Dolstra authored
I don't think it's a good idea to use allowedRequisites for stdenv, so don't mention it here.
-
Eelco Dolstra authored
-
Gergely Risko authored
-
- Aug 27, 2014
-
-
Mikey Ariel authored
-
- Aug 23, 2014
-
-
Gergely Risko authored
-
- Aug 12, 2014
-
-
Eelco Dolstra authored
-
- Aug 04, 2014
-
-
Eelco Dolstra authored
-
- Jul 24, 2014
-
-
Eelco Dolstra authored
These are too difficult to implement via nix-store --serve. ‘--show-progress’ could be re-implemented fairly easily via a sink/source wrapper class.
-
- Jul 17, 2014
-
-
Eelco Dolstra authored
-
Eelco Dolstra authored
‘trusted-users’ is a list of users and groups that have elevated rights, such as the ability to specify binary caches. It defaults to ‘root’. A typical value would be ‘@wheel’ to specify all users in the wheel group. ‘allowed-users’ is a list of users and groups that are allowed to connect to the daemon. It defaults to ‘*’. A typical value would be ‘@users’ to specify the ‘users’ group.
-
- Jul 16, 2014
-
-
Eelco Dolstra authored
-
- Jul 04, 2014
-
-
Eelco Dolstra authored
Fixes #294.
-
- Jul 03, 2014
-
-
Eelco Dolstra authored
-
- Jun 27, 2014
-
-
Paul Colomiets authored
-
- May 26, 2014
-
-
Adam Szkoda authored
-
- May 21, 2014
-
-
Eelco Dolstra authored
If a build log is not available locally, then ‘nix-store -l’ will now try to download it from the servers listed in the ‘log-servers’ option in nix.conf. For instance, if you have: log-servers = http://hydra.nixos.org/log then it will try to get logs from http://hydra.nixos.org/log/<base name of the store path>. So you can do things like: $ nix-store -l $(which xterm) and get a log even if xterm wasn't built locally.
-
- May 13, 2014
-
-
Charles Strahan authored
-
- May 02, 2014
-
-
Eelco Dolstra authored
-
- Apr 28, 2014
-
-
Charles Strahan authored
-
- Apr 25, 2014
-
-
Eelco Dolstra authored
-
- Apr 15, 2014
-
-
Ricardo M. Correia authored
The option '--delete-generations Nd' deletes all generations older than N days. However, most likely the user does not want to delete the generation that was active N days ago. For example, say that you have these 3 generations: 1: <30 days ago> 2: <15 days ago> 3: <1 hour ago> If you do --delete-generations 7d (say, as part of a cron job), most likely you still want to keep generation 2, i.e. the generation that was active 7 days ago (and for most of the past 7 days, in fact). This patch fixes this issue. Note that this also affects 'nix-collect-garbage --delete-older-than Nd'. Thanks to @roconnor for noticing the issue!
-
- Apr 11, 2014
-
-
Eelco Dolstra authored
-
- Apr 10, 2014
-
- Apr 09, 2014
-
-
Eelco Dolstra authored
Grmbl...
-
- Apr 08, 2014
-
-
Eelco Dolstra authored
-
Eelco Dolstra authored
-
Eelco Dolstra authored
-
- Apr 07, 2014
-
-
Eelco Dolstra authored
-
- Apr 04, 2014
-
-
Eelco Dolstra authored
-
Eelco Dolstra authored
-
- Mar 29, 2014
-
-
Ricardo M. Correia authored
-
Ricardo M. Correia authored
It will delete all generations older than the specified number of days.
-
- Mar 12, 2014
-
-
Eelco Dolstra authored
-
Eelco Dolstra authored
-
Eelco Dolstra authored
-
- Mar 11, 2014
-
-
Eelco Dolstra authored
-
Shea Levy authored
-