On 06/19/2013 06:26 AM, Corey O'Connor wrote:
Should this be a transparent upgrade for a nixos system running 1.5.2?
I'm quite sure it was intended so.
Since this change I've been unable to nixos-rebuild switch --upgrade or
use nix-env. They both seem to get stuck querying the binary cache.
Hi Eelco,
Changed paths:
M modules/programs/bash/profile.sh
Log Message:
---
Unconditionally add ~/bin to $PATH
here we go again. :-( I thought we had reached a consensus on this issue
a long time ago?
| commit 8eca4db54aed5b0969a2f0c56e2736cb3c8a078a
| Author: Peter
https://github.com/NixOS/nixos/pull/138
It allows to define
bash.availableFeatures.user_bin.env_code = PATH=~/bin:$PATH;
in a configuration.nix file - and users can opt out from such snippets.
I don't want to say the patch is perfect, but eventually its worth
thinking about such composable
On Tue, Jun 18, 2013 at 11:34 PM, Vladimír Čunát vcu...@gmail.com wrote:
I don't know why this happens, the new cache on Amazon has worked very
well for me so far (although I haven't used it so much yet). Note that the
bump to 1.5.3 is NOT in binary cache yet (in the statically served one).
