| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22941
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22939
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22937
|
|
|
|
|
|
|
| |
The nbd client needs kernel support and is available only on Linux, but
the server process ought to work in all POSIX'ish environments.
svn path=/nixpkgs/trunk/; revision=22936
|
|
|
|
|
|
| |
test suite failure on hydra: http://hydra.nixos.org/build/518375
svn path=/nixpkgs/trunk/; revision=22935
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22934
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22933
|
|
|
|
|
|
| |
qt4 somehow depends on libcap which is linux only
svn path=/nixpkgs/trunk/; revision=22932
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22931
|
|
|
|
|
|
| |
I don't want kde-4.5 to be visible for nix-env, but I want hydra to build it
svn path=/nixpkgs/trunk/; revision=22930
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22927
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22925
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22924
|
|
|
|
|
|
|
| |
The latest version, 2.11, doesn't compile on Darwin. The build
expression for 2.11 is still still available in "latest.nix".
svn path=/nixpkgs/trunk/; revision=22923
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22922
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22921
|
|
|
|
|
|
|
| |
The tests suite succeeds fine on Linux/x86. Let's see what happens on
other platforms.
svn path=/nixpkgs/trunk/; revision=22920
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22919
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22918
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22914
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22913
|
|
|
|
|
|
| |
linker of glibc on mips (specifically ld.so.1, and not ld-*.so.? as we had before)
svn path=/nixpkgs/trunk/; revision=22912
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22910
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22909
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22908
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22907
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22906
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22905
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22903
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22901
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22898
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22897
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22896
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22895
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22894
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22893
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22892
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22891
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22890
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22889
|
|
|
|
|
|
| |
renaming it to zipTwoLists
svn path=/nixpkgs/trunk/; revision=22887
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`callPackage' was described here:
http://www.mail-archive.com/nix-dev@cs.uu.nl/msg02624.html
It allows all-packages.nix to be shortened significantly (from 10152
to 6980 lines) by automatically filling in package functions'
required arguments from `pkgs'. That is, a function
{ stdenv, fetchurl, libfoo, libbar }: ...
can now be called as
callPackage ./<bla>.nix { };
rather than
import ./<bla>.nix {
inherit stdenv fetchurl libfoo libbar;
};
This reduces boring typing work when adding a dependency and reduces
the number of trivial commits to all-packages.nix.
Overrides or arguments that don't exist in `pkgs' can be passed
explicitly, e.g.,
callPackage ./<bla>.nix {
libfoo = libfoo_1_2_3;
};
The conversion was done automatically with a magic Perl regexp. I
checked that `nix-env' produces the same results before and after
(except for three packages that depend on webkit, which uses
deepOverride).
`callPackage' applies `makeOverridable' automatically, so almost
every package now exports an `override' function.
There are two downsides to using callPackage:
- Evaluation is a bit slower (about 15% on `nix-env -qa --drv-path
\*').
- There can be unexpected results for functions that have default
argument values. For instance, a function
{ libfoo ? null }: ...
called using `callPackage' will be passed a `libfoo' argument
provided that `pkgs.libfoo' exists. If this is used to control
whether a package has to have a certain dependency, you need to
explicitly write:
callPackage ./<bla>.nix {
libfoo = null;
};
svn path=/nixpkgs/trunk/; revision=22885
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22882
|
| |
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22876
|
|
|
|
|
|
|
| |
The README contains documentation that is useful in addition to the man
pages.
svn path=/nixpkgs/trunk/; revision=22875
|
| |
|
| |
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22870
|
|
|
|
| |
svn path=/nixpkgs/trunk/; revision=22867
|