You can do thing like this in your configuration.nix:
```
let pkgs-16_03 = import (fetchTarball
http://nixos.org/releases/nixos/16.03-beta-small/nixos-16.03.252.dc3073b/nixexprs.tar.xz)
{}; in {
environment.systemPackages = [ pkgs-16_03.w3m ];
}
```
That basically brings in the nixpkgs
Nix allows you to have multiple versions of one package, but each version
can require it's specific build recipe.
nixpkgs - is a place for latest versions of packages, and, pragmatically,
for most used non-latest versions. The place for all packages of all
versions is currently vacant.
Given
On 08/12/2016 02:58 AM, Roger Qiu wrote:
Nix is based on content addressing. To install a specific version of a
package, just pick a version, fix the content address, and install it!
[...]
or if a previous (or newer) revision of nixpkgs had the
package, then you load that package set and point
Nix is based on content addressing. To install a specific version of a
package, just pick a version, fix the content address, and install it!
However nixpkgs is a community effort in creating a standard default
package set. This means the community decides to write nix expressions for
the
Nick,
I think the concept here is that:
- in nixpkgs there are only latest versions (in few cases more) of the
software, because it's hard to maintain huge set of packages with such a
small community (comparing to debian, redhat or other distros)
- nix is created to extend in mind, I find it lot
If you know the path of the package the easiest way is `nix-env -i
/nix/store/...`.
For installing a package by previous version number I don't think there
is an easy way to do it. (Except for some packages were different
versions are available in nixpkgs). This is partially because "version"
in
