Re: [Nix-dev] Including SSL certificates with NixOS configuration
On Tue, Sep 13, 2016 at 1:12 PM, Wilhelm Schusterwrote: > Can I use it to deploy onto an already existing NixOS instance? Yes, this is possible with targetEnv = "none": deployment = { targetEnv = "none"; targetHost = "myhost.example.com"; }; ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev
[Nix-commits] [NixOS/nixpkgs] f0f917: elm: Constrain aeson-pretty to <0.8 (#17511)
Branch: refs/heads/master Home: https://github.com/NixOS/nixpkgs Commit: f0f917201778148db279681b3eec42b70355e0a4 https://github.com/NixOS/nixpkgs/commit/f0f917201778148db279681b3eec42b70355e0a4 Author: Brad Ediger <b...@bradediger.com> Date: 2016-08-04 (Thu, 04 Aug 2016) Changed paths: M pkgs/development/compilers/elm/packages/elm-compiler.nix M pkgs/development/compilers/elm/packages/elm-package.nix Log Message: --- elm: Constrain aeson-pretty to <0.8 (#17511) https://github.com/elm-lang/elm-compiler/pull/1431 ___ nix-commits mailing list nix-comm...@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-commits
Re: [Nix-dev] Source URL breakage - please can we improve the determinism
We have also run into this issue with spotify and similar unfree / non-redistributable packages. The consensus last time we had upstream URLs disappear was that it is not permissible to cache and redistribute even the original source. There may be a partial solution for this problem, but it will not solve the issue for nonfree packages. On Sun, May 8, 2016 at 10:11 AM Игорь Пашевwrote: > Can't be nix cache used for this? Source tarballs are kind of derivation > too. > ___ > nix-dev mailing list > nix-dev@lists.science.uu.nl > http://lists.science.uu.nl/mailman/listinfo/nix-dev > ___ nix-dev mailing list nix-dev@lists.science.uu.nl http://lists.science.uu.nl/mailman/listinfo/nix-dev