Kirill,
thank you again
2015-03-02 9:29 GMT+01:00 Kirill Elagin <kirela...@gmail.com>:
> That’s because you now have the `nixos` expression instead of `nixpkgs`
> but it is still misleadingly called `nixpkgs`.
>
> I suggested this to you somewhere mid-February just as the quickest
> solution to get stable nixpkgs because you wanted sass and there were some
> Ruby-related changes going on in master.
>
> Again, the quickest solution now is to replace the first line with:
>
> ~~~~
> let pkgs = (import <nixpkgs> {}).pkgs;
> ~~~~
>
> But it’s probably better to figure things out.
> First of all, it might be the case that Ruby things on master stabilised
> and you’ll be able to switch back to unstable and get sass working. I have
> no idea, as I don’t use Ruby, we need an advise from someone who knows
> what’s going on with Ruby in nixpkgs.
>
This is probably the most interesting option. Does anyone here know about
Ruby on nixpkgs ?
> Another posibility is to be honest and rename the stable nixos channel to
> `nixos` and then set `$NIX_PATH` to
> `nixpkgs=$HOME/.nix-defexpr/channels/nixos/nixpkgs`. There might be a
> better way to do this with `~/.nix-defexpr` but I actually still have no
> idea how it works, so we need someone else’s advice here again.
>
I didn't understand what you meant here. Probably because I was missing a
general view of the architecture, I guess. Sorry for the fuss.
I hadn't understood what the relationship between the channel name and the
NIX_PATH was.
Now I thing I get it ;-)
_______________________________________________
nix-dev mailing list
nix-dev@lists.science.uu.nl
http://lists.science.uu.nl/mailman/listinfo/nix-dev
