swendel/nixpkgs
1
0
Fork 0
mirror of https://github.com/SebastianWendel/nixpkgs.git synced 2024-09-29 00:20:19 +02:00
Code Issues Packages Projects Releases Wiki Activity
nixpkgs/pkgs/top-level/all-packages.nix

11724 lines
356 KiB
Nix
Raw Normal View History

* Merge all-packages.nix into all-packages-generic.nix. svn path=/nixpkgs/branches/usability/; revision=4765
2006-02-08 18:37:45 +01:00
/* This file composes the Nix Packages collection. That is, it
imports the functions that build the various packages, and calls
them with appropriate arguments. The result is a set of all the
packages in the Nix Packages collection for some particular
* Remove `customKernel' which is obsolete as far as I can tell. * Remove `sumTwoArgs' since it has no remaining callers. svn path=/nixpkgs/trunk/; revision=22797
2010-07-28 18:09:13 +02:00
platform. */
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
* Merge all-packages.nix into all-packages-generic.nix. svn path=/nixpkgs/branches/usability/; revision=4765
2006-02-08 18:37:45 +01:00
* Support different kinds of stdenvs on a particular system (like "i686-cygwin") by adding an argument "stdenvType" to specify which stdenv to use (like "i686-mingw"). svn path=/nixpkgs/trunk/; revision=6213
2006-08-23 17:58:54 +02:00
{ # The system (e.g., `i686-linux') for which to build the packages.
* __XXX primops are deprecated. svn path=/nixpkgs/trunk/; revision=15036
2009-04-14 15:59:45 +02:00
system ? builtins.currentSystem
* Converting packages. This is the minimal Nix stdenv for building the ATerm library. svn path=/nixpkgs/trunk/; revision=459
2003-11-02 18:42:19 +01:00
* Merge all-packages.nix into all-packages-generic.nix. svn path=/nixpkgs/branches/usability/; revision=4765
2006-02-08 18:37:45 +01:00
, # The standard environment to use. Only used for bootstrapping. If
# null, the default standard environment is used.
bootStdenv ? null
Set `noSysDirs' to `false' on non-GNU/Linux platforms.
2012-08-31 11:50:04 +02:00
, # Non-GNU/Linux OSes are currently "impure" platforms, with their libc
# outside of the store. Thus, GCC, GFortran, & co. must always look for
# files in standard system directories (/usr/include, etc.)
Remove support for the obsolete powerpc-darwin and i686-darwin platforms
2012-11-29 14:10:49 +01:00
noSysDirs ? (system != "x86_64-darwin"
Set `noSysDirs' to `false' on non-GNU/Linux platforms.
2012-08-31 11:50:04 +02:00
&& system != "x86_64-freebsd" && system != "i686-freebsd"
&& system != "x86_64-kfreebsd-gnu")
Darwin: Change `noSysDirs' to `false' by default. svn path=/nixpkgs/trunk/; revision=33911
2012-04-24 18:14:44 +02:00
* Merge all-packages.nix into all-packages-generic.nix. svn path=/nixpkgs/branches/usability/; revision=4765
2006-02-08 18:37:45 +01:00
# More flags for the bootstrapping of stdenv.
* The `patch' command is now part of stdenv, so it no longer needs to be passed to derivations that need to apply patches. * GCC 3.4 is now the default compiler (old GCC renamed to `gcc-3.3'). * The temporary GCCs built during the stdenvLinux bootstrap are now built without C++ support and without profiling. * Remove fixincl in GCC 3.4 to prevent a retained dependency on the previous GCC. * Always set $prefix in setup.sh, even when there is no configure script. svn path=/nixpkgs/trunk/; revision=1444
2004-09-18 19:23:18 +02:00
, gccWithCC ? true
, gccWithProfiling ? true
* Finally got stdenv-nix-linux working again. Still not perfect, though. * libxml2: upgrade to latest. * octavefront/rna: keep debug info. svn path=/nixpkgs/trunk/; revision=830
2004-03-11 18:26:14 +01:00
* Allow the Nixpkgs config to be passed as a function argument (rather than through ~/.nixpkgs/config.nix or $NIXPKGS_CONFIG). svn path=/nixpkgs/trunk/; revision=16861
2009-08-26 15:51:37 +02:00
, # Allow a configuration attribute set to be passed in as an
# argument. Otherwise, it's read from $NIXPKGS_CONFIG or
# ~/.nixpkgs/config.nix.
config ? null
* Fix Perl on FreeBSD. svn path=/nixpkgs/branches/stdenv-updates/; revision=19685
2010-01-26 19:10:59 +01:00
I made the whole nixpkgs dependencies available to the cross compiler, no needing to keep a new tree of expressions apart for the expressions to get cross-compiled. I changed the whole way of using cross compilation with nixpkgs, which before was done through a simple adapter. Now the adapter became complex, and I've tried to avoid the most obvious recursivities. For example, the fetchurl expression should never be cross-compiled, as the gmp, mpfr, and some others, like some ncurses, perl, ... I made overrided copies of those necessary as perlNoCross, ncursesNoCross, as stdenvNoCross, keeping in mind that the stdenv (capable of cross compilation) is built upon stdenvNoCross using an adapter. So, to cross compile, instead of building using "nixpkgs/default.nix", you should build with your own "myarchiteture.nix", which should have contents like these, for example: import /etc/nixos/nixpkgs/default.nix { crossSystem = { config = "armv5tel-unknown-linux-gnueabi"; bigEndian = false; arch = "arm"; float = "soft"; }; } svn path=/nixpkgs/branches/stdenv-updates/; revision=18398
2009-11-17 23:58:48 +01:00
, crossSystem ? null
Changing the way 'platform' gets into all-packages, allowing setting it in nixpkgs config. svn path=/nixpkgs/branches/stdenv-updates/; revision=23635
2010-09-03 23:34:49 +02:00
, platform ? null
* Merge all-packages.nix into all-packages-generic.nix. svn path=/nixpkgs/branches/usability/; revision=4765
2006-02-08 18:37:45 +01:00
}:
* Updated to reflect the changes to the grammar. svn path=/nixpkgs/trunk/; revision=464
2003-11-03 11:22:00 +01:00
* Use all those new packages. svn path=/nixpkgs/trunk/; revision=545
2003-11-25 19:02:05 +01:00
Changing the way 'platform' gets into all-packages, allowing setting it in nixpkgs config. svn path=/nixpkgs/branches/stdenv-updates/; revision=23635
2010-09-03 23:34:49 +02:00
let config_ = config; platform_ = platform; in # rename the function arguments
* Allow the Nixpkgs config to be passed as a function argument (rather than through ~/.nixpkgs/config.nix or $NIXPKGS_CONFIG). svn path=/nixpkgs/trunk/; revision=16861
2009-08-26 15:51:37 +02:00
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
let
Fix references to pkgs/lib
2013-09-30 22:43:34 +02:00
lib = import ../../lib;
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
# The contents of the configuration file found at $NIXPKGS_CONFIG or
# $HOME/.nixpkgs/config.nix.
adding hint telling where to set config for nixos svn path=/nixpkgs/trunk/; revision=17337
2009-09-21 17:55:18 +02:00
# for NIXOS (nixos-rebuild): use nixpkgs.config option
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
config =
* Allow the Nixpkgs config to be passed as a function argument (rather than through ~/.nixpkgs/config.nix or $NIXPKGS_CONFIG). svn path=/nixpkgs/trunk/; revision=16861
2009-08-26 15:51:37 +02:00
let
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
toPath = builtins.toPath;
getEnv = x: if builtins ? getEnv then builtins.getEnv x else "";
pathExists = name:
builtins ? pathExists && builtins.pathExists (toPath name);
configFile = getEnv "NIXPKGS_CONFIG";
homeDir = getEnv "HOME";
configFile2 = homeDir + "/.nixpkgs/config.nix";
allow { pkgs, pkgsOrig, ... } : in config.nix svn path=/nixpkgs/trunk/; revision=14700
2009-03-25 14:29:47 +01:00
configExpr =
* Allow the Nixpkgs config to be passed as a function argument (rather than through ~/.nixpkgs/config.nix or $NIXPKGS_CONFIG). svn path=/nixpkgs/trunk/; revision=16861
2009-08-26 15:51:37 +02:00
if config_ != null then config_
else if configFile != "" && pathExists configFile then import (toPath configFile)
else if homeDir != "" && pathExists configFile2 then import (toPath configFile2)
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
else {};
allow { pkgs, pkgsOrig, ... } : in config.nix svn path=/nixpkgs/trunk/; revision=14700
2009-03-25 14:29:47 +01:00
* Allow the Nixpkgs config to be passed as a function argument (rather than through ~/.nixpkgs/config.nix or $NIXPKGS_CONFIG). svn path=/nixpkgs/trunk/; revision=16861
2009-08-26 15:51:37 +02:00
in
allow { pkgs, pkgsOrig, ... } : in config.nix svn path=/nixpkgs/trunk/; revision=14700
2009-03-25 14:29:47 +01:00
# allow both:
# { /* the config */ } and
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
# { pkgs, ... } : { /* the config */ }
* Allow the Nixpkgs config to be passed as a function argument (rather than through ~/.nixpkgs/config.nix or $NIXPKGS_CONFIG). svn path=/nixpkgs/trunk/; revision=16861
2009-08-26 15:51:37 +02:00
if builtins.isFunction configExpr
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
then configExpr { inherit pkgs; }
allow { pkgs, pkgsOrig, ... } : in config.nix svn path=/nixpkgs/trunk/; revision=14700
2009-03-25 14:29:47 +01:00
else configExpr;
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
Changing the way 'platform' gets into all-packages, allowing setting it in nixpkgs config. svn path=/nixpkgs/branches/stdenv-updates/; revision=23635
2010-09-03 23:34:49 +02:00
# Allow setting the platform in the config file. Otherwise, let's use a reasonable default (pc)
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
Adding an automatic proper platform for some systems we know That eases the burden of having to always set the platform at least in the non-pc pure nixpkgs platforms.
2013-01-29 22:11:37 +01:00
platformAuto = let
platforms = (import ./platforms.nix);
in
if system == "armv6l-linux" then platforms.raspberrypi
else if system == "armv5tel-linux" then platforms.sheevaplug
else if system == "mips64el-linux" then platforms.fuloong2f_n32
platforms.nix: Separate 32-bit and 64-bit PCs With this, stdenv.platform.kernelArch can be used by the kernel builder for PC platforms too. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-01 03:34:44 +01:00
else if system == "x86_64-linux" then platforms.pc64
else if system == "i686-linux" then platforms.pc32
else platforms.pcBase;
Adding an automatic proper platform for some systems we know That eases the burden of having to always set the platform at least in the non-pc pure nixpkgs platforms.
2013-01-29 22:11:37 +01:00
platform = if platform_ != null then platform_
else config.platform or platformAuto;
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
* Move functions like `runCommand' out of all-packages.nix and into build-support/. svn path=/nixpkgs/trunk/; revision=18465
2009-11-19 17:07:47 +01:00
# Helper functions that are exported through `pkgs'.
pkgs/applications/editors/emacs-modes/prolog: initial version of prolog-mode for Emacs svn path=/nixpkgs/trunk/; revision=18675
2009-11-27 18:40:56 +01:00
helperFunctions =
* Export the stdenv adapter functions. * Add a "kernel" attribute containing the default kernel to make it easier to override. svn path=/nixpkgs/trunk/; revision=19189
2010-01-03 18:56:55 +01:00
stdenvAdapters //
* Move functions like `runCommand' out of all-packages.nix and into build-support/. svn path=/nixpkgs/trunk/; revision=18465
2009-11-19 17:07:47 +01:00
(import ../build-support/trivial-builders.nix { inherit (pkgs) stdenv; inherit (pkgs.xorg) lndir; });
* Export the stdenv adapter functions. * Add a "kernel" attribute containing the default kernel to make it easier to override. svn path=/nixpkgs/trunk/; revision=19189
2010-01-03 18:56:55 +01:00
stdenvAdapters =
Add a stdenv adapter ‘useGoldLinker’ to force use of Gold
2014-02-04 16:58:12 +01:00
import ../stdenv/adapters.nix pkgs;
* Export the stdenv adapter functions. * Add a "kernel" attribute containing the default kernel to make it easier to override. svn path=/nixpkgs/trunk/; revision=19189
2010-01-03 18:56:55 +01:00
* Move functions like `runCommand' out of all-packages.nix and into build-support/. svn path=/nixpkgs/trunk/; revision=18465
2009-11-19 17:07:47 +01:00
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
# Allow packages to be overriden globally via the `packageOverrides'
# configuration option, which must be a function that takes `pkgs'
# as an argument and returns a set of new or overriden packages.
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
# The `packageOverrides' function is called with the *original*
* Quick proof-of-concept of making it easy to override package configuration options in ~/.nixpkgs/config.nix. Example: { packageOverrides = pkgs: { subversion = pkgs.subversion.function (origArgs: { bdbSupport = false; pythonBindings = !origArgs.pythonBindings; }); }; } I.e. pkgs.subversion.function is the original function call to the Subversion function in all-packages.nix. This requires the "subversion" attribute to use makeOverridable, which stores the original function and function arguments in the "function" attribute of the result. svn path=/nixpkgs/trunk/; revision=12728
2008-08-26 18:50:33 +02:00
# (un-overriden) set of packages, allowing packageOverrides
# attributes to refer to the original attributes (e.g. "foo =
# ... pkgs.foo ...").
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
pkgs = applyGlobalOverrides (config.packageOverrides or (pkgs: {}));
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
# Return the complete set of packages, after applying the overrides
* ‘applyGlobalOverrides’ considered harmful. Getting rid of it in the calls to KDE 4.5 and 4.6 cuts nix-env evaluation time (for ‘-qa --drv-path *’) from 10.2s to 7.4s. There are two other calls to ‘applyGlobalOverrides’, namely in ‘webkit’ and ‘webkitSVN’ for the libsoup override. We should get rid of those too. svn path=/nixpkgs/trunk/; revision=27611
2011-07-05 16:38:31 +02:00
# returned by the `overrider' function (see above). Warning: this
# function is very expensive!
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
applyGlobalOverrides = overrider:
let
# Call the overrider function. We don't want stdenv overrides
# in the case of cross-building, or otherwise the basic
# overrided packages will not be built with the crossStdenv
# adapter.
overrides = overrider pkgsOrig //
* Streamline the stdenv bootstrap and resulting closure by removing some redundant builds (e.g., GMP was built three times). * Updated GMP to 5.0.2. * Updated PPL to 0.11.2. * Remove ad hoc flags to build GCC's dependencies statically. Instead, use the ‘makeStaticLibraries’ stdenv adapter. * Build GMP with C++ support by default. svn path=/nixpkgs/branches/stdenv-updates/; revision=30891
2011-12-14 15:31:56 +01:00
(lib.optionalAttrs (pkgsOrig.stdenv ? overrides && crossSystem == null) (pkgsOrig.stdenv.overrides pkgsOrig));
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
# The un-overriden packages, passed to `overrider'.
pkgs/top-level/all-packages.nix: strip trailing white space, no functional change svn path=/nixpkgs/trunk/; revision=23830
2010-09-17 16:47:02 +02:00
pkgsOrig = pkgsFun pkgs {};
* Quick proof-of-concept of making it easy to override package configuration options in ~/.nixpkgs/config.nix. Example: { packageOverrides = pkgs: { subversion = pkgs.subversion.function (origArgs: { bdbSupport = false; pythonBindings = !origArgs.pythonBindings; }); }; } I.e. pkgs.subversion.function is the original function call to the Subversion function in all-packages.nix. This requires the "subversion" attribute to use makeOverridable, which stores the original function and function arguments in the "function" attribute of the result. svn path=/nixpkgs/trunk/; revision=12728
2008-08-26 18:50:33 +02:00
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
# The overriden, final packages.
pkgs/top-level/all-packages.nix: strip trailing white space, no functional change svn path=/nixpkgs/trunk/; revision=23830
2010-09-17 16:47:02 +02:00
pkgs = pkgsFun pkgs overrides;
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
in pkgs;
* Quick proof-of-concept of making it easy to override package configuration options in ~/.nixpkgs/config.nix. Example: { packageOverrides = pkgs: { subversion = pkgs.subversion.function (origArgs: { bdbSupport = false; pythonBindings = !origArgs.pythonBindings; }); }; } I.e. pkgs.subversion.function is the original function call to the Subversion function in all-packages.nix. This requires the "subversion" attribute to use makeOverridable, which stores the original function and function arguments in the "function" attribute of the result. svn path=/nixpkgs/trunk/; revision=12728
2008-08-26 18:50:33 +02:00
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
# The package compositions. Yes, this isn't properly indented.
Remove uses of __overrides feature In addition to replacing use of a feature with IMO confusing semantics, this will also let us cleanly separate out all-packages.nix into category-specific files without changing the structure of the pkgs attrset. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-30 17:04:45 +01:00
pkgsFun = pkgs: overrides:
* Added a function `applyGlobalOverrides' to return Nixpkgs with the specified overrides applied. This does the same as the `packageOverrides' attribute in ~/.nixpkgs/config.nix, but can be used within all-packages.nix to do a "deep" override for some specific package. For instance, to build Thunderbird with an older version of Glib, you can say: thunderbird3 = let pkgs = applyGlobalOverrides (pkgsOrig: { gtkLibs220 = pkgsOrig.gtkLibs220 // { glib = pkgsOrig.gtkLibs218.glib; }; }); in pkgs.callPackage .../thunderbird/3.x.nix { inherit (pkgs.gnome) libIDL; }; Note that `pkgsFun' now has an argument `pkgs' to refer to its own result. * Moved callPackage etc. into pkgsFun so that it uses the right overriden packages, if applicable. `defaultScope' isn't in the result set because that causes nix-env to go into an apparently infinite recursion. * Dropped the optional pkgsOrig argument to ~/.nixpkgs/config.nix, because it's probably not useful or used. svn path=/nixpkgs/trunk/; revision=23613
2010-09-03 12:46:18 +02:00
with helperFunctions;
Remove uses of __overrides feature In addition to replacing use of a feature with IMO confusing semantics, this will also let us cleanly separate out all-packages.nix into category-specific files without changing the structure of the pkgs attrset. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-30 17:04:45 +01:00
let defaultScope = pkgs // pkgs.xorg; self = self_ // overrides;
self_ = with self; helperFunctions // {
maudeUnstable: updated full-maude to latest alpha release svn path=/nixpkgs/trunk/; revision=13017
2008-10-09 12:10:49 +02:00
Make some arguments passed to all-packages.nix available in the pkgs set These are needed to re-call <nixpkgs/pkgs/stdenv> to, say, deeply override glibc Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-05 03:21:31 +02:00
# Make some arguments passed to all-packages.nix available
Remove the unmaintained (and AFAIK unused) stdenv for mingw
2014-06-30 13:31:08 +02:00
inherit system platform;
Make some arguments passed to all-packages.nix available in the pkgs set These are needed to re-call <nixpkgs/pkgs/stdenv> to, say, deeply override glibc Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-05 03:21:31 +02:00
Remove uses of __overrides feature In addition to replacing use of a feature with IMO confusing semantics, this will also let us cleanly separate out all-packages.nix into category-specific files without changing the structure of the pkgs attrset. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-30 17:04:45 +01:00
# Allow callPackage to fill in the pkgs argument
inherit pkgs;
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
* Add callPackage etc. svn path=/nixpkgs/trunk/; revision=22876
2010-08-02 15:57:57 +02:00
# We use `callPackage' to be able to omit function arguments that
# can be obtained from `pkgs' or `pkgs.xorg' (i.e. `defaultScope').
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
# Use `newScope' for sets of packages in `pkgs' (see e.g. `gnome'
* Add callPackage etc. svn path=/nixpkgs/trunk/; revision=22876
2010-08-02 15:57:57 +02:00
# below).
callPackage = newScope {};
newScope = extra: lib.callPackageWith (defaultScope // extra);
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=23000
2010-08-06 14:47:20 +02:00
* Added the Dutch Tax Return program for 2009. svn path=/nixpkgs/trunk/; revision=20828
2010-03-25 20:40:19 +01:00
# Override system. This is useful to build i686 packages on x86_64-linux.
pkgsi686Linux: Use 32b kernels (x86_64 kernels can't be built with 32b gcc).
2014-02-22 15:56:59 +01:00
forceSystem = system: kernel: (import ./all-packages.nix) {
provide pkgsi686Linux attr for convinience.. svn path=/nixpkgs/trunk/; revision=19197
2010-01-04 08:44:30 +01:00
inherit system;
pkgsi686Linux: Use 32b kernels (x86_64 kernels can't be built with 32b gcc).
2014-02-22 15:56:59 +01:00
platform = platform // { kernelArch = kernel; };
forceSystem: Inherit `crossSystem' and `platform'. svn path=/nixpkgs/trunk/; revision=33119
2012-03-15 21:27:41 +01:00
inherit bootStdenv noSysDirs gccWithCC gccWithProfiling config
pkgsi686Linux: Use 32b kernels (x86_64 kernels can't be built with 32b gcc).
2014-02-22 15:56:59 +01:00
crossSystem;
provide pkgsi686Linux attr for convinience.. svn path=/nixpkgs/trunk/; revision=19197
2010-01-04 08:44:30 +01:00
};
pkgs/top-level/all-packages.nix: strip trailing white space, no functional change svn path=/nixpkgs/trunk/; revision=23830
2010-09-17 16:47:02 +02:00
* Added the Dutch Tax Return program for 2009. svn path=/nixpkgs/trunk/; revision=20828
2010-03-25 20:40:19 +01:00
# Used by wine, firefox with debugging version of Flash, ...
pkgsi686Linux: Use 32b kernels (x86_64 kernels can't be built with 32b gcc).
2014-02-22 15:56:59 +01:00
pkgsi686Linux = forceSystem "i686-linux" "i386";
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
* Use callPackage_i686 for i686-only packages. svn path=/nixpkgs/trunk/; revision=23113
2010-08-11 15:25:30 +02:00
callPackage_i686 = lib.callPackageWith (pkgsi686Linux // pkgsi686Linux.xorg);
* Allow packages to be overriden globally via the `packageOverrides' configuration option. For instance, to override GCC globally for all of Nixpkgs, you can put the following in ~/.nixpkgs/config.nix: { packageOverrides = pkgs: { gcc = pkgs.gcc41; } } This should make a lot of configuration support in Nixpkgs unnecessary, like selectVersion and many little-used configuration options. It also provides a somewhat convenient place to put custom, private additions to Nixpkgs, e.g. { packageOverrides = pkgs: { myHello = pkgs.stdenv.mkDerivation { name = "my-hello-0.1"; buildCommand = ...; }; }; }; Note that this requires Nix >= 0.12pre12726. * Removed the `myPackages' option `packageOverrides' obsoletes it. svn path=/nixpkgs/trunk/; revision=12727
2008-08-26 17:35:00 +02:00
# For convenience, allow callers to get the path to Nixpkgs.
* It makes more sense for "path" to point at the top of the Nixpkgs tree, rather than the pkgs subdirectory. svn path=/nixpkgs/trunk/; revision=15893
2009-06-09 00:43:27 +02:00
path = ../..;
* Use all those new packages. svn path=/nixpkgs/trunk/; revision=545
2003-11-25 19:02:05 +01:00
maudeUnstable: updated full-maude to latest alpha release svn path=/nixpkgs/trunk/; revision=13017
2008-10-09 12:10:49 +02:00
* Started moving from XFree86 to the freedesktop.org Xlibs libraries. svn path=/nixpkgs/trunk/; revision=860
2004-03-27 22:59:31 +01:00
### Symbolic names.
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
x11 = xlibsWrapper;
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Start the switch to the new X libraries. It's still conditional: set `useOldXLibs' to `false' in all-packages-generic.nix to use them. * Added Xaw3d. * Added Xaw3d support to Emacs. svn path=/nixpkgs/trunk/; revision=4263
2005-11-12 18:05:51 +01:00
# `xlibs' is the set of X library components. This used to be the
Added libdwarf, libevent 1.4, libmcrypt, libmemcached, oniguruma. These are dependencies for HipHop Virtual Machine.
2012-12-01 21:28:32 +01:00
# old modular X llibraries project (called `xlibs') but now it's just
* Start the switch to the new X libraries. It's still conditional: set `useOldXLibs' to `false' in all-packages-generic.nix to use them. * Added Xaw3d. * Added Xaw3d support to Emacs. svn path=/nixpkgs/trunk/; revision=4263
2005-11-12 18:05:51 +01:00
# the set of packages in the modular X.org tree (which also includes
# non-library components like the server, drivers, fonts, etc.).
* Remove the old modular X libraries. svn path=/nixpkgs/trunk/; revision=5729
2006-07-17 14:46:39 +02:00
xlibs = xorg // {xlibs = xlibsWrapper;};
* Start the switch to the new X libraries. It's still conditional: set `useOldXLibs' to `false' in all-packages-generic.nix to use them. * Added Xaw3d. * Added Xaw3d support to Emacs. svn path=/nixpkgs/trunk/; revision=4263
2005-11-12 18:05:51 +01:00
* Merge all-packages.nix into all-packages-generic.nix. svn path=/nixpkgs/branches/usability/; revision=4765
2006-02-08 18:37:45 +01:00
* Push packages from the final stdenv bootstrapping phase to all-packages. That is, an attribute like "bash" in all-packages.nix should evaluate to the "bash" used to build stdenv, it shouldn't build a new one. Hm, this would be a lot cleaner if we had lazy_rec ;-) svn path=/nixpkgs/branches/usability/; revision=4775
2006-02-09 18:04:18 +01:00
### Helper functions.
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
inherit lib config stdenvAdapters;
maudeUnstable: updated full-maude to latest alpha release svn path=/nixpkgs/trunk/; revision=13017
2008-10-09 12:10:49 +02:00
Give Org-Mode a high priority. svn path=/nixpkgs/trunk/; revision=22694
2010-07-22 10:59:46 +02:00
inherit (lib) lowPrio hiPrio appendToName makeOverridable;
add versionedDerivation
2013-05-05 17:05:59 +02:00
inherit (misc) versionedDerivation;
* A function `useDietLibC' that returns a modified stdenv that uses dietlibc to produce small, statically linked binaries. This stdenv also passes `-Os' to GCC automatically to optimise for size. It also tries to prevent builders from linking against dynamic libraries (which dietlibc doesn't support). * A function `addAttrsToDerivation' that returns a modified stdenv that always adds the specified attributes to the derivations that it produces. Example (from curl): curlDiet = import ../tools/networking/curl { inherit fetchurl zlib; stdenv = addAttrsToDerivation { CFLAGS = "-DHAVE_INET_NTOA_R_2_ARGS=1"; } (useDietLibC stdenv); }; (This is needed to get curl to build with dietlibc. Also note the stacking of stdenv-modifying functions.) * curl-diet: no longer necessary. svn path=/nixpkgs/trunk/; revision=6761
2006-10-18 14:50:04 +02:00
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
# Applying this to an attribute set will cause nix-env to look
# inside the set for derivations.
* eval-release.nix: force nix-instantiate to include nested attribute sets. svn path=/nixpkgs/trunk/; revision=31500
2012-01-12 17:59:58 +01:00
recurseIntoAttrs = attrs: attrs // { recurseForDerivations = true; };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* composedArgsAndFun -> makeOverridable for consistency. * Rename a few single-version packages to "default.nix". svn path=/nixpkgs/trunk/; revision=22803
2010-07-29 10:21:21 +02:00
builderDefs = lib.composedArgsAndFun (import ../build-support/builder-defs/builder-defs.nix) {
xlock: fixed build and updated to version 5.24 svn path=/nixpkgs/trunk/; revision=17356
2009-09-22 22:16:38 +02:00
inherit stringsWithDeps lib stdenv writeScript
Adding fetchmtn, including fetchmtn and fetchgit in builder-defs, updating monotone-viz. Adding dadadodo. svn path=/nixpkgs/trunk/; revision=16207
2009-07-07 12:04:32 +02:00
fetchurl fetchmtn fetchgit;
* Clean up indentation (expanded tabs etc.). svn path=/nixpkgs/trunk/; revision=11150
2008-03-17 10:41:28 +01:00
};
Changed builderDefs to use composedArgsAndFun, reduced number of nulls, made overrides in builderDefsPackage to work in an intuitive manner. svn path=/nixpkgs/trunk/; revision=12655
2008-08-19 07:54:09 +02:00
builderDefsPackage = builderDefs.builderDefsPackage builderDefs;
Some refactorings in builderDefs. Psi is a simple showcase. TeXLive now works as far as English is concerned, and it is also updated up to newest builderDefs. svn path=/nixpkgs/trunk/; revision=11235
2008-03-20 16:40:26 +01:00
* Put strings-with-deps in lib. svn path=/nixpkgs/trunk/; revision=15729
2009-05-25 20:22:19 +02:00
stringsWithDeps = lib.stringsWithDeps;
Added a new setup proposal, builder is no more derived from shell script (where edit=glibc rebuild), but is composed from a nix attribute set with strings and dependencies - so if you add a function, old expressions ignore it; collateral damage are packages in this style: Fastest Fourier Transform in the West, Audacity sound editor, Falling Sand game. Also added string equality that ignores dependencies to lib. Note that hasSuffixHack is now the more predictable version, but hasSuffix is left to remind us to fix the bug. svn path=/nixpkgs/trunk/; revision=9549
2007-10-29 11:52:04 +01:00
xlock: fixed build and updated to version 5.24 svn path=/nixpkgs/trunk/; revision=17356
2009-09-22 22:16:38 +02:00
Rewrite the CPAN generator to Perl Also: - It's now installable by doing "nix-env -i nix-generate-from-cpan". - It maps dependencies to the correct attribute (e.g. HTML::HeadParser is mapped to HTMLParser). - It automatically selects buildPerlPackage or buildPerlModule. - It's documented in the manual.
2013-06-13 15:39:08 +02:00
### Nixpkgs maintainer tools
nix-generate-from-cpan = callPackage ../../maintainers/scripts/nix-generate-from-cpan.nix { };
Add nixpkgs-lint This is a simple tool to scan Nixpkgs for violations of the packaging guidelines, such as multiple packages with the same name, packages that lack a description or license, and so on. To use: $ nix-env -i nixpkgs-lint $ cd .../nixpkgs $ nixpkgs-lint Current statistics: Number of packages: 8666 Number of missing maintainers: 3711 Number of missing licenses: 6159 Number of missing descriptions: 1337 Number of bad descriptions: 633 Number of name collisions: 277
2013-07-25 23:50:14 +02:00
nixpkgs-lint = callPackage ../../maintainers/scripts/nixpkgs-lint.nix { };
Rewrite the CPAN generator to Perl Also: - It's now installable by doing "nix-env -i nix-generate-from-cpan". - It maps dependencies to the correct attribute (e.g. HTML::HeadParser is mapped to HTMLParser). - It automatically selects buildPerlPackage or buildPerlModule. - It's documented in the manual.
2013-06-13 15:39:08 +02:00
* Merge all-packages.nix into all-packages-generic.nix. svn path=/nixpkgs/branches/usability/; revision=4765
2006-02-08 18:37:45 +01:00
### STANDARD ENVIRONMENT
* Folded the Cygwin, powerpc-darwin and FreeBSD stdenv into the "native" stdenv. svn path=/nixpkgs/trunk/; revision=12147
2008-06-18 17:09:13 +02:00
allStdenvs = import ../stdenv {
Remove the unmaintained (and AFAIK unused) stdenv for mingw
2014-06-30 13:31:08 +02:00
inherit system platform config;
allStdenvs: Propagate `system'. svn path=/nixpkgs/trunk/; revision=33898
2012-04-24 00:31:39 +02:00
allPackages = args: import ./all-packages.nix ({ inherit config system; } // args);
* Folded the Cygwin, powerpc-darwin and FreeBSD stdenv into the "native" stdenv. svn path=/nixpkgs/trunk/; revision=12147
2008-06-18 17:09:13 +02:00
};
Simplified much more the expressions for cross building and multiplatform. I introduce the new nixpkgs parameter "platform", defaulting to "pc", which was before defined as an attribute of nixpkgs. I made the crossSystem nixpkgs attribute set parameter contain its own 'platform'. This allows cross-building a kernel for a given crossSystem.platform in a non-PC platform. The actual native platform can be taken from stdenv.platform, and this way we also avoid the constant passing of 'platform' to packages for platform-dependant builds (kernel, initrd, ...). I will update nixos accordingly to these changes, for non-PC platforms to work. I think we are gaining on flexibility and clearness. I could cross build succesfully an ultrasparc kernel and a mipsel kernel on PC. But since this change, I should be able to do this also in non-PC. Before this change, there was no possibility of distinguishing the "target platform" or the "native build platform" when cross building, being the single "platform" attribute always interpreted as target platform. The platform is a quite relevant attribute set, as it determines the linuxHeaders used (in the case, by now the only one supported, of linux targets). The platform attributes are quite linux centric still. Let's hope for more generality to come. svn path=/nixpkgs/trunk/; revision=20273
2010-02-27 18:35:47 +01:00
defaultStdenv = allStdenvs.stdenv // { inherit platform; };
* Merge all-packages.nix into all-packages-generic.nix. svn path=/nixpkgs/branches/usability/; revision=4765
2006-02-08 18:37:45 +01:00
Mark alternative stdenvs as lowPrio
2012-09-19 19:13:11 +02:00
stdenvCross = lowPrio (makeStdenvCross defaultStdenv crossSystem binutilsCross gccCrossStageFinal);
- Removed all *NoCross expressions I dupilcated in nixpkgs, while maintaining the cross compilation functionality. - I renamed some expected stdenv.mkDerivation parameter attributes so we can keep this branch properly updated from trunk. We agreed with Nicolas Pierron doing a massive renaming, so all current buildInputs become hostInputs (input as build for the host machine, in autotools terminology) , and then buildInputs would mean "input as for the build machine". By now, the specific "input as for the build machine" is specified through buildNativeInputs. We should fix this in the merge to trunk. - I made the generic stdenv understand the buildNativeInputs, otherwise if we start changing nixpkgs expressions so they distinguish the current buildInputs into buildInputs and buildNativeInputs, we could break even more nixpkgs for other platforms. - I changed the default result of mkDerivation so it becomes the derivation for to be run in the build machine. This allows, without any special rewriting, "fetchurl" derivations to be always results for the build machine to use them. - The change above implies that, for anyone wanting to cross-compile, has to build the hostDrv of the wanted derivation. For example, after this commit, the usual test of "nix-build -A bison.hostDrv arm.nix" works. I described the contents of this arm.nix in r18398. svn path=/nixpkgs/branches/stdenv-updates/; revision=18471
2009-11-19 20:03:34 +01:00
pkgs/top-level/all-packages.nix: switch to Python 2.6 (except on Darwin) MacOS X can build Python 2.6 just fine, but for some reason a lot of modules don't work, so the resulting binary isn't very useful. svn path=/nixpkgs/branches/stdenv-updates/; revision=19598
2010-01-21 16:39:11 +01:00
stdenv =
Trying to make gcc 4.5 cross-buildable svn path=/nixpkgs/branches/stdenv-updates/; revision=22848
2010-08-01 23:21:26 +02:00
if bootStdenv != null then (bootStdenv // {inherit platform;}) else
Fixing a typo. And letting stdenvCross be prioritary to the global override. svn path=/nixpkgs/trunk/; revision=31748
2012-01-21 01:26:50 +01:00
if crossSystem != null then
Making the cross-stdenv not to be used unless cross-compiling. This way, no "hostDrv" or "buildDrv" attributes are added to derivations. svn path=/nixpkgs/trunk/; revision=19866
2010-02-08 16:28:05 +01:00
stdenvCross
Fixing a typo. And letting stdenvCross be prioritary to the global override. svn path=/nixpkgs/trunk/; revision=31748
2012-01-21 01:26:50 +01:00
else
let
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
changer = config.replaceStdenv or null;
Fixing a typo. And letting stdenvCross be prioritary to the global override. svn path=/nixpkgs/trunk/; revision=31748
2012-01-21 01:26:50 +01:00
in if changer != null then
changer {
# We import again all-packages to avoid recursivities.
pkgs = import ./all-packages.nix {
# We remove packageOverrides to avoid recursivities
config = removeAttrs config [ "replaceStdenv" ];
};
}
Making the cross-stdenv not to be used unless cross-compiling. This way, no "hostDrv" or "buildDrv" attributes are added to derivations. svn path=/nixpkgs/trunk/; revision=19866
2010-02-08 16:28:05 +01:00
else
defaultStdenv;
I made the whole nixpkgs dependencies available to the cross compiler, no needing to keep a new tree of expressions apart for the expressions to get cross-compiled. I changed the whole way of using cross compilation with nixpkgs, which before was done through a simple adapter. Now the adapter became complex, and I've tried to avoid the most obvious recursivities. For example, the fetchurl expression should never be cross-compiled, as the gmp, mpfr, and some others, like some ncurses, perl, ... I made overrided copies of those necessary as perlNoCross, ncursesNoCross, as stdenvNoCross, keeping in mind that the stdenv (capable of cross compilation) is built upon stdenvNoCross using an adapter. So, to cross compile, instead of building using "nixpkgs/default.nix", you should build with your own "myarchiteture.nix", which should have contents like these, for example: import /etc/nixos/nixpkgs/default.nix { crossSystem = { config = "armv5tel-unknown-linux-gnueabi"; bigEndian = false; arch = "arm"; float = "soft"; }; } svn path=/nixpkgs/branches/stdenv-updates/; revision=18398
2009-11-17 23:58:48 +01:00
Hack to fix llvm/clang build on Darwin (Or at least restore it to the same level as brokenness as before the staging merge. I.e. it depends on gcc-apple, which doesn't build on standard 10.9 systems.)
2014-08-09 23:31:00 +02:00
stdenvApple = stdenvAdapters.overrideGCC allStdenvs.stdenvNative gccApple;
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
forceNativeDrv = drv : if crossSystem == null then drv else
Rename hostDrv -> crossDrv, buildDrv -> nativeDrv This is for consistency with terminology in stdenv (and the terms "hostDrv" and "buildDrv" are not very intuitive, even if they're consistent with GNU terminology).
2012-12-28 19:08:19 +01:00
(drv // { crossDrv = drv.nativeDrv; });
Big fixes in the cross build: - Before this changes, cflags and ldflags for the native and the cross compiler got mixed. Not all the gcc-wrapper/gcc-cross-wrapper variables are independant now, but enough, I think. - Fixed the generic stdenv expression, which did a big mess on buildInputs and buildNativeInputs. Now it distinguishes when there is a stdenvCross or not. Maybe we should have a single stdenv and forget about the stdenvCross adapter - this could end in a stdenv a bit complex, but simpler than the generic stdenv + adapter. - Added basic support in pkgconfig for cross-builds: a single PKG_CONFIG_PATH now works for both the cross and the native compilers, but I think this should work well for most cases I can think of. - I tried to fix the guile expression to cross-biuld; guile is built, but not its manual, so the derivation still fails. Guile requires patching to cross-build, as far as I understnad. - Made the glibcCross build to be done through the usage of a gcc-cross-wrapper over the gcc-cross-stage-static, instead of using it directly. - Trying to make physfs (a neverball dependency) cross build. - Updated the gcc expression to support building a cross compiler without getting derivation variables mixed with those of the stdenvCross. svn path=/nixpkgs/branches/stdenv-updates/; revision=18534
2009-11-22 20:51:45 +01:00
* gcc-wrapper: use the right dynamic linker when -m32 is used. * An attribute `stdenv_32bit' that returns a stdenv capable of building 32-bit binaries. * grub: build on x86_64-linux. svn path=/nixpkgs/trunk/; revision=12211
2008-06-29 18:13:02 +02:00
# A stdenv capable of building 32-bit binaries. On x86_64-linux,
# it uses GCC compiled with multilib support; on i686-linux, it's
# just the plain stdenv.
Mark alternative stdenvs as lowPrio
2012-09-19 19:13:11 +02:00
stdenv_32bit = lowPrio (
* gcc-wrapper: use the right dynamic linker when -m32 is used. * An attribute `stdenv_32bit' that returns a stdenv capable of building 32-bit binaries. * grub: build on x86_64-linux. svn path=/nixpkgs/trunk/; revision=12211
2008-06-29 18:13:02 +02:00
if system == "x86_64-linux" then
Use gcc48_multi for stdenv_32bit Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 22:12:41 +01:00
overrideGCC stdenv gcc48_multi
* gcc-wrapper: use the right dynamic linker when -m32 is used. * An attribute `stdenv_32bit' that returns a stdenv capable of building 32-bit binaries. * grub: build on x86_64-linux. svn path=/nixpkgs/trunk/; revision=12211
2008-06-29 18:13:02 +02:00
else
Mark alternative stdenvs as lowPrio
2012-09-19 19:13:11 +02:00
stdenv);
* gcc-wrapper: use the right dynamic linker when -m32 is used. * An attribute `stdenv_32bit' that returns a stdenv capable of building 32-bit binaries. * grub: build on x86_64-linux. svn path=/nixpkgs/trunk/; revision=12211
2008-06-29 18:13:02 +02:00
* bclr: shrink fixes.patch from 3.6 MB (!) to 11 KB by not including Autoconf/Automake generated code. svn path=/nixpkgs/trunk/; revision=22815
2010-07-29 21:56:16 +02:00
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
### BUILD SUPPORT
* Converting packages. This is the minimal Nix stdenv for building the ATerm library. svn path=/nixpkgs/trunk/; revision=459
2003-11-02 18:42:19 +01:00
Lots of Perl package updates
2013-01-19 00:02:51 +01:00
attrSetToDir = arg: import ../build-support/upstream-updater/attrset-to-dir.nix {
Add an automated updater script and definitions for its use for WebKit svn path=/nixpkgs/trunk/; revision=16816
2009-08-24 00:10:08 +02:00
inherit writeTextFile stdenv lib;
theAttrSet = arg;
};
* Use all those new packages. svn path=/nixpkgs/trunk/; revision=545
2003-11-25 19:02:05 +01:00
* Add a setup hook ‘autoreconfHook’ to simplify packages that need to run autoreconf: buildInputs = [ autoreconfHook ]; is essentially equivalent to buildInputs = [ autoconf automake libtool ]; preConfigure = "autoreconf -i"; svn path=/nixpkgs/branches/x-updates/; revision=34181
2012-05-19 04:52:36 +02:00
autoreconfHook = makeSetupHook
{ substitutions = { inherit autoconf automake libtool; }; }
../build-support/setup-hooks/autoreconf.sh;
* Fork of build-env in the Nix distribution. This one supports ignoring collisions and selectively including directories. svn path=/nixpkgs/trunk/; revision=7160
2006-11-28 17:46:12 +01:00
buildEnv = import ../build-support/buildenv {
* It's important to inherit packages from "pkgs" rather than the lexical scope for package overrides to work properly. svn path=/nixpkgs/branches/stdenv-updates/; revision=32456
2012-02-21 15:13:16 +01:00
inherit (pkgs) runCommand perl;
* Fork of build-env in the Nix distribution. This one supports ignoring collisions and selectively including directories. svn path=/nixpkgs/trunk/; revision=7160
2006-11-28 17:46:12 +01:00
};
all-packages.nix: string trailing whitespace
2013-09-16 10:59:39 +02:00
My attempt to get Steam working in NixOS. It uses a function called buildFHSChrootEnv {} that composed chroot environments. In such a chroot environment, I could run Steam without much problem
2013-09-13 23:58:59 +02:00
buildFHSChrootEnv = import ../build-support/build-fhs-chrootenv {
inherit stdenv glibc glibcLocales gcc coreutils diffutils findutils;
inherit gnused gnugrep gnutar gzip bzip2 bashInteractive xz shadow gawk;
fhs-chrootenv (steam): support directly using users other than root, fix sound support, fix /run/user
2014-05-22 22:01:00 +02:00
inherit less buildEnv;
My attempt to get Steam working in NixOS. It uses a function called buildFHSChrootEnv {} that composed chroot environments. In such a chroot environment, I could run Steam without much problem
2013-09-13 23:58:59 +02:00
};
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
Commited my experimental Visual C# build function. Currently, it should only be used by brave people svn path=/nixpkgs/trunk/; revision=22272
2010-06-15 13:16:35 +02:00
dotnetenv = import ../build-support/dotnetenv {
inherit stdenv;
dotnetfx 4.0 is now the default svn path=/nixpkgs/trunk/; revision=29628
2011-10-04 15:28:32 +02:00
dotnetfx = dotnetfx40;
Commited my experimental Visual C# build function. Currently, it should only be used by brave people svn path=/nixpkgs/trunk/; revision=22272
2010-06-15 13:16:35 +02:00
};
Scatter output hook This hook allows to scatter files in $out to multiple outputs. For "bin" and "doc" outputs there are prefefined default masks, but they can be overriden by setting files_<outname>, for example: files_bin = [ "/bin/*" "/lib/libexec/" ]; To make an effect hook must be specified in buildInputs.
2014-05-06 23:41:49 +02:00
scatterOutputHook = makeSetupHook {} ../build-support/setup-hooks/scatter_output.sh;
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
vsenv = callPackage ../build-support/vsenv {
Added my very experimental Visual Studio build stuff. You should be even more brave to use this svn path=/nixpkgs/trunk/; revision=22273
2010-06-15 13:32:19 +02:00
vs = vs90wrapper;
Added template to use deb-package wrapper. svn path=/nixpkgs/trunk/; revision=10911
2008-03-02 19:41:32 +01:00
};
Add fetchbower function to go along with bower2nix Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-06 14:20:22 +01:00
fetchbower = import ../build-support/fetchbower {
inherit stdenv git;
inherit (nodePackages) fetch-bower;
};
Add `fetchbzr', to retrieve remote Bazaar repositories. svn path=/nixpkgs/trunk/; revision=12924
2008-09-26 10:57:51 +02:00
fetchbzr = import ../build-support/fetchbzr {
inherit stdenv bazaar;
};
* Remove redundant parentheses. svn path=/nixpkgs/trunk/; revision=6758
2006-10-18 12:32:45 +02:00
fetchcvs = import ../build-support/fetchcvs {
* fetchcvs: cleanup, use nix-store --add-fixed like fetchurl/svn. Argument "url" renamed to "cvsRoot" (it's not a URL). svn path=/nixpkgs/trunk/; revision=10889
2008-02-28 23:36:37 +01:00
inherit stdenv cvs;
Added fetchcvs. svn path=/nixpkgs/trunk/; revision=5295
2006-05-11 14:36:16 +02:00
};
* Remove redundant parentheses. svn path=/nixpkgs/trunk/; revision=6758
2006-10-18 12:32:45 +02:00
fetchdarcs = import ../build-support/fetchdarcs {
* updated darcs to 1.0.5, added curl dependency * added an experimental fetchdarcs function, based on fetchsvn (there are no expressions yet that use this function) svn path=/nixpkgs/trunk/; revision=4615
2006-01-30 12:18:38 +01:00
inherit stdenv darcs nix;
};
* fetchgit and nix-prefetch-git svn path=/nixpkgs/trunk/; revision=16035
2009-06-24 14:48:01 +02:00
fetchgit = import ../build-support/fetchgit {
fetchgit: Handle https. svn path=/nixpkgs/trunk/; revision=28857
2011-08-28 18:03:14 +02:00
inherit stdenv git cacert;
* fetchgit and nix-prefetch-git svn path=/nixpkgs/trunk/; revision=16035
2009-06-24 14:48:01 +02:00
};
Separate fetchgitPrivate into a separate file
2014-07-17 00:05:56 +02:00
fetchgitPrivate = import ../build-support/fetchgit/private.nix {
inherit fetchgit writeScript openssh stdenv;
};
Add function for fetching from a private git repo
2014-05-14 19:35:31 +02:00
Live builds support: initially for git and svn. taglib_live is packaged as an example. svn path=/nixpkgs/trunk/; revision=25351
2011-01-03 00:23:59 +01:00
fetchgitrevision = import ../build-support/fetchgitrevision runCommand git;
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
fetchmtn = callPackage ../build-support/fetchmtn (config.fetchmtn or {});
Adding fetchmtn, including fetchmtn and fetchgit in builder-defs, updating monotone-viz. Adding dadadodo. svn path=/nixpkgs/trunk/; revision=16207
2009-07-07 12:04:32 +02:00
Add gox and packer packages
2014-05-14 01:19:41 +02:00
packer = callPackage ../development/tools/packer { };
Merge #2630: add and use fetchpatch fetchpatch is fetchurl that determinizes the patch. Some parts of generated patches change from time to time, e.g. see #1983 and http://comments.gmane.org/gmane.linux.distributions.nixos/12815 Using fetchpatch should prevent the hash from changing. Conflicts (auto-solved): pkgs/development/libraries/haskell/gitit/default.nix
2014-05-17 07:27:29 +02:00
fetchpatch = callPackage ../build-support/fetchpatch { };
* Remove redundant parentheses. svn path=/nixpkgs/trunk/; revision=6758
2006-10-18 12:32:45 +02:00
fetchsvn = import ../build-support/fetchsvn {
* fetchsvn: Nix already checks the hash, no need for the builder to do it. svn path=/nixpkgs/trunk/; revision=10896
2008-02-29 11:30:29 +01:00
inherit stdenv subversion openssh;
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
sshSupport = true;
};
Live builds support: initially for git and svn. taglib_live is packaged as an example. svn path=/nixpkgs/trunk/; revision=25351
2011-01-03 00:23:59 +01:00
fetchsvnrevision = import ../build-support/fetchsvnrevision runCommand subversion;
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Added hacky fetchsvn component which allows users to fetch code over svn+ssh svn path=/nixpkgs/trunk/; revision=11455
2008-04-02 15:28:55 +02:00
fetchsvnssh = import ../build-support/fetchsvnssh {
inherit stdenv subversion openssh expect;
sshSupport = true;
};
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
fetchhg = import ../build-support/fetchhg {
inherit stdenv mercurial nix;
};
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
# `fetchurl' downloads a file from the network.
fetchurl = import ../build-support/fetchurl {
inherit curl stdenv;
};
* GCC 4.0.0 added (though it's not used for anything yet). svn path=/nixpkgs/trunk/; revision=2878
2005-04-22 14:14:55 +02:00
Add fetchurl_gnome wrapper It just creates correct mirror://gnome/sources/... URL. svn path=/nixpkgs/trunk/; revision=29377
2011-09-20 08:21:46 +02:00
# A wrapper around fetchurl that generates miror://gnome URLs automatically
fetchurl_gnome -> fetchurlGnome
2014-05-08 13:34:51 +02:00
fetchurlGnome = callPackage ../build-support/fetchurl/gnome.nix { };
Add fetchurl_gnome wrapper It just creates correct mirror://gnome/sources/... URL. svn path=/nixpkgs/trunk/; revision=29377
2011-09-20 08:21:46 +02:00
* curl: build with OpenSSL (https) support by default. * Some fetchurl-related refactoring. The `realCurl' attribute is gone, `curl' is the real thing. To prevent an infinite recursion in `fetchurl' (because it depends on curl and building curl needs fetchurl), curl and its dependencies (openssl, zlib, perl) use `fetchurlBoot', which is the fetchurl used by the previous bootstrap phase (e.g. the statically linked version of curl for stdenv-linux). So as a result you can use https:// urls almost everywhere. There's also some hackery to prevent a different curl from being built in every stdenv-linux bootstrap phase (namely the stdenv.fetchurl attribute which allows fetchurl to be overriden everywhere). svn path=/nixpkgs/trunk/; revision=11905
2008-05-27 09:49:55 +02:00
# fetchurlBoot is used for curl and its dependencies in order to
# prevent a cyclic dependency (curl depends on curl.tar.bz2,
# curl.tar.bz2 depends on fetchurl, fetchurl depends on curl). It
# uses the curl from the previous bootstrap phase (e.g. a statically
# linked curl in the case of stdenv-linux).
fetchurlBoot = stdenv.fetchurlBoot;
Add a function "fetchzip" This function downloads and unpacks a file in one fixed-output derivation. This is primarily useful for dynamically generated zip files, such as GitHub's /archive URLs, where the unpacked content of the zip file doesn't change, but the zip file itself may (e.g. due to minor changes in the compression algorithm, or changes in timestamps). Fetchzip is implemented by extending fetchurl with a "postFetch" hook that is executed after the file has been downloaded. This hook can thus perform arbitrary checks or transformations on the downloaded file.
2014-05-08 14:57:20 +02:00
fetchzip = import ../build-support/fetchzip { inherit lib fetchurl unzip; };
Rename fetchGitHub -> fetchFromGitHub We're not fetching all of GitHub, after all.
2014-05-08 15:49:39 +02:00
fetchFromGitHub = { owner, repo, rev, sha256 }: fetchzip {
fetchFromGitHub: Use .tar.gz instead of .zip Also clean up the name attribute of fetchzip derivations a bit.
2014-05-09 15:50:40 +02:00
name = "${repo}-${rev}-src";
url = "https://github.com/${owner}/${repo}/archive/${rev}.tar.gz";
Add a utility function "fetchGitHub" This is a small wrapper around fetchzip. It allows you to say: src = fetchGitHub { owner = "NixOS"; repo = "nix"; rev = "924e19341a5ee488634bc9ce1ea9758ac496afc3"; # or a tag sha256 = "1ld1jc26wy0smkg63chvdzsppfw6zy1ykf3mmc50hkx397wcbl09"; };
2014-05-08 15:26:42 +02:00
inherit sha256;
};
* Interface to support mirror:// in nix-prefetch-url. The function resolveMirrorURLs produces a file containing the URLs to which a mirror:// URL resolves. svn path=/nixpkgs/trunk/; revision=12410
2008-07-23 18:04:10 +02:00
resolveMirrorURLs = {url}: fetchurl {
showURLs = true;
inherit url;
};
hipchat: Fix access to /usr/share/X11/xkb HipChat (or rather its copy of Qt) expects to find keyboard data in /usr/share/X11/xkb. So use a LD_PRELOAD library to intercept and rewrite the Glibc calls that access those paths. We've been doing the same thing with packages like Spotify, but now this functionality has been abstracted into a reusable library, libredirect.so. It uses an environment variable $NIX_REDIRECTS containing a colon-separated list of path prefixes to be rewritten, e.g. "/foo=bar:/xyzzy=/fnord".
2014-05-27 01:00:04 +02:00
libredirect = callPackage ../build-support/libredirect { };
Added desktop file generation function and desktop item for firefox svn path=/nixpkgs/trunk/; revision=15529
2009-05-10 14:03:53 +02:00
makeDesktopItem = import ../build-support/make-desktopitem {
inherit stdenv;
};
all-packages.nix: commented out package 'vice' error: getting status of `/usr/local/src/nix-pkgs-current/pkgs/misc/emulators/vice': No such file or directory svn path=/nixpkgs/trunk/; revision=15646
2009-05-18 15:53:01 +02:00
Update of skype expression: make the use of pulse audio optional based on the configuration setting for pulse audio (off by default). Removing pulse audio from the build inputs when it is not used prevents the bug of Skype taking 100% cpu from showing up. This demonstrates nicely nix' features: in other distributions the recomended solution was to remove read permission from the pulse audio libs. svn path=/nixpkgs/trunk/; revision=31959
2012-02-01 23:09:35 +01:00
makeAutostartItem = import ../build-support/make-startupitem {
inherit stdenv;
inherit lib;
};
makeInitrd: Make the compressor configurable
2013-02-19 17:49:31 +01:00
makeInitrd = {contents, compressor ? "gzip -9"}:
import ../build-support/kernel/make-initrd.nix {
Make initrd and the kernel builds repeatable.
2013-08-16 02:42:11 +02:00
inherit stdenv perl perlArchiveCpio cpio contents ubootChooser compressor;
makeInitrd: Make the compressor configurable
2013-02-19 17:49:31 +01:00
};
* makeInitrd, makeModulesClosure: moved from NixOS. * Use sh from klibc in the initrd. svn path=/nixpkgs/trunk/; revision=11154
2008-03-17 11:40:47 +01:00
* Add a setup hook ‘autoreconfHook’ to simplify packages that need to run autoreconf: buildInputs = [ autoreconfHook ]; is essentially equivalent to buildInputs = [ autoconf automake libtool ]; preConfigure = "autoreconf -i"; svn path=/nixpkgs/branches/x-updates/; revision=34181
2012-05-19 04:52:36 +02:00
makeWrapper = makeSetupHook { } ../build-support/setup-hooks/make-wrapper.sh;
* makeWrapper: new function that transparently takes care of creating a wrapper script. E.g. wrapProgram $out/bin/prog --set FOO bar will create a wrapper around "prog" so that the environment variable FOO is set to bar. The original program is renamed to $out/bin/.wrapped-prog. * Function makeSetupHook to convert a script into a setup hook which can be included in buildInputs. This makes it easier to use scripts like makeWrapper. * Added Bazaar, yet another distributed version management system. svn path=/nixpkgs/trunk/; revision=10211
2008-01-18 11:29:58 +01:00
makeModulesClosure: Use kmod instead of module-init-tools
2013-08-07 22:41:51 +02:00
makeModulesClosure = { kernel, rootModules, allowMissing ? false }:
all-packages.nix changes for all previous commits.. svn path=/nixpkgs/trunk/; revision=11276
2008-03-24 20:40:15 +01:00
import ../build-support/kernel/modules-closure.nix {
makeModulesClosure: Use kmod instead of module-init-tools
2013-08-07 22:41:51 +02:00
inherit stdenv kmod kernel nukeReferences rootModules allowMissing;
all-packages.nix changes for all previous commits.. svn path=/nixpkgs/trunk/; revision=11276
2008-03-24 20:40:15 +01:00
};
* makeInitrd, makeModulesClosure: moved from NixOS. * Use sh from klibc in the initrd. svn path=/nixpkgs/trunk/; revision=11154
2008-03-17 11:40:47 +01:00
* Export the paths-from-graph.pl script. svn path=/nixpkgs/trunk/; revision=15865
2009-06-05 15:20:14 +02:00
pathsFromGraph = ../build-support/kernel/paths-from-graph.pl;
A helper to get the source some package is built from. svn path=/nixpkgs/trunk/; revision=12933
2008-10-01 17:57:22 +02:00
srcOnly = args: (import ../build-support/src-only) ({inherit stdenv; } // args);
* Move the substitution functions into stdenv (not merged yet). * If the environment variable buildCommand is set, then eval that instead of doing the build phases. This is used by the runCommand function in all-packages.nix to allow one-lines like foo = runCommand "foo" {} "mkdir $out; echo foo > $out/foo"; svn path=/nixpkgs/trunk/; revision=7298
2006-12-10 23:24:42 +01:00
substituteAll = import ../build-support/substitute/substitute-all.nix {
Removed references to setup-new-2.sh and setup-new.sh from all-packages.nix svn path=/nixpkgs/branches/stdenv-updates/; revision=9737
2007-11-17 15:34:34 +01:00
inherit stdenv;
* Utility: the generic substituter. It substitutes all occurences of `@var@' in the file `src', writing the result to $out, where `var' is any environment variable starting with a lowercase character. Example: genericSubstituter { src = ./file; foo = "bla"; shell = bash + "/bin/sh"; }; will replace `@foo@' with `bla' and `@shell@' with `/nix/store/...-bash-.../bin/sh'. svn path=/nixpkgs/trunk/; revision=6928
2006-11-02 23:44:32 +01:00
};
replace-dependency: Eelco has ruled, lowerCamelCase > dash-case :(
2013-01-13 17:15:01 +01:00
replaceDependency = import ../build-support/replace-dependency.nix {
Add the replace-dependency build support function. The use case is to do a deep replacement of a dependency without rebuilding the entire tree. For example, suppose a security hole is found in glibc and a patch released. Ideally, you'd just rebuild everything, but that takes time, space, and CPU that you might not have, so in the mean time you could build a safe version of, say, firefox with: firefox-safe = replace-dependency { drv = firefox; old-dependency = glibc; new-dependency = patched-glibc; }; Building firefox-safe will rebuild glibc, but only do a simple copy/string replacement on all other dependencies of firefox. On my system (MBP 13" mid-2012), after a new glibc had been build building firefox took around 11 seconds. See the comments in the file for more details.
2013-01-11 20:42:09 +01:00
inherit runCommand nix lib;
replace-dependency: Eelco has ruled, lowerCamelCase > dash-case :(
2013-01-13 17:15:01 +01:00
};
Add the replace-dependency build support function. The use case is to do a deep replacement of a dependency without rebuilding the entire tree. For example, suppose a security hole is found in glibc and a patch released. Ideally, you'd just rebuild everything, but that takes time, space, and CPU that you might not have, so in the mean time you could build a safe version of, say, firefox with: firefox-safe = replace-dependency { drv = firefox; old-dependency = glibc; new-dependency = patched-glibc; }; Building firefox-safe will rebuild glibc, but only do a simple copy/string replacement on all other dependencies of firefox. On my system (MBP 13" mid-2012), after a new glibc had been build building firefox took around 11 seconds. See the comments in the file for more details.
2013-01-11 20:42:09 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nukeReferences = callPackage ../build-support/nuke-references/default.nix { };
* buildRPM: print out the RPMs in the image. svn path=/nixpkgs/trunk/; revision=11168
2008-03-17 18:29:07 +01:00
vmTools = import ../build-support/vm/default.nix {
inherit pkgs;
};
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
* Start moving the Nix expressions that support the build farm (e.g. making source tarballs, doing coverage analysis) to the Nixpkgs tree. This makes it easier to run build farm jobs locally since you don't need to check out the "release" tree separately. Also it means one less input to declare for build farm jobs. * Removed succeedOnFailure and separate logging of phases. Hydra doesn't need that. svn path=/nixpkgs/trunk/; revision=13388
2008-11-24 16:10:06 +01:00
releaseTools = import ../build-support/release/default.nix {
inherit pkgs;
};
Fix references to pkgs/lib
2013-09-30 22:43:34 +02:00
composableDerivation = (import ../../lib/composable-derivation.nix) {
removed mkDerivationByConfiguration, using composableDerivation instead qgis, vim_configurable both work now svn path=/nixpkgs/trunk/; revision=13661
2008-12-20 02:20:35 +01:00
inherit pkgs lib;
};
* Turn the nukeRefs() function into a separate program. svn path=/nixpkgs/trunk/; revision=6941
2006-11-03 14:33:24 +01:00
Simplified much more the expressions for cross building and multiplatform. I introduce the new nixpkgs parameter "platform", defaulting to "pc", which was before defined as an attribute of nixpkgs. I made the crossSystem nixpkgs attribute set parameter contain its own 'platform'. This allows cross-building a kernel for a given crossSystem.platform in a non-PC platform. The actual native platform can be taken from stdenv.platform, and this way we also avoid the constant passing of 'platform' to packages for platform-dependant builds (kernel, initrd, ...). I will update nixos accordingly to these changes, for non-PC platforms to work. I think we are gaining on flexibility and clearness. I could cross build succesfully an ultrasparc kernel and a mipsel kernel on PC. But since this change, I should be able to do this also in non-PC. Before this change, there was no possibility of distinguishing the "target platform" or the "native build platform" when cross building, being the single "platform" attribute always interpreted as target platform. The platform is a quite relevant attribute set, as it determines the linuxHeaders used (in the case, by now the only one supported, of linux targets). The platform attributes are quite linux centric still. Let's hope for more generality to come. svn path=/nixpkgs/trunk/; revision=20273
2010-02-27 18:35:47 +01:00
platforms = import ./platforms.nix;
Porting changes from stdenv-updates into this branch. This comes from: svn diff ^/nixpkgs/trunk/@18255 ^/nixpkgs/branches/stdenv-updates/ > diff patch -p0 < diff and then adding into svn all files new from the patch. trunk@18255 comes from the last time I updated stdenv-updates from trunk. svn path=/nixpkgs/stdenv-updates2/; revision=18272
2009-11-08 01:32:12 +01:00
Add a setup hook that automatically sets up $CLASSPATH All JARs in $pkg/share/java (for each $pkg in the build inputs) are added to $CLASSPATH. Thus, you can say buildInputs = [ setJavaClassPath someJavaDependency ]; and the JARs in someJavaDependency will be found automatically by tools like javac or ant. Note that the manual used to say that JARs should be installed in lib/java; this is now share/java, following the Debian policy: http://www.debian.org/doc/packaging-manuals/java-policy/x110.html The directory share/java makes more sense because JARs are architecture-independent. (Also, a quick grep shows that we were not exactly consistent about this in Nixpkgs.)
2014-01-06 13:42:37 +01:00
setJavaClassPath = makeSetupHook { } ../build-support/setup-hooks/set-java-classpath.sh;
Add a setup hook for fixing dylib install names on Darwin Install names need to be absolute paths, otherwise programs that link against the dylib won't work without setting $DYLD_LIBRARY_PATH. Most packages do this correctly, but some (like Boost and ICU) do not. This setup hook absolutizes all install names.
2014-01-15 13:39:52 +01:00
fixDarwinDylibNames = makeSetupHook { } ../build-support/setup-hooks/fix-darwin-dylib-names.sh;
Move generation of coverage reports from nixos/lib/testing to releaseTools Also, turn some stdenv adapters into setup hooks.
2014-03-03 13:39:30 +01:00
keepBuildTree = makeSetupHook { } ../build-support/setup-hooks/keep-build-tree.sh;
Turn the coverage analysis stdenv adapters into setup hooks Stdenv adapters are kinda weird and un-idiomatic (especially when they don't actually change stdenv). It's more idiomatic to say buildInputs = [ makeCoverageAnalysisReport ];
2014-02-05 14:11:21 +01:00
Move generation of coverage reports from nixos/lib/testing to releaseTools Also, turn some stdenv adapters into setup hooks.
2014-03-03 13:39:30 +01:00
enableGCOVInstrumentation = makeSetupHook { } ../build-support/setup-hooks/enable-coverage-instrumentation.sh;
makeGCOVReport = makeSetupHook
{ deps = [ pkgs.lcov pkgs.enableGCOVInstrumentation ]; }
Turn the coverage analysis stdenv adapters into setup hooks Stdenv adapters are kinda weird and un-idiomatic (especially when they don't actually change stdenv). It's more idiomatic to say buildInputs = [ makeCoverageAnalysisReport ];
2014-02-05 14:11:21 +01:00
../build-support/setup-hooks/make-coverage-analysis-report.sh;
Porting changes from stdenv-updates into this branch. This comes from: svn diff ^/nixpkgs/trunk/@18255 ^/nixpkgs/branches/stdenv-updates/ > diff patch -p0 < diff and then adding into svn all files new from the patch. trunk@18255 comes from the last time I updated stdenv-updates from trunk. svn path=/nixpkgs/stdenv-updates2/; revision=18272
2009-11-08 01:32:12 +01:00
* Updates paths in all-packages-generic.fix. svn path=/nixpkgs/trunk/; revision=472
2003-11-03 19:21:30 +01:00
### TOOLS
Added abduco
2014-07-23 14:49:43 +02:00
abduco = callPackage ../tools/misc/abduco { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
acct = callPackage ../tools/system/acct { };
Add GNU Accounting Utilities. svn path=/nixpkgs/trunk/; revision=16981
2009-09-08 10:29:40 +02:00
acoustid_fingerprinter: pin to ffmpeg_1
2013-12-16 14:33:31 +01:00
acoustidFingerprinter = callPackage ../tools/audio/acoustid-fingerprinter {
ffmpeg = ffmpeg_1;
};
acoustid-fingerprinter: Add new package, v0.6. This is the commandline tool for interacting with the chromaprint library and it's needed for Picard version 1.2 (as it no longer has support for AmpliFIND/PUIDs). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-08-14 18:36:23 +02:00
actdiag: new package Actdiag generates activity-diagram image from spec-text file (similar to Graphviz).
2013-09-21 19:31:40 +02:00
actdiag = pythonPackages.actdiag;
adom: add famous rogue-like game
2014-07-15 17:21:18 +02:00
adom = callPackage ../games/adom { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
aefs = callPackage ../tools/filesystems/aefs { };
* Added AEFS. svn path=/nixpkgs/trunk/; revision=8549
2007-04-08 01:38:01 +02:00
Aegisub: New Package Adding Aegisub: an advanced movie subtitle editor
2013-12-22 18:37:41 +01:00
aegisub = callPackage ../applications/video/aegisub {
Aegisub: update to 3.1.3 (close #2550) New dependencies: icu, intltool, boost (default = 1.55), wxGTK 3.0 Fixes a bug on Boost detection @vcunat: minor refactoring.
2014-05-06 03:56:41 +02:00
wxGTK = wxGTK30;
icedtea: Remove It has apparently never worked. Also drop xerces and xalan, which were only used by icedtea.
2014-01-03 15:55:27 +01:00
lua = lua5_1;
Aegisub: New Package Adding Aegisub: an advanced movie subtitle editor
2013-12-22 18:37:41 +01:00
};
Add aespipe, an AES encrypting or decrypting pipe
2013-02-18 22:47:41 +01:00
aespipe = callPackage ../tools/security/aespipe { };
added AES crypt
2013-06-27 13:43:50 +02:00
aescrypt = callPackage ../tools/misc/aescrypt { };
Adding ahcpd.
2013-05-29 19:12:06 +02:00
ahcpd = callPackage ../tools/networking/ahcpd { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
aircrackng = callPackage ../tools/networking/aircrack-ng { };
Adding aircrack-ng. svn path=/nixpkgs/trunk/; revision=13936
2009-02-01 22:21:12 +01:00
analog: added version 6.0 svn path=/nixpkgs/trunk/; revision=32029
2012-02-04 11:32:07 +01:00
analog = callPackage ../tools/admin/analog {};
Add apktool, tool for reverse engineering Android apk files
2014-05-22 15:29:36 +02:00
apktool = callPackage ../development/tools/apktool {
buildTools = androidenv.buildTools;
};
apt-offline: offline APT package manager
2014-02-26 06:33:51 +01:00
apt-offline = callPackage ../tools/misc/apt-offline { };
Added archivemount-0.6.1, a FUSE-based file system for mounting tar archives. svn path=/nixpkgs/trunk/; revision=27758
2011-07-13 14:33:54 +02:00
archivemount = callPackage ../tools/filesystems/archivemount { };
add arandr: simple visual front end for xrandr
2013-09-23 22:33:51 +02:00
arandr = callPackage ../tools/X11/arandr { };
arcanist: version 20140521 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-21 22:17:52 +02:00
arcanist = callPackage ../development/tools/misc/arcanist {};
arduino-core libraries +inotool
2012-11-28 02:55:24 +01:00
arduino_core = callPackage ../development/arduino/arduino-core {
jdk = jdk;
jre = jdk;
};
argyllcms: New package, version 1.4.0 ArgyllCMS is an ICC compatible color management system.
2012-12-13 15:58:57 +01:00
argyllcms = callPackage ../tools/graphics/argyllcms {};
arp-scan: new package Arp-scan is a command-line tool that uses the ARP protocol to discover and fingerprint IP hosts on the local network. http://www.nta-monitor.com/tools-resources/security-tools/arp-scan
2014-02-03 12:34:50 +01:00
arp-scan = callPackage ../tools/misc/arp-scan { };
ascii: New package, version 3.12. Quite a useful tool, especially for non English native speakers to find out what people mean with things like "hiccup", "boink", "blugle" and whatnot. And of course it's quite useful to convert between hex/oct/dec/bin. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-12 08:00:19 +01:00
ascii = callPackage ../tools/text/ascii { };
Adding asymptote graphic generation tool svn path=/nixpkgs/trunk/; revision=20158
2010-02-21 18:36:41 +01:00
asymptote = builderDefsPackage ../tools/graphics/asymptote {
inherit freeglut ghostscriptX imagemagick fftw boehmgc
mesa ncurses readline gsl libsigsegv python zlib perl
asympote: fix build
2014-01-05 09:43:12 +01:00
texinfo xz;
Adding asymptote graphic generation tool svn path=/nixpkgs/trunk/; revision=20158
2010-02-21 18:36:41 +01:00
texLive = texLiveAggregationFun {
asympote: fix build
2014-01-05 09:43:12 +01:00
paths = [ texLive texLiveExtra texLiveCMSuper ];
Adding asymptote graphic generation tool svn path=/nixpkgs/trunk/; revision=20158
2010-02-21 18:36:41 +01:00
};
};
Move namePrefix="" python packages out of python-packges.nix It doesn't make sense to build tools/applications with three different python interpreter versions, so move them out of python modules list. Also reverts 53ffc6e0ef395a2bd7651423d9783ad8184be1d0.
2013-07-31 13:32:25 +02:00
awscli = callPackage ../tools/admin/awscli { };
ec2-ami-tools: Update to 1.6.0.0
2012-07-25 21:35:51 +02:00
ec2_api_tools = callPackage ../tools/virtualization/ec2-api-tools { };
amazon ec2 api tools svn path=/nixpkgs/trunk/; revision=17975
2009-10-27 13:51:09 +01:00
ec2-ami-tools: Update to 1.6.0.0
2012-07-25 21:35:51 +02:00
ec2_ami_tools = callPackage ../tools/virtualization/ec2-ami-tools { };
amazon ec2 api tools svn path=/nixpkgs/trunk/; revision=17975
2009-10-27 13:51:09 +01:00
Adding Linux 2.6.36 svn path=/nixpkgs/trunk/; revision=24403
2010-10-21 14:28:14 +02:00
altermime = callPackage ../tools/networking/altermime {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
amule = callPackage ../tools/networking/p2p/amule { };
Added aMule svn path=/nixpkgs/trunk/; revision=9413
2007-10-06 17:59:35 +02:00
Amule, Quassel: use appendToName to provide different names for common/named overrides. svn path=/nixpkgs/trunk/; revision=24622
2010-11-09 00:45:58 +01:00
amuleDaemon = appendToName "daemon" (amule.override {
AMule: Convenience packages for daemon and clent svn path=/nixpkgs/trunk/; revision=23846
2010-09-18 13:26:30 +02:00
monolithic = false;
daemon = true;
Amule, Quassel: use appendToName to provide different names for common/named overrides. svn path=/nixpkgs/trunk/; revision=24622
2010-11-09 00:45:58 +01:00
});
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=24045
2010-10-04 11:49:25 +02:00
Amule, Quassel: use appendToName to provide different names for common/named overrides. svn path=/nixpkgs/trunk/; revision=24622
2010-11-09 00:45:58 +01:00
amuleGui = appendToName "gui" (amule.override {
AMule: Convenience packages for daemon and clent svn path=/nixpkgs/trunk/; revision=23846
2010-09-18 13:26:30 +02:00
monolithic = false;
client = true;
Amule, Quassel: use appendToName to provide different names for common/named overrides. svn path=/nixpkgs/trunk/; revision=24622
2010-11-09 00:45:58 +01:00
});
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=24045
2010-10-04 11:49:25 +02:00
- Added xcodeenv: experimental support to build iOS apps through Nix - Moved mobile development tools into a separate folder
2013-01-07 16:52:42 +01:00
androidenv = import ../development/mobile/androidenv {
Added androidenv - the Android SDK, their additions and two functions that build and emulate Android Apps
2012-11-07 21:10:39 +01:00
inherit pkgs;
pkgs_i686 = pkgsi686Linux;
};
all-packages.nix: strip trailing whitespace
2013-01-16 12:22:46 +01:00
tools/security/apg: New nixpkg.
2013-02-17 14:44:54 +01:00
apg = callPackage ../tools/security/apg { };
grc: add expression
2013-07-31 06:11:31 +02:00
grc = callPackage ../tools/misc/grc { };
otool and setfile: cleanup
2013-07-07 10:54:33 +02:00
otool = callPackage ../os-specific/darwin/otool { };
gobject-introspection: fix build on darwin * add otool expression (add otool to build inputs) * add libintlOrEmpty to build inputs
2013-07-03 14:02:40 +02:00
Bump pass(word-store) to 1.6.1. ...and also simplify the expression massively.
2014-04-30 23:36:05 +02:00
pass = callPackage ../tools/security/pass {
gnupg = gnupg1compat;
};
password-store: add expression
2013-08-03 11:25:13 +02:00
otool and setfile: cleanup
2013-07-07 10:54:33 +02:00
setfile = callPackage ../os-specific/darwin/setfile { };
setFile: add expression
2013-07-04 00:50:37 +02:00
install_name_tool: add expression
2013-07-04 11:13:36 +02:00
install_name_tool = callPackage ../os-specific/darwin/install_name_tool { };
- Added xcodeenv: experimental support to build iOS apps through Nix - Moved mobile development tools into a separate folder
2013-01-07 16:52:42 +01:00
xcodeenv = callPackage ../development/mobile/xcodeenv { };
all-packages.nix: strip trailing whitespace
2013-04-21 20:10:40 +02:00
Make xcode version configurable + fix android emulator tests
2014-01-13 14:34:46 +01:00
titaniumenv = callPackage ../development/mobile/titaniumenv {
Added androidenv - the Android SDK, their additions and two functions that build and emulate Android Apps
2012-11-07 21:10:39 +01:00
inherit pkgs;
pkgs_i686 = pkgsi686Linux;
};
all-packages.nix: strip trailing whitespace
2013-04-21 20:10:40 +02:00
Expose Android NDK in the top level expression
2014-09-02 14:11:09 +02:00
inherit (androidenv) androidsdk_4_4 androidndk;
Make "nix-env -i android-sdk" DTRT
2012-11-08 16:38:38 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
aria2 = callPackage ../tools/networking/aria2 { };
Apparently nobody ever noticed that aria was already packaged when packaging it once more; merging expressions
2014-07-04 19:42:14 +02:00
aria = aria2;
* Added aria2, a download utility. svn path=/nixpkgs/trunk/; revision=21912
2010-05-20 13:11:24 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
at = callPackage ../tools/system/at { };
Add At, the classical Unix command scheduler. svn path=/nixpkgs/trunk/; revision=11434
2008-04-01 11:08:17 +02:00
Adding atftp svn path=/nixpkgs/trunk/; revision=28874
2011-08-29 14:47:39 +02:00
atftp = callPackage ../tools/networking/atftp {};
autogen: minor update and fix by disabling tests /dev/tty is missing
2013-02-23 14:44:38 +01:00
autogen = callPackage ../development/tools/misc/autogen { };
Add GNU AutoGen. svn path=/nixpkgs/trunk/; revision=17491
2009-09-29 11:01:40 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
autojump = callPackage ../tools/misc/autojump { };
Add Autojump, a smart replacement for `cd'. svn path=/nixpkgs/trunk/; revision=15738
2009-05-27 00:05:05 +02:00
autorandr: add autorandr an automatic display configuration selector
2013-09-25 00:10:59 +02:00
autorandr = callPackage ../tools/misc/autorandr {
inherit (xorg) xrandr xdpyinfo;
};
* Simplify the avahi call. svn path=/nixpkgs/branches/x-updates/; revision=26158
2011-03-04 14:04:08 +01:00
avahi = callPackage ../development/libraries/avahi {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
qt4Support = config.avahi.qt4Support or false;
* Simplify the avahi call. svn path=/nixpkgs/branches/x-updates/; revision=26158
2011-03-04 14:04:08 +01:00
};
Add `avahi' package. svn path=/nixpkgs/trunk/; revision=10527
2008-02-06 20:36:12 +01:00
Add aws, a utility for working with various AWS services
2012-07-09 19:47:16 +02:00
aws = callPackage ../tools/virtualization/aws { };
all-packages.nix: strip trailing whitespace
2012-07-10 15:57:56 +02:00
* Added aws-mturk-clt, the Amazon Mechanical Turk command-line tools. svn path=/nixpkgs/trunk/; revision=28150
2011-08-04 14:13:53 +02:00
aws_mturk_clt = callPackage ../tools/misc/aws-mturk-clt { };
Add `avahi' package. svn path=/nixpkgs/trunk/; revision=10527
2008-02-06 20:36:12 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
axel = callPackage ../tools/networking/axel { };
add axel, a downloader with support for multiple connection for faster downloading svn path=/nixpkgs/trunk/; revision=9139
2007-08-16 21:50:59 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
azureus = callPackage ../tools/networking/p2p/azureus { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
basex: new package BaseX is a very fast and light-weight, yet powerful XML database and XPath/XQuery processor, including support for the latest W3C Full Text and Update Recommendations. It supports large XML instances and offers a highly interactive front-end (basexgui). Apart from two local standalone modes, BaseX offers a client/server architecture. Homepage: http://basex.org/ Implementation notes: - I'm using the pre-built java package (because it's simple) - I copied the basex.svg icon file from the Ubuntu package because I couldn't find it anywhere else. It's 9.3 KiB.
2013-08-31 14:27:40 +02:00
basex = callPackage ../tools/text/xml/basex { };
Adding babeld.
2013-05-29 19:15:49 +02:00
babeld = callPackage ../tools/networking/babeld { };
Adding BadVPN network (mostly BPN) tools
2013-11-17 18:48:13 +01:00
badvpn = callPackage ../tools/networking/badvpn {};
banner: a tool to print print large banners to ASCII terminals svn path=/nixpkgs/trunk/; revision=27656
2011-07-08 00:19:52 +02:00
banner = callPackage ../games/banner {};
Adding GNU barcode svn path=/nixpkgs/trunk/; revision=24173
2010-10-08 10:48:34 +02:00
barcode = callPackage ../tools/graphics/barcode {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bc = callPackage ../tools/misc/bc { };
Added bc :P svn path=/nixpkgs/trunk/; revision=4045
2005-10-10 02:55:07 +02:00
bcache-tools: new package Bcache is a Linux kernel block layer cache. It allows one or more fast disk drives such as flash-based solid state drives (SSDs) to act as a cache for one or more slower hard disk drives. This package contains the required user-space tools. User documentation is in Documentation/bcache.txt in the Linux kernel tree. http://bcache.evilpiepirate.org/
2014-02-01 12:30:23 +01:00
bcache-tools = callPackage ../tools/filesystems/bcache-tools { };
* Add bchunk. svn path=/nixpkgs/trunk/; revision=34529
2012-06-17 05:36:22 +02:00
bchunk = callPackage ../tools/cd-dvd/bchunk { };
all-packages.nix: stripped trailing whitespace svn path=/nixpkgs/trunk/; revision=34541
2012-06-18 11:52:37 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bfr = callPackage ../tools/misc/bfr { };
bfr added (pipe buffer) svn path=/nixpkgs/trunk/; revision=12348
2008-07-11 22:27:53 +02:00
bindfs: add expression
2014-08-05 23:57:20 +02:00
bindfs = callPackage ../tools/filesystems/bindfs { };
Add bitbucket-cli to nixpkgs Adding refnil as mainteners Added alias in top-level
2014-07-08 21:58:30 +02:00
bitbucket-cli = pythonPackages.bitbucket-cli;
blockdiag: new package Blockdiag generates block-diagram image from spec-text file (similar to Graphviz). Also add its needed dependencies, funcparserlib and webcolors.
2013-09-21 18:15:18 +02:00
blockdiag = pythonPackages.blockdiag;
bmon: new package bmon is a ncurses network bandwidth monitor. Homepage: http://www.carisma.slowglass.com/~tgr/bmon/
2013-07-25 12:43:40 +02:00
bmon = callPackage ../tools/misc/bmon { };
Bochs: update to version 2.6.6
2014-08-11 02:06:39 +02:00
bochs = callPackage ../applications/virtualization/bochs { wxSupport = false; };
First commit. Added Nix expression for Bochs - "the highly portable x86 emulator".
2013-11-23 02:22:05 +01:00
all-packages: remove gcc47 dependencies now gcc48 is default I checked these and they built fine
2013-12-07 20:10:55 +01:00
boomerang = callPackage ../development/tools/boomerang { };
boomerang: New package from the fork. This adds the boomerang decompiler, which has been forked on github because of some years of inactivity.
2012-08-09 18:58:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bootchart = callPackage ../tools/system/bootchart { };
Adding the bootchart capture script. It worked for me, run standalone, not as init. I tried their website renderer, but it did not work for me. It may be shut down, because their last update is for 2006. Next steps: put it into nixos, and build the renderer (java!). svn path=/nixpkgs/trunk/; revision=18041
2009-10-30 00:15:10 +01:00
Added bro 2.1
2013-05-30 18:13:50 +02:00
bro = callPackage ../applications/networking/ids/bro { };
Added bsod emulator for unix
2012-06-25 16:25:01 +02:00
bsod = callPackage ../misc/emulators/bsod { };
Fix btrfs-progs build http://hydra.nixos.org/build/2842473
2012-07-18 15:21:33 +02:00
btrfsProgs = callPackage ../tools/filesystems/btrfsprogs { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
networking: Add bwm-ng expression.
2013-08-14 13:00:59 +02:00
bwm_ng = callPackage ../tools/networking/bwm-ng { };
byobu 5.37 integration
2013-05-06 13:06:59 +02:00
byobu = callPackage ../tools/misc/byobu { };
all-packages: fix ordering around consul Insertion into lexicographic order seems so difficult :-)
2014-08-14 14:28:08 +02:00
capstone = callPackage ../development/libraries/capstone { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
catdoc = callPackage ../tools/text/catdoc { };
Add catdoc svn path=/nixpkgs/trunk/; revision=21558
2010-05-03 05:45:40 +02:00
Add packages for libzdb, libsearpc, ccnet, seafile-shared, and seafile-client
2014-02-04 20:02:46 +01:00
ccnet = callPackage ../tools/networking/ccnet { };
all-packages: fix ordering around consul Insertion into lexicographic order seems so difficult :-)
2014-08-14 14:28:08 +02:00
consul = callPackage ../servers/consul { };
consul_ui = callPackage ../servers/consul/ui.nix { };
capstone: version 2.1.2 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-08 14:04:11 +02:00
chntpw: new expression
2014-08-04 11:03:49 +02:00
chntpw = callPackage ../tools/security/chntpw { };
nixpkgs: add COPRTHR 1.6 COPRTHR is a very excellent little SDK implementing OpenCL and related tech for regular multicore processors, as well as things like my new Parallella (along with remote/networked OpenCL compute support). Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-07 11:12:25 +02:00
coprthr = callPackage ../development/libraries/coprthr {
flex = flex_2_5_35;
};
all-packages: fix ordering around consul Insertion into lexicographic order seems so difficult :-)
2014-08-14 14:28:08 +02:00
crawl = callPackage ../games/crawl { lua = lua5; };
consul: new package
2014-06-16 00:08:44 +02:00
added cv: Tool that shows the progress of coreutils programs
2014-07-20 15:44:47 +02:00
cv = callPackage ../tools/misc/cv { };
all-packages: fix ordering around consul Insertion into lexicographic order seems so difficult :-)
2014-08-14 14:28:08 +02:00
direnv = callPackage ../tools/misc/direnv { };
Add dungeon crawl stone soup 0.14
2014-07-04 18:26:14 +02:00
ditaa: new package Ditaa is a small command-line utility written in Java, that can convert diagrams drawn using ascii art ('drawings' that contain characters that resemble lines like | / - ), into proper bitmap graphics. Homepage: http://ditaa.sourceforge.net/
2013-09-12 17:25:09 +02:00
ditaa = callPackage ../tools/graphics/ditaa { };
Add DLX simulator. Upstream provides no version number.
2012-12-04 14:29:35 +01:00
dlx = callPackage ../misc/emulators/dlx { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
eggdrop = callPackage ../tools/networking/eggdrop { };
added eggdrop, iftop svn path=/nixpkgs/trunk/; revision=17710
2009-10-08 09:01:55 +02:00
Add package enca 1.13 to tools/text
2012-08-08 01:58:17 +02:00
enca = callPackage ../tools/text/enca { };
Create package for 'fasd'
2014-03-15 20:21:30 +01:00
fasd = callPackage ../tools/misc/fasd {
inherit (haskellPackages) pandoc;
};
fop: new package fop is a XML formatter driven by XSL Formatting Objects (XSL-FO). Homepage: http://xmlgraphics.apache.org/fop/
2013-09-29 21:18:52 +02:00
fop = callPackage ../tools/typesetting/fop { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mcrl = callPackage ../tools/misc/mcrl { };
* added mcrl, mcrl2 and openmpi to all-packages.nix svn path=/nixpkgs/trunk/; revision=15874
2009-06-05 16:36:35 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mcrl2 = callPackage ../tools/misc/mcrl2 { };
* added mcrl, mcrl2 and openmpi to all-packages.nix svn path=/nixpkgs/trunk/; revision=15874
2009-06-05 16:36:35 +02:00
mpdcron: add expression
2014-05-23 00:39:28 +02:00
mpdcron = callPackage ../tools/audio/mpdcron { };
syslog-ng: moved package from tools/misc to tools/system svn path=/nixpkgs/trunk/; revision=28155
2011-08-04 17:59:14 +02:00
syslogng = callPackage ../tools/system/syslog-ng { };
syslog-ng: add missing python build input
2014-01-15 16:51:15 +01:00
New pkg: syslog-ng-incubator A collection of tools and modules for syslog-ng
2014-07-07 18:07:06 +02:00
syslogng_incubator = callPackage ../tools/system/syslog-ng-incubator { };
Add rsyslog 7.2.6 and its dependencies
2013-03-14 14:07:56 +01:00
rsyslog = callPackage ../tools/system/rsyslog { };
Added syslog-ng (and the eventlog library that it depends on). svn path=/nixpkgs/trunk/; revision=13988
2009-02-05 17:50:45 +01:00
added mcrypt
2013-06-27 12:04:46 +02:00
mcrypt = callPackage ../tools/misc/mcrypt { };
mcelog: a tool to access the machine check exceptions logged by the kernel. The kernel indicated that machine check exceptions were logged, but did not tell what kind of exceptions. In my case, this is usually the processor being throttled because it gets too hot (laptop...), but it may also be more severe problems. Anyway, with this tool you can access these logs. svn path=/nixpkgs/trunk/; revision=32547
2012-02-24 21:20:59 +01:00
mcelog = callPackage ../os-specific/linux/mcelog { };
apparix: new package Add directory bookmarks, distant listing, and distant editing to the command line http://micans.org/apparix
2014-04-15 10:40:58 +02:00
apparix = callPackage ../tools/misc/apparix { };
appdata-tools: add new package
2014-05-19 13:26:28 +02:00
appdata-tools = callPackage ../tools/misc/appdata-tools { };
asciidoc: add support for matplotlib filter
2013-09-22 14:29:43 +02:00
asciidoc = callPackage ../tools/typesetting/asciidoc {
Revert "asciidoc: add missing dependencies" This reverts commit aef81d6eb68506426e2004d195125f89922e6a6a. It's really not good to have every little package that depends on asciidoc to pull in 1.5 GiB in dependencies (such as Lilypond).
2013-09-30 13:15:53 +02:00
inherit (pythonPackages) matplotlib numpy aafigure recursivePthLoader;
asciidoc: purify and add asciidocFull attribute The current asciidoc expression is impure; it relies on several tools to be found in PATH at runtime. This commit adds a enableStandardFeatures parameter that, if true, pulls in all dependencies and patches asciidoc to contain full paths to the tools. I've set enableStandardFeatures = false for the existing asciidoc attribute so that the closure size stays unchanged, at 255 MiB. The new asciidocFull attribute (with enableStandardFeatures = true) has a closure size of 1.5 GiB.
2013-09-23 21:26:44 +02:00
enableStandardFeatures = false;
asciidoc: add support for matplotlib filter
2013-09-22 14:29:43 +02:00
};
Add AsciiDoc. svn path=/nixpkgs/trunk/; revision=11039
2008-03-10 16:57:14 +01:00
asciidoc-full: rename attribute from asciidocFull But keep asciidocFull attribute for backwards compatibility (with a timestamp so we can later decide when to finally remove the old attribute).
2014-06-22 22:24:27 +02:00
asciidoc-full = appendToName "full" (asciidoc.override {
asciidoc: purify and add asciidocFull attribute The current asciidoc expression is impure; it relies on several tools to be found in PATH at runtime. This commit adds a enableStandardFeatures parameter that, if true, pulls in all dependencies and patches asciidoc to contain full paths to the tools. I've set enableStandardFeatures = false for the existing asciidoc attribute so that the closure size stays unchanged, at 255 MiB. The new asciidocFull attribute (with enableStandardFeatures = true) has a closure size of 1.5 GiB.
2013-09-23 21:26:44 +02:00
inherit (pythonPackages) pygments;
enableStandardFeatures = true;
});
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
autossh = callPackage ../tools/networking/autossh { };
added autossh 1.4b. svn path=/nixpkgs/trunk/; revision=22018
2010-05-27 21:43:57 +02:00
Simple packaging of bacula. svn path=/nixpkgs/trunk/; revision=28182
2011-08-05 21:18:02 +02:00
bacula = callPackage ../tools/backup/bacula { };
Adds beanstalkd v1.9
2013-11-24 23:26:56 +01:00
beanstalkd = callPackage ../servers/beanstalkd { };
Add bgs, a simple background setter for X
2013-10-01 17:10:18 +02:00
bgs = callPackage ../tools/X11/bgs { };
all-packages.nix: strip trailing whitespace
2013-10-03 16:20:09 +02:00
Add biber-1.8 and dependencies
2014-02-25 17:37:32 +01:00
biber = callPackage ../tools/typesetting/biber {
inherit (perlPackages)
autovivification BusinessISBN BusinessISMN BusinessISSN ConfigAutoConf
DataCompare DataDump DateSimple EncodeEUCJPASCII EncodeHanExtra EncodeJIS2K
ExtUtilsLibBuilder FileSlurp IPCRun3 Log4Perl LWPProtocolHttps ListAllUtils
ListMoreUtils ModuleBuild MozillaCA ReadonlyXS RegexpCommon TextBibTeX
UnicodeCollate UnicodeLineBreak URI XMLLibXMLSimple XMLLibXSLT XMLWriter;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
bibtextools = callPackage ../tools/typesetting/bibtex-tools {
* More cleanup. Updated to the latest Stratego/XT 0.17. svn path=/nixpkgs/trunk/; revision=14610
2009-03-19 15:34:16 +01:00
inherit (strategoPackages016) strategoxt sdf;
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
bittorrent = callPackage ../tools/networking/p2p/bittorrent {
* BitTorrent 5.0.3. * wxPython 2.6.3. svn path=/nixpkgs/trunk/; revision=7341
2006-12-13 21:30:09 +01:00
gui = true;
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
};
* Apply r32435 from the trunk (always build Python with SSL support). Remove .ssl references from some packages missed in that commit. svn path=/nixpkgs/branches/stdenv-updates/; revision=32469
2012-02-22 00:35:35 +01:00
bittornado = callPackage ../tools/networking/p2p/bit-tornado { };
Added BitTornado, as BitTorrent doesn't support IPv6 svn path=/nixpkgs/trunk/; revision=8897
2007-06-20 01:38:01 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
blueman = callPackage ../tools/bluetooth/blueman {
* Added Blueman (a Bluetooth application). * Added obex-data-server and python-notify, needed by Blueman. svn path=/nixpkgs/trunk/; revision=22497
2010-07-06 16:54:22 +02:00
inherit (pythonPackages) notify;
};
* Removed selectVersion. There's no good reason to write `selectVersion ./foo "bar"' instead of `import ./foo/bar.nix'. * Replaced `with args' with formal function arguments in several packages. * Renamed several files to `default.nix'. As a general rule, version numbers should only be included in the filename when there is a reason to keep multiple versions of a package in Nixpkgs. Otherwise, it just makes it harder to update the package. svn path=/nixpkgs/trunk/; revision=18403
2009-11-18 10:39:59 +01:00
bmrsa = builderDefsPackage (import ../tools/security/bmrsa/11.nix) {
Starting migrating old builderDefs packages to builderDefsPackage style. svn path=/nixpkgs/trunk/; revision=13591
2008-12-04 22:01:26 +01:00
inherit unzip;
Added Shamir Secret Sharing Scheme and bmrsa. Fixed libgcrypt svn path=/nixpkgs/trunk/; revision=10928
2008-03-03 13:30:39 +01:00
};
bogofilter: get rid of bdb alias
2013-12-16 14:30:55 +01:00
bogofilter = callPackage ../tools/misc/bogofilter { };
Add Bogofilter, a fast bayesian spam filter. svn path=/nixpkgs/trunk/; revision=10908
2008-03-02 19:35:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bsdiff = callPackage ../tools/compression/bsdiff { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Alphabet, and its order... svn path=/nixpkgs/trunk/; revision=30816
2011-12-09 22:18:09 +01:00
btar = callPackage ../tools/backup/btar { };
bud: new package This adds `bud`, a TLS terminating proxy.
2014-07-08 21:38:55 +02:00
bud = callPackage ../tools/networking/bud {
inherit (pythonPackages) gyp;
};
bup: update to latest git version. why the git version? 0.24b (in nixpkgs) was broken. using 0.25rc1 gave the same error (gcc 4.6 related) Both these versions are over a year old and lots of commits were made after that, including something that fixed building on nix.
2012-07-22 19:50:31 +02:00
bup = callPackage ../tools/backup/bup {
bup: include support for xattrs, acls and fuse on linux this enables the commands "bup meta" and "bup fuse".
2012-08-05 14:02:05 +02:00
inherit (pythonPackages) pyxattr pylibacl setuptools fuse;
inherit (haskellPackages) pandoc;
bup: optionally depend on par2cmdline The default is to use it from path when available, as this is an optional feature.
2013-01-06 18:15:04 +01:00
par2Support = (config.bup.par2Support or false);
bup: update to latest git version. why the git version? 0.24b (in nixpkgs) was broken. using 0.25rc1 gave the same error (gcc 4.6 related) Both these versions are over a year old and lots of commits were made after that, including something that fixed building on nix.
2012-07-22 19:50:31 +02:00
};
add bup: backup system based on the git packfile format [1] https://github.com/apenwarr/bup Signed-off-by: David Guibert <david.guibert@gmail.com> svn path=/nixpkgs/trunk/; revision=28497
2011-08-11 18:33:47 +02:00
Add ori, a secure distributed filesystem.
2014-05-14 20:01:31 +02:00
ori = callPackage ../tools/backup/ori { };
atool: add archiver helper
2012-08-05 23:49:37 +02:00
atool = callPackage ../tools/archivers/atool { };
add bup: backup system based on the git packfile format [1] https://github.com/apenwarr/bup Signed-off-by: David Guibert <david.guibert@gmail.com> svn path=/nixpkgs/trunk/; revision=28497
2011-08-11 18:33:47 +02:00
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
bzip2 = callPackage ../tools/compression/bzip2 { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cabextract = callPackage ../tools/archivers/cabextract { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
added cadaver: a command-line WebDAV client for Unix
2014-07-30 16:55:44 +02:00
cadaver = callPackage ../tools/networking/cadaver { };
cantata: create version 1.3.4
2014-05-03 04:36:20 +02:00
cantata = callPackage ../applications/audio/cantata { };
can-utils: new package CAN userspace utilities and tools (for use with Linux SocketCAN). There is no real "homepage" for this project (the only thing I could find was the gitorious page) and they haven't produced any proper releases (source archives and/or git tags), even though git history goes back to 2006 and things seem stable.
2014-03-09 13:23:46 +01:00
can-utils = callPackage ../os-specific/linux/can-utils { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ccid = callPackage ../tools/security/ccid { };
Adding pcsclite with the opensource ccid usb drivers. This gives a daemon controlling the smartcard reader used to read the Spanish identity card. svn path=/nixpkgs/trunk/; revision=19319
2010-01-09 18:35:57 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ccrypt = callPackage ../tools/security/ccrypt { };
Committing Lluís Batlle's submissions from mailing list posting <45219fb00901110456i6f21db35tbd1894eaea2146ff@mail.gmail.com>: * nixpkgs-ccrypt-1.7-new.patch * nixpkgs-cmake-add-ccmake.patch * nixpkgs-cpufrequtils-005-new.patch * nixpkgs-dwm-5.1-fix.patch * nixpkgs-freeimage-3.11.0-new.patch * nixpkgs-proxychains-3.1-new.patch * nixpkgs-psi-to-0.12.patch * nixpkgs-skype-to-2.0.0.72.patch * nixpkgs-truecrypt-6.1a-fix.patch * nixpkgs-vxl-1.11.0-new.patch * nixpkgs-xkb-popular-esperanto-symbols.patch * nixpkgs-xorg-via-video-fix.patch svn path=/nixpkgs/trunk/; revision=13751
2009-01-12 22:12:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cdecl = callPackage ../development/tools/cdecl { };
Adding cdecl-2.5 svn path=/nixpkgs/trunk/; revision=13833
2009-01-24 22:01:27 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cdrdao = callPackage ../tools/cd-dvd/cdrdao { };
* Move dvd+rw-tools and cdrkit to tools/cd-dvd. * Added cdrdao. svn path=/nixpkgs/trunk/; revision=12426
2008-07-25 15:04:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cdrkit = callPackage ../tools/cd-dvd/cdrkit { };
* Move dvd+rw-tools and cdrkit to tools/cd-dvd. * Added cdrdao. svn path=/nixpkgs/trunk/; revision=12426
2008-07-25 15:04:51 +02:00
Added the ceph filesystem.
2014-04-16 23:42:21 +02:00
ceph = callPackage ../tools/filesystems/ceph { };
Adding cfdg - context-free design grammar svn path=/nixpkgs/trunk/; revision=20166
2010-02-22 11:46:49 +01:00
cfdg = builderDefsPackage ../tools/graphics/cfdg {
cfdg: use default/latest ffmpeg
2013-12-16 14:34:39 +01:00
inherit libpng bison flex ffmpeg;
Adding cfdg - context-free design grammar svn path=/nixpkgs/trunk/; revision=20166
2010-02-22 11:46:49 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
checkinstall = callPackage ../tools/package-management/checkinstall { };
* Automatically build Debian packages using checkinstall, as suggested by Pjotr Prins a while back. This could also be used to generate RPMs for packages that don't have a spec-file. * Added checkinstall to Nixpkgs. However we don't use our own build yet because with it "make install" segfaults in a Debian VM, while the pre-built binary does work. svn path=/nixpkgs/trunk/; revision=13400
2008-11-25 03:20:41 +01:00
* Removed selectVersion. There's no good reason to write `selectVersion ./foo "bar"' instead of `import ./foo/bar.nix'. * Replaced `with args' with formal function arguments in several packages. * Renamed several files to `default.nix'. As a general rule, version numbers should only be included in the filename when there is a reason to keep multiple versions of a package in Nixpkgs. Otherwise, it just makes it harder to update the package. svn path=/nixpkgs/trunk/; revision=18403
2009-11-18 10:39:59 +01:00
cheetahTemplate = builderDefsPackage (import ../tools/text/cheetah-template/2.0.1.nix) {
Upgrade default to python version 2.5.x. svn path=/nixpkgs/trunk/; revision=12910
2008-09-24 10:50:32 +02:00
inherit makeWrapper python;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
Added cheetah-template templating engine svn path=/nixpkgs/trunk/; revision=12053
2008-06-12 12:07:54 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
chkrootkit = callPackage ../tools/security/chkrootkit { };
add chkrootkit. It might need some tweaks to work properly. svn path=/nixpkgs/trunk/; revision=10141
2008-01-14 15:43:24 +01:00
Add chrony. Chrony is a pair of programs which are used to maintain the accuracy of the system clock on a computer.
2013-05-22 00:41:58 +02:00
chrony = callPackage ../tools/networking/chrony { };
Add chunkfs package
2014-01-02 18:20:10 +01:00
chunkfs = callPackage ../tools/filesystems/chunkfs { };
Add chunksync package
2013-12-30 14:21:52 +01:00
chunksync = callPackage ../tools/backup/chunksync { };
Adding cjdns. The executable runs; I haven't tried to run a node.
2013-06-20 20:52:58 +02:00
cjdns = callPackage ../tools/networking/cjdns { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cksfv = callPackage ../tools/networking/cksfv { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
add clementine-1.2.1
2013-12-31 14:51:11 +01:00
clementine = callPackage ../applications/audio/clementine { };
Add ciopfs
2012-07-26 05:16:57 +02:00
ciopfs = callPackage ../tools/filesystems/ciopfs { };
colord, gusb: package. Part of #517.
2013-05-10 19:17:36 +02:00
colord = callPackage ../tools/misc/colord { };
gnome3.gnome_control_center: build and fix runtime deps
2014-02-08 12:30:10 +01:00
colord-gtk = callPackage ../tools/misc/colord-gtk { };
Add colordiff package. svn path=/nixpkgs/trunk/; revision=26860
2011-04-17 10:26:56 +02:00
colordiff = callPackage ../tools/text/colordiff { };
concurrencykit: version 0.4.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-01 03:48:58 +02:00
concurrencykit = callPackage ../development/libraries/concurrencykit { };
Add 'connect' for traversing SOCKS proxies
2012-11-28 23:29:11 +01:00
connect = callPackage ../tools/networking/connect { };
Adding ttysnoop pty redirector
2013-10-20 16:42:53 +02:00
conspy = callPackage ../os-specific/linux/conspy {};
connman: new packages ConnMan v1.20 and connman-ui
2014-01-04 01:13:26 +01:00
connman = callPackage ../tools/networking/connman { };
connmanui = callPackage ../tools/networking/connmanui { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
convertlit = callPackage ../tools/text/convertlit { };
* Added convertlit, a tool for converting Microsoft Reader ebooks, plus its dependency libtommath. svn path=/nixpkgs/trunk/; revision=12606
2008-08-12 21:57:35 +02:00
Add collectd 5.4.0
2013-08-30 11:58:02 +02:00
collectd = callPackage ../tools/system/collectd { };
Add colormake
2013-07-25 11:35:51 +02:00
colormake = callPackage ../development/tools/build-managers/colormake { };
add cowsay svn path=/nixpkgs/trunk/; revision=31936
2012-01-30 20:05:24 +01:00
cowsay = callPackage ../tools/misc/cowsay { };
Add cpuminer, multi-threaded Litecoin and Bitcoin miner
2014-01-13 00:02:30 +01:00
cpuminer = callPackage ../tools/misc/cpuminer { };
cpuminer-multi: initial expression
2014-06-29 06:05:39 +02:00
cpuminer-multi = callPackage ../tools/misc/cpuminer-multi { };
cuetools-1.3.1
2013-03-18 00:18:36 +01:00
cuetools = callPackage ../tools/cd-dvd/cuetools { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
unifdef = callPackage ../development/tools/misc/unifdef { };
- Some Ruby interpreter bumped version - Kernel headers 2.6.18 added (XEN virtual images) - unifdef package added for kernel headers 2.6.18 - Python Zope and 4suite added - Trying bioconductor packages with R-lang (still failing) - Bumped gmp version - Added rq cluster runner - still requires extra gems (installs, but does not run) svn path=/nixpkgs/trunk/; revision=12766
2008-08-29 15:53:28 +02:00
Keep nixpkgs backwards-compatible at least 1 version
2012-12-17 16:21:55 +01:00
"unionfs-fuse" = callPackage ../tools/filesystems/unionfs-fuse { };
Add unionfs-fuse
2012-12-16 02:32:10 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
usb_modeswitch = callPackage ../development/tools/misc/usb-modeswitch { };
adding wvdial, wvstreams, usb_modeswitch svn path=/nixpkgs/trunk/; revision=21131
2010-04-16 17:56:28 +02:00
add anthy, Japanese input method
2014-08-27 09:39:34 +02:00
anthy = callPackage ../tools/inputmethods/anthy { };
biosdevname: add package
2014-05-13 06:31:10 +02:00
biosdevname = callPackage ../tools/networking/biosdevname { };
ClamAV: package.
2012-07-23 16:21:25 +02:00
clamav = callPackage ../tools/security/clamav { };
all-packages.nix: strip trailing whitespace
2012-07-29 21:34:20 +02:00
Add cloc-1.58
2013-03-16 14:59:35 +01:00
cloc = callPackage ../tools/misc/cloc {
inherit (perlPackages) perl AlgorithmDiff RegexpCommon;
};
Add CLooG, an alternative to CLooG-PPL based on the integer set library, an optional dependency for GCC 4.6.0 svn path=/nixpkgs/trunk/; revision=26635
2011-03-31 23:25:08 +02:00
cloog = callPackage ../development/libraries/cloog { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cloogppl = callPackage ../development/libraries/cloog-ppl { };
Add CLooG-PPL, an optional dependency of GCC 4.4. svn path=/nixpkgs/trunk/; revision=16422
2009-07-18 23:28:10 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
convmv = callPackage ../tools/misc/convmv { };
Add convmv svn path=/nixpkgs/trunk/; revision=22444
2010-07-03 10:06:01 +02:00
cool-old-term: add 0.9 (close #3685, #3575)
2014-08-19 23:35:33 +02:00
cool-old-term = callPackage ../applications/misc/cool-old-term { };
coreutils: 8.20 does build on Darwin Where gcc is: i686-apple-darwin11-llvm-gcc-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.11.00)
2013-09-07 16:30:23 +02:00
coreutils = callPackage ../tools/misc/coreutils
Setting coreutils to 8.20 for linux, 8.19 for darwin As Eelco noted in 0ecd1f62c799dffbdbd4bc1ba8120bfb4a4c7a6f, Darwin can't build 8.20. But linux can't build 8.19 now.
2013-01-02 20:01:49 +01:00
{
# TODO: Add ACL support for cross-Linux.
aclSupport = crossSystem == null && stdenv.isLinux;
};
Porting changes from stdenv-updates into this branch. This comes from: svn diff ^/nixpkgs/trunk/@18255 ^/nixpkgs/branches/stdenv-updates/ > diff patch -p0 < diff and then adding into svn all files new from the patch. trunk@18255 comes from the last time I updated stdenv-updates from trunk. svn path=/nixpkgs/stdenv-updates2/; revision=18272
2009-11-08 01:32:12 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cpio = callPackage ../tools/archivers/cpio { };
* Converting packages. This is the minimal Nix stdenv for building the ATerm library. svn path=/nixpkgs/trunk/; revision=459
2003-11-02 18:42:19 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cromfs = callPackage ../tools/archivers/cromfs { };
Added cromfs - patch by Lluis Batlle svn path=/nixpkgs/trunk/; revision=13700
2009-01-04 18:24:11 +01:00
Minor cleanup
2012-11-29 14:40:25 +01:00
cron = callPackage ../tools/system/cron { };
* Added cron. svn path=/nixpkgs/trunk/; revision=7618
2007-01-10 16:44:58 +01:00
tweak
2014-06-19 13:53:03 +02:00
cudatoolkit5 = callPackage ../development/compilers/cudatoolkit/5.5.nix {
Added cuda6 compiler as package cudatoolkit6.
2014-06-19 13:24:21 +02:00
python = python26;
};
cudatoolkit6 = callPackage ../development/compilers/cudatoolkit/6.0.nix {
Adding NVIDIA CUDA toolkit and haskell-accelerate-cuda plus deps. svn path=/nixpkgs/trunk/; revision=34186
2012-05-20 19:38:03 +02:00
python = python26;
};
tweak
2014-06-19 13:53:03 +02:00
cudatoolkit = cudatoolkit5;
Minor cleanup
2012-11-29 14:40:25 +01:00
curl = callPackage ../tools/networking/curl rec {
* curl: build with OpenSSL (https) support by default. * Some fetchurl-related refactoring. The `realCurl' attribute is gone, `curl' is the real thing. To prevent an infinite recursion in `fetchurl' (because it depends on curl and building curl needs fetchurl), curl and its dependencies (openssl, zlib, perl) use `fetchurlBoot', which is the fetchurl used by the previous bootstrap phase (e.g. the statically linked version of curl for stdenv-linux). So as a result you can use https:// urls almost everywhere. There's also some hackery to prevent a different curl from being built in every stdenv-linux bootstrap phase (namely the stdenv.fetchurl attribute which allows fetchurl to be overriden everywhere). svn path=/nixpkgs/trunk/; revision=11905
2008-05-27 09:49:55 +02:00
fetchurl = fetchurlBoot;
Minor cleanup
2012-11-29 14:40:25 +01:00
zlibSupport = true;
Add optional scp support to curl svn path=/nixpkgs/trunk/; revision=22976
2010-08-05 23:06:45 +02:00
sslSupport = zlibSupport;
* CURL: build without scp support on Cygwin because libssh2 doesn't build. svn path=/nixpkgs/trunk/; revision=23142
2010-08-12 13:54:55 +02:00
scpSupport = zlibSupport && !stdenv.isSunOS && !stdenv.isCygwin;
* curl: build with OpenSSL (https) support by default. * Some fetchurl-related refactoring. The `realCurl' attribute is gone, `curl' is the real thing. To prevent an infinite recursion in `fetchurl' (because it depends on curl and building curl needs fetchurl), curl and its dependencies (openssl, zlib, perl) use `fetchurlBoot', which is the fetchurl used by the previous bootstrap phase (e.g. the statically linked version of curl for stdenv-linux). So as a result you can use https:// urls almost everywhere. There's also some hackery to prevent a different curl from being built in every stdenv-linux bootstrap phase (namely the stdenv.fetchurl attribute which allows fetchurl to be overriden everywhere). svn path=/nixpkgs/trunk/; revision=11905
2008-05-27 09:49:55 +02:00
};
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Gratuitous Space Battles. Needs libcurl.so.3, so put an old version of that in, too
2013-09-16 06:07:11 +02:00
curl3 = callPackage ../tools/networking/curl/7.15.nix rec {
zlibSupport = true;
sslSupport = zlibSupport;
};
Add curl-unix-socket, Run HTTP requests over UNIX socket
2014-09-04 12:08:34 +02:00
curl_unix_socket = callPackage ../tools/networking/curl-unix-socket rec { };
Add cunit svn path=/nixpkgs/trunk/; revision=29069
2011-09-07 03:12:38 +02:00
cunit = callPackage ../tools/misc/cunit { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
curlftpfs = callPackage ../tools/filesystems/curlftpfs { };
Added curlftpfs which is for mounting ftp's with fuse. svn path=/nixpkgs/trunk/; revision=9520
2007-10-25 16:07:50 +02:00
Add cutter, TCP/IP Connection cutting
2014-05-20 12:37:20 +02:00
cutter = callPackage ../tools/networking/cutter { };
Minor cleanup
2012-11-29 14:40:25 +01:00
dadadodo = builderDefsPackage (import ../tools/text/dadadodo) { };
Adding fetchmtn, including fetchmtn and fetchgit in builder-defs, updating monotone-viz. Adding dadadodo. svn path=/nixpkgs/trunk/; revision=16207
2009-07-07 12:04:32 +02:00
Add snort-2.9.4.6
2013-05-30 15:05:39 +02:00
daq = callPackage ../applications/networking/ids/daq { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dar = callPackage ../tools/archivers/dar { };
Adding dar (disk archiver with indexable archives) - patch by Lluis Batlle svn path=/nixpkgs/trunk/; revision=13695
2009-01-03 16:11:52 +01:00
all-packages.nix: remove redundant 'neon = neon029' overrides
2013-02-21 12:02:15 +01:00
davfs2 = callPackage ../tools/filesystems/davfs2 { };
* davfs2 updated to 1.4.5. * neon updated to 0.28.6. svn path=/nixpkgs/trunk/; revision=18841
2009-12-08 14:08:27 +01:00
add dbench svn path=/nixpkgs/trunk/; revision=28807
2011-08-25 03:00:25 +02:00
dbench = callPackage ../development/tools/misc/dbench { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dcraw = callPackage ../tools/graphics/dcraw { };
Adding dcraw. svn path=/nixpkgs/trunk/; revision=14904
2009-04-06 19:50:17 +02:00
Adding Debian devscripts. Mostly for uscan. I plan to later use uscan for simplifying package updates in some NixPkgs packages. I have no code for that now. I added Perl packages File::DesktopEntry and File::BaseDir in a slightly hascky way because one part of the installation system replaced PREFIX= with --prefix= and the other complained that it doesn't know what to do with --prefix=. I checked that a script using File::DesktopEntry works, and I don't know enough Perl to rewrite buildPerlPackage and hope that my change is an improvement. I removed trnaslated manpages because it uses po4a which has some more Debian-specific dependencies of its own.
2012-10-07 16:02:46 +02:00
debian_devscripts = callPackage ../tools/misc/debian-devscripts {
inherit (perlPackages) CryptSSLeay LWP TimeDate DBFile FileDesktopEntry;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
debootstrap = callPackage ../tools/misc/debootstrap { };
adding debootstrap (bootstrap debian in a chroot) svn path=/nixpkgs/trunk/; revision=17709
2009-10-08 02:54:31 +02:00
Applying the patch adding 'detox' from Tom Ridge and Karn Kallio. svn path=/nixpkgs/trunk/; revision=23655
2010-09-06 09:21:08 +02:00
detox = callPackage ../tools/misc/detox { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ddclient = callPackage ../tools/networking/ddclient { };
* ddclient svn path=/nixpkgs/trunk/; revision=17183
2009-09-16 13:53:09 +02:00
Adding dd_rescue - this is not the same as GNU ddrescue which has not been updated for a long time svn path=/nixpkgs/trunk/; revision=24801
2010-11-22 09:40:10 +01:00
dd_rescue = callPackage ../tools/system/dd_rescue { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ddrescue = callPackage ../tools/system/ddrescue { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
add deluge to top-level packages
2013-03-27 02:36:10 +01:00
deluge = pythonPackages.deluge;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
desktop_file_utils = callPackage ../tools/misc/desktop-file-utils { };
Use $NIXPKGS_CONFIG to determine whether ghostscript has cups support. svn path=/nixpkgs/trunk/; revision=14275
2009-02-27 14:44:31 +01:00
Add despotify
2012-11-25 13:00:12 +01:00
despotify = callPackage ../development/libraries/despotify { };
Apply makeOverridable to stdenv This removes the need for hacks like stdenv.regenerate. It also ensures that overrideGCC is now stackable (so ‘stdenv = useGoldLinker clangStdenv’ works).
2014-02-04 17:18:38 +01:00
dev86 = callPackage ../development/compilers/dev86 { };
Adding dev86 (I'll try to get virtualbox built) svn path=/nixpkgs/trunk/; revision=13844
2009-01-25 15:31:24 +01:00
* dnsmasq updated to 2.59. svn path=/nixpkgs/trunk/; revision=32334
2012-02-16 19:03:12 +01:00
dnsmasq = callPackage ../tools/networking/dnsmasq { };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
Adding dnstop svn path=/nixpkgs/trunk/; revision=30209
2011-11-03 19:43:48 +01:00
dnstop = callPackage ../tools/networking/dnstop { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dhcp = callPackage ../tools/networking/dhcp { };
add findutilsStatic svn path=/nixpkgs/trunk/; revision=6250
2006-08-26 11:44:39 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dhcpcd = callPackage ../tools/networking/dhcpcd { };
* dhcpcd, another DHCP client (not tested). Hopefully it works better than dhclient in conjunction with wpa_supplicant. svn path=/nixpkgs/trunk/; revision=16411
2009-07-17 13:41:19 +02:00
Add di package
2014-08-28 14:16:11 +02:00
di = callPackage ../tools/system/di { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
diffstat = callPackage ../tools/text/diffstat { };
Add diffstat. (by Vincent Ordy) svn path=/nixpkgs/trunk/; revision=11823
2008-05-14 09:58:32 +02:00
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
diffutils = callPackage ../tools/text/diffutils { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
wgetpaste is a handy shell utility getting things pasted on pasting services online svn path=/nixpkgs/trunk/; revision=33450
2012-03-28 15:21:42 +02:00
wgetpaste = callPackage ../tools/text/wgetpaste { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dirmngr = callPackage ../tools/security/dirmngr { };
Mass GnuPG upgrade gnupg tests fail. Will try to fix later. svn path=/nixpkgs/trunk/; revision=21884
2010-05-19 22:58:56 +02:00
add disper svn path=/nixpkgs/trunk/; revision=29845
2011-10-14 20:04:34 +02:00
disper = callPackage ../tools/misc/disper { };
dmd: Add (D language compiler).
2014-01-10 19:09:52 +01:00
dmd = callPackage ../development/compilers/dmd { };
added dmg2img-1.6.2 svn path=/nixpkgs/trunk/; revision=25667
2011-01-22 13:28:59 +01:00
dmg2img = callPackage ../tools/misc/dmg2img { };
docbook2odf: new package Tested like this: nix-build -A docbook2odf ./result/bin/docbook2odf --verbose --debug result/share/doc/docbook2odf/examples/book.docbook swriter book.odt # verify that the document looks ok
2013-09-25 23:30:02 +02:00
docbook2odf = callPackage ../tools/typesetting/docbook2odf {
inherit (perlPackages) PerlMagick;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
docbook2x = callPackage ../tools/typesetting/docbook2x {
* Drop the "perl" prefix from Perl attribute names. It's redundant now that Perl packages are in their own namespace (perlPackages.<pkg>). svn path=/nixpkgs/trunk/; revision=15176
2009-04-20 14:49:35 +02:00
inherit (perlPackages) XMLSAX XMLParser XMLNamespaceSupport;
Add docbook2x. svn path=/nixpkgs/trunk/; revision=11051
2008-03-11 10:34:17 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dosfstools = callPackage ../tools/filesystems/dosfstools { };
Added dosfstools svn path=/nixpkgs/trunk/; revision=10487
2008-02-04 05:41:55 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dotnetfx35 = callPackage ../development/libraries/dotnetfx35 { };
Commited my experimental Visual C# build function. Currently, it should only be used by brave people svn path=/nixpkgs/trunk/; revision=22272
2010-06-15 13:16:35 +02:00
dotnetfx 4.0 is now the default svn path=/nixpkgs/trunk/; revision=29628
2011-10-04 15:28:32 +02:00
dotnetfx40 = callPackage ../development/libraries/dotnetfx40 { };
Commited my experimental Visual C# build function. Currently, it should only be used by brave people svn path=/nixpkgs/trunk/; revision=22272
2010-06-15 13:16:35 +02:00
add dolphinEmu and dolphinEmuMaster Dolphin is a high quality, open source Gamecube/Wii/Triforce emulator for Windows, Mac OS X and Linux
2014-09-02 10:19:44 +02:00
dolphinEmu = callPackage ../misc/emulators/dolphin-emu { };
dolphinEmuMaster = callPackage ../misc/emulators/dolphin-emu/master.nix { };
dropbear: update to 2013.58, and build dynamically I had to do a trick with GNU make, to allow it to find libs.
2013-06-18 22:53:19 +02:00
dropbear = callPackage ../tools/networking/dropbear { };
Adding dropbear, a small implementation of ssh2 client and server. I made it statically build by default I had to fix the zlib static cross-build, because the native stripping corrupted the target static library. It is not the first time I see this. I add drobear to the cross-built packages for hydra. svn path=/nixpkgs/trunk/; revision=20518
2010-03-10 00:11:12 +01:00
add dtach-0.8 svn path=/nixpkgs/trunk/; revision=30497
2011-11-20 22:48:56 +01:00
dtach = callPackage ../tools/misc/dtach { };
duo_unix: version 1.9.7 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-02-18 06:15:18 +01:00
duo-unix = callPackage ../tools/security/duo-unix { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
duplicity = callPackage ../tools/backup/duplicity {
duplicity: add missing 'lockfile' build input
2014-03-08 13:28:50 +01:00
inherit (pythonPackages) boto lockfile;
Add gnupg1 compatibility wrapper Gnupg1compat is symlinked gnupg2 with two additional symlinks: gpg->gpg2 and gpgv->gpgv2. Move original gnupg 1.x to gnupg1orig. Set default gnupg1 to gnupg1compat. svn path=/nixpkgs/trunk/; revision=21888
2010-05-19 22:59:20 +02:00
gnupg = gnupg1;
Adding 'duplicity', and its dependency 'librsync' svn path=/nixpkgs/trunk/; revision=19813
2010-02-04 14:42:41 +01:00
};
duply: new package Duply is a shell front end for the duplicity backup tool http://duplicity.nongnu.org/. It greatly simplifies it's usage by implementing backup job profiles, batch commands and more. Who says secure backups on non-trusted spaces are no child's play? Homepage: http://duply.net/
2013-08-21 21:56:33 +02:00
duply = callPackage ../tools/backup/duply { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dvdplusrwtools = callPackage ../tools/cd-dvd/dvd+rw-tools { };
* Move dvd+rw-tools and cdrkit to tools/cd-dvd. * Added cdrdao. svn path=/nixpkgs/trunk/; revision=12426
2008-07-25 15:04:51 +02:00
Add dvgrab. svn path=/nixpkgs/trunk/; revision=28789
2011-08-24 16:55:48 +02:00
dvgrab = callPackage ../tools/video/dvgrab { };
add dvtm 0.10
2014-01-01 14:55:49 +01:00
dvtm = callPackage ../tools/misc/dvtm { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
e2fsprogs = callPackage ../tools/filesystems/e2fsprogs { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
Add easyrsa
2013-07-10 21:00:56 +02:00
easyrsa = callPackage ../tools/networking/easyrsa { };
Add ebook-tools-0.1.1 svn path=/nixpkgs/trunk/; revision=23189
2010-08-16 14:40:03 +02:00
ebook_tools = callPackage ../tools/text/ebook-tools { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ecryptfs = callPackage ../tools/security/ecryptfs { };
Adding ecryptfs, and one of its dependencies: keyutils. (I have not tried whether they work) svn path=/nixpkgs/trunk/; revision=19645
2010-01-25 11:34:47 +01:00
editres: add version 1.0.6 The tool doesn't seem to work well for me. Not sure whether I'm building it wrong, maybe?
2013-07-04 14:12:42 +02:00
editres = callPackage ../tools/graphics/editres {
inherit (xlibs) libXt libXaw;
inherit (xorg) utilmacros;
};
Minor cleanup
2012-11-29 14:40:25 +01:00
edk2 = callPackage ../development/compilers/edk2 { };
Add Intel's EDK svn path=/nixpkgs/trunk/; revision=33058
2012-03-14 05:18:52 +01:00
Add emscripten: LLVM to JavaScript compiler
2014-07-12 17:17:50 +02:00
emscripten = callPackage ../development/compilers/emscripten { };
emscriptenfastcomp = callPackage ../development/compilers/emscripten-fastcomp { };
Adding the efibootmgr, patch sent by Shea Levy. svn path=/nixpkgs/trunk/; revision=26456
2011-03-22 14:21:24 +01:00
efibootmgr = callPackage ../tools/system/efibootmgr { };
efivar: Add derivation
2014-06-11 01:13:28 +02:00
efivar = callPackage ../tools/system/efivar { };
Add evemu tool to emulate and record input device event data [Bjørn Forsman: * wrap some long lines * tweak meta attrs (don't repeat package name, s/meta.maintainer/meta.maintainers/) * provide a version number (v2.0) for 'evemu' (for nix-env) ]
2014-07-22 17:37:13 +02:00
evemu = callPackage ../tools/system/evemu { };
Add elasticsearch 0.20.5
2013-03-07 12:36:29 +01:00
elasticsearch = callPackage ../servers/search/elasticsearch { };
elasticsearch: add support for plugins
2014-07-05 12:09:53 +02:00
elasticsearchPlugins = recurseIntoAttrs (
callPackage ../servers/search/elasticsearch/plugins.nix { }
);
emv: Initial install script
2014-07-25 09:20:17 +02:00
emv = callPackage ../tools/misc/emv { };
hugin, enblend-enfuse: enbaleParallelBuilding, default boost Also unset meta.broken.
2014-08-12 21:17:53 +02:00
enblendenfuse = callPackage ../tools/graphics/enblend-enfuse { };
Adding enblend-fuse, libxmi and hugin. Maybe hugin doesn't run well enough still. svn path=/nixpkgs/trunk/; revision=14894
2009-04-05 23:41:38 +02:00
encfs: packaged. Patch by Ambrus Kaposi. svn path=/nixpkgs/trunk/; revision=24900
2010-11-28 10:59:13 +01:00
encfs = callPackage ../tools/filesystems/encfs { };
enscript: Build with the default GCC
2014-07-23 11:25:38 +02:00
enscript = callPackage ../tools/text/enscript { };
add grub svn path=/nixpkgs/trunk/; revision=3391
2005-07-21 13:26:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ethtool = callPackage ../tools/misc/ethtool { };
add man svn path=/nixpkgs/trunk/; revision=3669
2005-08-23 16:19:16 +02:00
Add ettercap, a comprehensive suite for man in the middle attacks
2013-10-03 15:35:34 +02:00
ettercap = callPackage ../applications/networking/sniffers/ettercap { };
* Update euca2ools. svn path=/nixpkgs/trunk/; revision=33762
2012-04-12 16:16:23 +02:00
euca2ools = callPackage ../tools/virtualization/euca2ools { pythonPackages = python26Packages; };
* Added euca2ools. svn path=/nixpkgs/branches/modular-python/; revision=26607
2011-03-30 16:37:53 +02:00
Add evtest, a simple tool for input event debugging
2013-02-20 21:00:48 +01:00
evtest = callPackage ../applications/misc/evtest { };
Add gnome3.nautilus and remove gnome2.nautilus (didn't compile) Some icons are still missing (and theme), didn't find a way to fix that.
2014-01-09 17:21:19 +01:00
exempi = callPackage ../development/libraries/exempi { };
execline: new package Execline is a small scripting language, to be used in place of a shell in non-interactive scripts.
2014-08-23 06:40:52 +02:00
execline = callPackage ../tools/misc/execline { };
New exercism package
2014-07-10 14:49:44 +02:00
exercism = callPackage ../development/tools/exercism { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
exif = callPackage ../tools/graphics/exif { };
Adding exiftags svn path=/nixpkgs/trunk/; revision=17748
2009-10-11 17:52:27 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
exiftags = callPackage ../tools/graphics/exiftags { };
* Added expect. svn path=/nixpkgs/trunk/; revision=10877
2008-02-27 16:48:53 +01:00
add extundelete
2013-07-08 21:08:40 +02:00
extundelete = callPackage ../tools/filesystems/extundelete { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
expect = callPackage ../tools/misc/expect { };
added fcron svn path=/nixpkgs/trunk/; revision=13192
2008-11-04 22:40:39 +01:00
f2fs-tools: initial expression
2014-03-23 02:47:37 +01:00
f2fs-tools = callPackage ../tools/filesystems/f2fs-tools { };
fabric: new expression
2013-06-11 00:23:35 +02:00
fabric = pythonPackages.fabric;
fail2ban: systemd support - upgrade fail2ban to 0.9 - override systemd to enable python support and include sqlite3 module - make fail2ban enablable
2014-08-02 03:11:09 +02:00
fail2ban = callPackage ../tools/security/fail2ban {
systemd = systemd.override {
pythonSupport = true;
};
};
* Added fail2ban, a program that scans log files for repeated failing login attempts and bans IP addresses. svn path=/nixpkgs/trunk/; revision=34148
2012-05-17 00:58:49 +02:00
Adding fakeroot. svn path=/nixpkgs/trunk/; revision=25440
2011-01-06 11:43:32 +01:00
fakeroot = callPackage ../tools/system/fakeroot { };
Add fakechroot
2014-01-31 14:25:26 +01:00
fakechroot = callPackage ../tools/system/fakechroot { };
add fcitx-4.2.7
2013-01-28 04:35:03 +01:00
fcitx = callPackage ../tools/inputmethods/fcitx { };
Add GNU fdisk. svn path=/nixpkgs/trunk/; revision=16626
2009-08-10 00:15:40 +02:00
add fcitx-anthy
2014-08-27 11:05:14 +02:00
fcitx-anthy = callPackage ../tools/inputmethods/fcitx/fcitx-anthy.nix { };
* Added fail2ban, a program that scans log files for repeated failing login attempts and bans IP addresses. svn path=/nixpkgs/trunk/; revision=34148
2012-05-17 00:58:49 +02:00
fcron = callPackage ../tools/system/fcron { };
adding figlet svn path=/nixpkgs/trunk/; revision=15316
2009-04-26 13:06:48 +02:00
Adding fdm svn path=/nixpkgs/trunk/; revision=24409
2010-10-22 00:03:36 +02:00
fdm = callPackage ../tools/networking/fdm {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
figlet = callPackage ../tools/misc/figlet { };
file = callPackage ../tools/misc/file { };
Added the package man-pages. svn path=/nixpkgs/trunk/; revision=6071
2006-08-08 02:09:27 +02:00
Adding filegive, my file sending program
2013-05-02 09:32:23 +02:00
filegive = callPackage ../tools/networking/filegive { };
Added fileschanged version 0.6.9. svn path=/nixpkgs/trunk/; revision=24511
2010-10-28 13:10:09 +02:00
fileschanged = callPackage ../tools/misc/fileschanged { };
Remove findutils 4.2.27 We only used this version on Darwin, but the regular findutils seems to build fine.
2012-11-29 12:02:07 +01:00
findutils = callPackage ../tools/misc/findutils { };
* Oops, the bootstrap tools contained an impure gzip/gunzip. * To prevent this kind of thing, check that all tools are statically linked. * Use findutils 4.2.27, 4.2.28 doesn't build with dietlibc. svn path=/nixpkgs/trunk/; revision=6881
2006-10-28 00:50:58 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
finger_bsd = callPackage ../tools/networking/bsd-finger { };
finger client and daemon added svn path=/nixpkgs/trunk/; revision=10364
2008-01-28 20:51:14 +01:00
Adding fio, the flexible IO tester. svn path=/nixpkgs/trunk/; revision=34275
2012-05-29 16:21:55 +02:00
fio = callPackage ../tools/system/fio { };
mpack: add version 1.6
2013-08-17 14:42:06 +02:00
flashtool: add version 0.9.14.0
2014-02-28 11:02:31 +01:00
flashtool = callPackage_i686 ../development/mobile/flashtool {
flashtool: clean up the build some more
2014-02-28 12:13:29 +01:00
platformTools = androidenv.platformTools;
flashtool: add version 0.9.14.0
2014-02-28 11:02:31 +01:00
};
Adding flashrom BIOS update utility. Patch by Edward O'Callaghan
2014-08-28 23:27:28 +02:00
flashrom = callPackage ../tools/misc/flashrom { };
Add expression for flpsed
2013-08-12 14:14:42 +02:00
flpsed = callPackage ../applications/editors/flpsed { };
Adding fio, the flexible IO tester. svn path=/nixpkgs/trunk/; revision=34275
2012-05-29 16:21:55 +02:00
added flvstreamer svn path=/nixpkgs/trunk/; revision=24884
2010-11-26 21:04:07 +01:00
flvstreamer = callPackage ../tools/networking/flvstreamer { };
Added 'bumblebee', a package that facilitates NVidia Optimus graphics with X11. Note: it relies heavily on 'virtualgl'. This also makes the approach taken by bumblebee not very effective. So, this package is actually mainly useful for shutting down your card so that it does not consume power/produce heat. See the comments in bumblebee/default.nix svn path=/nixpkgs/trunk/; revision=32036
2012-02-05 01:51:35 +01:00
libbsd = callPackage ../development/libraries/libbsd { };
adding lprof
2013-03-29 02:06:34 +01:00
lprof = callPackage ../tools/graphics/lprof { };
add fdk-aac-0.1.3
2014-01-02 22:11:02 +01:00
fdk_aac = callPackage ../development/libraries/fdk-aac { };
* Added flvtool2. svn path=/nixpkgs/trunk/; revision=29116
2011-09-08 23:48:10 +02:00
flvtool2 = callPackage ../tools/video/flvtool2 { };
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
fontforge = lowPrio (callPackage ../tools/misc/fontforge { });
* Use FontForge to give Wine better fonts. svn path=/nixpkgs/trunk/; revision=9181
2007-08-21 14:31:33 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
fontforgeX = callPackage ../tools/misc/fontforge {
* Drop pkgsOverriden. svn path=/nixpkgs/trunk/; revision=22823
2010-07-30 14:10:24 +02:00
withX11 = true;
* Purity fix in fontforge: don't look for /usr/include/libxml. svn path=/nixpkgs/trunk/; revision=11288
2008-03-26 13:57:30 +01:00
};
Added FontForge with X11 interface svn path=/nixpkgs/trunk/; revision=10918
2008-03-02 23:02:28 +01:00
Adding forktty terminal connection/disconnection helper
2013-10-20 18:26:36 +02:00
forktty = callPackage ../os-specific/linux/forktty {};
add fortune svn path=/nixpkgs/trunk/; revision=33462
2012-03-29 09:15:40 +02:00
fortune = callPackage ../tools/misc/fortune { };
Making xfe find and load icons fine I added more dependencies to fox, for that. I tried to add mesa too, but it wasn't trivial for it to find it, so I took it out.
2013-05-16 23:35:48 +02:00
fox = callPackage ../development/libraries/fox/default.nix {
libpng = libpng12;
};
Add xfe-1.33 and fox-1.6.9 This specific version of fox is required by xfe Signed-off-by: Baptist BENOIST <return_0@live.com>
2012-10-16 17:30:44 +02:00
fox_1_6 = callPackage ../development/libraries/fox/fox-1.6.nix { };
Add fox-1.7.9 Signed-off-by: Baptist BENOIST <return_0@live.com>
2012-10-16 17:30:26 +02:00
Add fping, a more scriptable ping
2013-02-04 10:45:47 +01:00
fping = callPackage ../tools/networking/fping {};
F-Prot: package
2012-07-24 09:47:37 +02:00
fprot = callPackage ../tools/security/fprot { };
Adding FreeIPMI svn path=/nixpkgs/trunk/; revision=25679
2011-01-24 08:06:17 +01:00
freeipmi = callPackage ../tools/system/freeipmi {};
FreeTalk is not ready for Guile 2.0 svn path=/nixpkgs/trunk/; revision=25999
2011-02-16 23:21:29 +01:00
freetalk = callPackage ../applications/networking/instant-messengers/freetalk {
guile = guile_1_8;
};
Adding freetalk svn path=/nixpkgs/trunk/; revision=25323
2010-12-29 20:20:55 +01:00
Add freetds svn path=/nixpkgs/trunk/; revision=30378
2011-11-10 23:20:48 +01:00
freetds = callPackage ../development/libraries/freetds { };
added ftgl, gource svn path=/nixpkgs/trunk/; revision=24379
2010-10-20 12:53:45 +02:00
ftgl = callPackage ../development/libraries/ftgl { };
Updating opencascade to 6.5.2. I had to bring an older ftgl in. svn path=/nixpkgs/trunk/; revision=32742
2012-03-02 14:47:37 +01:00
ftgl212 = callPackage ../development/libraries/ftgl/2.1.2.nix { };
ffmpeg: Add previous version to fix fuppes. svn path=/nixpkgs/trunk/; revision=27980
2011-07-27 23:00:09 +02:00
fuppes = callPackage ../tools/networking/fuppes {
ffmpeg = ffmpeg_0_6_90;
};
dos2unix and unix2dos provided by griswold svn path=/nixpkgs/trunk/; revision=19409
2010-01-13 22:09:55 +01:00
Adding a skeleton for a fsfs expression, but it still does not build. svn path=/nixpkgs/trunk/; revision=26631
2011-03-31 23:08:50 +02:00
fsfs = callPackage ../tools/filesystems/fsfs { };
* Added fuse-zip, a FUSE filesystem for accessing zip files. svn path=/nixpkgs/trunk/; revision=32143
2012-02-08 16:45:26 +01:00
fuse_zip = callPackage ../tools/filesystems/fuse-zip { };
fuse-exfat: add FUSE-mounter for exFAT devices
2013-09-06 23:10:14 +02:00
fuse_exfat = callPackage ../tools/filesystems/fuse-exfat { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dos2unix = callPackage ../tools/text/dos2unix { };
dos2unix and unix2dos provided by griswold svn path=/nixpkgs/trunk/; revision=19409
2010-01-13 22:09:55 +01:00
uni2ascii: packaged Patch by Cillian de Róiste svn path=/nixpkgs/trunk/; revision=23984
2010-09-28 11:48:15 +02:00
uni2ascii = callPackage ../tools/text/uni2ascii { };
New package: g500-control g500-control is a small tool to configure internal profiles of a Logitech G500 mouse. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-03-27 19:51:32 +01:00
g500-control = callPackage ../tools/misc/g500-control { };
Galculator: add version 2.3.1 Galculator is a GTK full-fledged calculator.
2014-05-24 18:19:47 +02:00
galculator = callPackage ../applications/misc/galculator {
gtk = gtk3;
};
Make appendToName do the right thing I.e. append a suffix *before* the version, rather than after. So we get "sqlite-interactive-3.8.0.2" instead of "sqlite-3.8.0.2-interactive". The latter is broken since nix-env just sees it the suffix as part of the version, so "nix-env -u" will happily upgrade "sqlite-3.8.0.2-interactive" to "sqlite-3.9".
2014-03-10 15:01:56 +01:00
gawk = callPackage ../tools/text/gawk { };
gawk: signify interactivity in name I forgot to commit this.
2014-01-26 13:44:34 +01:00
gawkInteractive = appendToName "interactive"
(gawk.override { readlineSupport = true; });
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
gbdfed: add package 1.6
2014-07-13 13:22:10 +02:00
gbdfed = callPackage ../tools/misc/gbdfed {
gtk = gtk2;
};
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
gdmap = callPackage ../tools/system/gdmap { };
Added gdmap, changed builder-defs to use derivation attribute on propagatedBuildInputs, manually fixed Xorg expression problem for Compiz, various fixes. svn path=/nixpkgs/trunk/; revision=9812
2007-12-01 17:20:23 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
genext2fs = callPackage ../tools/filesystems/genext2fs { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gengetopt = callPackage ../development/tools/misc/gengetopt { };
Add GNU Gengetopt. svn path=/nixpkgs/trunk/; revision=19618
2010-01-22 18:00:44 +01:00
* getmail: don't use pythonFull. svn path=/nixpkgs/branches/modular-python/; revision=26566
2011-03-28 15:13:15 +02:00
getmail = callPackage ../tools/networking/getmail { };
Add getmail svn path=/nixpkgs/trunk/; revision=24334
2010-10-17 21:30:59 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
getopt = callPackage ../tools/misc/getopt { };
* Added JDiskReport 1.2.3 (with a wrapper script `jdiskreport' to start it). svn path=/nixpkgs/trunk/; revision=4031
2005-10-08 01:02:58 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
gftp = callPackage ../tools/networking/gftp { };
Added: * dmenu * gftp * micropolis * byacc as a build-time dependency for micropolis contributed by baldo <baldo@quimby.lan> svn path=/nixpkgs/trunk/; revision=12526
2008-08-06 22:39:01 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gifsicle = callPackage ../tools/graphics/gifsicle { };
added gifscile (creating and reading gif animations) svn path=/nixpkgs/trunk/; revision=12176
2008-06-22 04:07:53 +02:00
Update GlusterFS
2012-12-04 18:54:03 +01:00
glusterfs = callPackage ../tools/filesystems/glusterfs { };
Adding GlusterFS - a distributed storage system svn path=/nixpkgs/trunk/; revision=16896
2009-08-31 11:52:01 +02:00
glmark2: Add glmark2 2014.03
2014-07-12 10:04:28 +02:00
glmark2 = callPackage ../tools/graphics/glmark2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
glxinfo = callPackage ../tools/graphics/glxinfo { };
* Added glxinfo/glxgears. svn path=/nixpkgs/trunk/; revision=8593
2007-04-18 16:21:24 +02:00
gmvault: New package Gmvault Gmail Backup - Backup and restore your gmail account at will.
2013-05-31 14:08:34 +02:00
gmvault = callPackage ../tools/networking/gmvault { };
Adding gnokii svn path=/nixpkgs/trunk/; revision=15916
2009-06-10 11:45:03 +02:00
gnokii = builderDefsPackage (import ../tools/misc/gnokii) {
gnokii-0.6.30, add ical and gtk support svn path=/nixpkgs/trunk/; revision=26334
2011-03-16 00:09:14 +01:00
inherit intltool perl gettext libusb pkgconfig bluez readline pcsclite
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
libical gtk glib;
gnokii-0.6.30, add ical and gtk support svn path=/nixpkgs/trunk/; revision=26334
2011-03-16 00:09:14 +01:00
inherit (xorg) libXpm;
Adding gnokii svn path=/nixpkgs/trunk/; revision=15916
2009-06-10 11:45:03 +02:00
};
gnufdisk: update the alpha-version, no hydra now It builds now.
2013-01-31 21:10:37 +01:00
gnufdisk = callPackage ../tools/system/fdisk {
guile = guile_1_8;
};
some libintl and libiconv cleanups + non-linux fixes
2013-04-14 13:27:58 +02:00
gnugrep = callPackage ../tools/text/gnugrep {
libiconv = libiconvOrNull;
};
* Converted more packages. * Moved fetchurl, aterm. svn path=/nixpkgs/trunk/; revision=460
2003-11-02 19:14:24 +01:00
gnulib: add version 0.0-7898-gdb9cad7
2013-03-24 23:32:14 +01:00
gnulib = callPackage ../development/tools/gnulib { };
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
gnupatch = callPackage ../tools/text/gnupatch { };
* User-Mode Linux and GNU Patch. svn path=/nixpkgs/trunk/; revision=779
2004-02-13 15:42:28 +01:00
gnupg1: support for IDEA is now included by default (the patent has expired)
2013-10-10 11:38:23 +02:00
gnupg1orig = callPackage ../tools/security/gnupg1 { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gnupg1compat = callPackage ../tools/security/gnupg1compat { };
Add gnupg1 compatibility wrapper Gnupg1compat is symlinked gnupg2 with two additional symlinks: gpg->gpg2 and gpgv->gpgv2. Move original gnupg 1.x to gnupg1orig. Set default gnupg1 to gnupg1compat. svn path=/nixpkgs/trunk/; revision=21888
2010-05-19 22:59:20 +02:00
# use config.packageOverrides if you prefer original gnupg1
gnupg1 = gnupg1compat;
upgrade some packages to libusb1 on my systems, I can now override "libusb = libusb1" in all of nixpkgs so perhaps we can soon drop libusb 0.1 support?
2013-06-28 23:04:28 +02:00
gnupg = callPackage ../tools/security/gnupg { libusb = libusb1; };
gnupg2 added svn path=/nixpkgs/trunk/; revision=10346
2008-01-28 20:45:57 +01:00
* Don't use the prerelease of GnuPG by default. svn path=/nixpkgs/trunk/; revision=34054
2012-05-11 01:51:40 +02:00
gnupg2_1 = lowPrio (callPackage ../tools/security/gnupg/git.nix {
added extra package for gnupg 2.1 git pre version. contains the merge of gnupg-ecc, enabling ecdsa and other algorithms. I mainly need this because I use ecdsa for my ssh keys, and want gpg-agent to be able to handle them. svn path=/nixpkgs/trunk/; revision=33682
2012-04-09 12:17:40 +02:00
libassuan = libassuan2_1;
* Don't use the prerelease of GnuPG by default. svn path=/nixpkgs/trunk/; revision=34054
2012-05-11 01:51:40 +02:00
});
added extra package for gnupg 2.1 git pre version. contains the merge of gnupg-ecc, enabling ecdsa and other algorithms. I mainly need this because I use ecdsa for my ssh keys, and want gpg-agent to be able to handle them. svn path=/nixpkgs/trunk/; revision=33682
2012-04-09 12:17:40 +02:00
gnuplot: Use default compiler on Darwin
2014-08-09 19:52:33 +02:00
gnuplot = callPackage ../tools/graphics/gnuplot { };
gnuplot: fix build on darwin * add readline to build inputs * don't use wxGTK
2013-07-04 00:51:25 +02:00
gnuplot: Reduce dependency bloat a bit
2014-08-09 19:30:28 +02:00
gnuplot_qt = gnuplot.override { withQt = true; };
Added gnuplotX - gnuplot with X11 on. svn path=/nixpkgs/trunk/; revision=9047
2007-08-04 17:12:14 +02:00
gnuplot darwin: optional gnuplot_aquaterm variant This variant uses the more Mac-friendly aqua driver, but it requires that you separately install the AquaTerm package. Note that AquaTerm is open source and could perhaps be later included as a nix derivation. If that happens, it would be nice to remove the gnuplot_aquaterm top-level attribute and just make it the default.
2013-11-10 14:43:43 +01:00
# must have AquaTerm installed separately
gnuplot_aquaterm = gnuplot.override { aquaterm = true; };
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
gnused = callPackage ../tools/text/gnused { };
* Converting packages. This is the minimal Nix stdenv for building the ATerm library. svn path=/nixpkgs/trunk/; revision=459
2003-11-02 18:42:19 +01:00
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
gnutar = callPackage ../tools/archivers/gnutar { };
* Converted more packages. * Moved fetchurl, aterm. svn path=/nixpkgs/trunk/; revision=460
2003-11-02 19:14:24 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gnuvd = callPackage ../tools/misc/gnuvd { };
* added gnuvd, dutch dictionary application svn path=/nixpkgs/trunk/; revision=17177
2009-09-16 10:36:05 +02:00
Added goaccess package
2014-05-27 12:50:30 +02:00
goaccess = callPackage ../tools/misc/goaccess { };
PPSSPP: 0.9.8
2014-05-27 05:22:24 +02:00
Adding 'google-authenticator'
2013-03-30 20:45:38 +01:00
googleAuthenticator = callPackage ../os-specific/linux/google-authenticator { };
gource: added meta information and moved the package into version-management category svn path=/nixpkgs/trunk/; revision=31570
2012-01-15 12:44:02 +01:00
gource = callPackage ../applications/version-management/gource {};
added ftgl, gource svn path=/nixpkgs/trunk/; revision=24379
2010-10-20 12:53:45 +02:00
added gpodder package
2014-07-20 21:12:05 +02:00
gpodder = callPackage ../applications/audio/gpodder { };
Adding gptfdisk (patch by Shea Levy). I add him in the maintainers list. I changed slightly the indentation of the expressions. svn path=/nixpkgs/trunk/; revision=26304
2011-03-14 22:13:35 +01:00
gptfdisk = callPackage ../tools/system/gptfdisk { };
Add grafana, A Graphite & InfluxDB Dashboard and Graph Editor
2014-05-26 16:47:06 +02:00
grafana = callPackage ../development/tools/misc/grafana { };
grafx2: new package GrafX2 is a bitmap paint program inspired by the Amiga programs Deluxe Paint and Brilliance. Specialized in 256-color drawing.
2013-11-21 11:19:56 +01:00
grafx2 = callPackage ../applications/graphics/grafx2 {};
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
graphviz = callPackage ../tools/graphics/graphviz { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
pkgs/top-level/all-packages.nix: stripped trailing whitespace svn path=/nixpkgs/trunk/; revision=22734
2010-07-26 15:41:09 +02:00
/* Readded by Michael Raskin. There are programs in the wild
Readding old Graphviz: I need it for some graph program that relies on its way of grid snapping. svn path=/nixpkgs/trunk/; revision=22483
2010-07-05 21:04:33 +02:00
* that do want 2.0 but not 2.22. Please give a day's notice for
Update guitone
2014-08-31 22:37:57 +02:00
* objections before removal. The feature is integer coordinates
Readding old Graphviz: I need it for some graph program that relies on its way of grid snapping. svn path=/nixpkgs/trunk/; revision=22483
2010-07-05 21:04:33 +02:00
*/
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
graphviz_2_0 = callPackage ../tools/graphics/graphviz/2.0.nix { };
Update guitone
2014-08-31 22:37:57 +02:00
/* Readded by Michael Raskin. There are programs in the wild
* that do want 2.32 but not 2.0 or 2.36. Please give a day's notice for
* objections before removal. The feature is libgraph.
*/
graphviz_2_32 = callPackage ../tools/graphics/graphviz/2.32.nix { };
Readding old Graphviz: I need it for some graph program that relies on its way of grid snapping. svn path=/nixpkgs/trunk/; revision=22483
2010-07-05 21:04:33 +02:00
json-c: update to 0.12, fixing CVE-2013-{6370,6371}
2014-05-03 17:17:34 +02:00
grive = callPackage ../tools/filesystems/grive {
json_c = json-c-0-11; # won't configure with 0.12; others are vulnerable
};
grive: new package
2012-06-29 17:27:59 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
groff = callPackage ../tools/text/groff {
* groff: don't build with ghostscript as a dependency by default. svn path=/nixpkgs/branches/stdenv-updates/; revision=14064
2009-02-12 23:33:17 +01:00
ghostscript = null;
add groff, needed for dhcp svn path=/nixpkgs/trunk/; revision=3651
2005-08-21 15:59:04 +02:00
};
* Fix the GRUB 1 build on x86_64-linux. It didn't build because gcc43_multi is broken in the stdenv branch. However, for GRUB 1 we can just use the 32-bit build of GRUB (using callPackage_i686). svn path=/nixpkgs/branches/stdenv-updates/; revision=25003
2010-12-06 15:25:58 +01:00
grub = callPackage_i686 ../tools/misc/grub {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
buggyBiosCDSupport = config.grub.buggyBiosCDSupport or true;
* gcc-wrapper: use the right dynamic linker when -m32 is used. * An attribute `stdenv_32bit' that returns a stdenv capable of building 32-bit binaries. * grub: build on x86_64-linux. svn path=/nixpkgs/trunk/; revision=12211
2008-06-29 18:13:02 +02:00
};
* Added GNU enscript. svn path=/nixpkgs/trunk/; revision=1040
2004-06-03 19:16:16 +02:00
Revert "Revert "Merge pull request #2449 from wkennington/master.grub"" This reverts commit 94205f5f21c4d9942bb4205c06229438051b6853. Conflicts: nixos/modules/system/boot/loader/grub/install-grub.pl
2014-08-31 18:18:13 +02:00
grub2 = callPackage ../tools/misc/grub/2.0x.nix { };
Adding a missing newline in all-packages.nix svn path=/nixpkgs/trunk/; revision=26632
2011-03-31 23:15:53 +02:00
Revert "Revert "Merge pull request #2449 from wkennington/master.grub"" This reverts commit 94205f5f21c4d9942bb4205c06229438051b6853. Conflicts: nixos/modules/system/boot/loader/grub/install-grub.pl
2014-08-31 18:18:13 +02:00
grub2_efi = grub2.override { efiSupport = true; };
grub2_zfs = grub2.override { zfsSupport = true; };
Add GNU GRUB 1.97~beta3 (aka. "GRUB 2"). svn path=/nixpkgs/trunk/; revision=17636
2009-10-04 23:39:34 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gssdp = callPackage ../development/libraries/gssdp {
* gcc-wrapper: use the right dynamic linker when -m32 is used. * An attribute `stdenv_32bit' that returns a stdenv capable of building 32-bit binaries. * grub: build on x86_64-linux. svn path=/nixpkgs/trunk/; revision=12211
2008-06-29 18:13:02 +02:00
inherit (gnome) libsoup;
};
add gssdp and gupnp here too svn path=/nixpkgs/trunk/; revision=12152
2008-06-18 21:40:56 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gt5 = callPackage ../tools/system/gt5 { };
Adding 'gt5', a diff-capable 'du' browser svn path=/nixpkgs/trunk/; revision=20236
2010-02-24 20:06:25 +01:00
gtest: New package, the google c++ testing framework. BSD licensed testing framework from google: https://code.google.com/p/googletest/
2013-11-11 16:51:23 +01:00
gtest = callPackage ../development/libraries/gtest {};
Added gmock (Google Mock) package to complement gtest package.
2014-08-08 19:16:03 +02:00
gmock = callPackage ../development/libraries/gmock {};
gtest: New package, the google c++ testing framework. BSD licensed testing framework from google: https://code.google.com/p/googletest/
2013-11-11 16:51:23 +01:00
gtkdatabox: add version 0.9.1.3 Patch submitted by Jan Malakhovski <oxij@oxij.org>.
2012-07-02 16:35:47 +02:00
gtkdatabox = callPackage ../development/libraries/gtkdatabox {};
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
gtkgnutella = callPackage ../tools/networking/p2p/gtk-gnutella { };
Build xpf with python enabled libxml2 svn path=/nixpkgs/trunk/; revision=3229
2005-06-20 22:35:07 +02:00
Adding GTK-VNC svn path=/nixpkgs/trunk/; revision=25547
2011-01-13 23:21:09 +01:00
gtkvnc = callPackage ../tools/admin/gtk-vnc {};
Build xpf with python enabled libxml2 svn path=/nixpkgs/trunk/; revision=3229
2005-06-20 22:35:07 +02:00
Adding gtmess svn path=/nixpkgs/trunk/; revision=30221
2011-11-04 11:28:18 +01:00
gtmess = callPackage ../applications/networking/instant-messengers/gtmess { };
all-packages: remove gcc47 dependencies now gcc48 is default I checked these and they built fine
2013-12-07 20:10:55 +01:00
gummiboot = callPackage ../tools/misc/gummiboot { };
Add gummiboot UEFI boot manager
2013-02-01 23:42:19 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gupnp = callPackage ../development/libraries/gupnp {
* gcc-wrapper: use the right dynamic linker when -m32 is used. * An attribute `stdenv_32bit' that returns a stdenv capable of building 32-bit binaries. * grub: build on x86_64-linux. svn path=/nixpkgs/trunk/; revision=12211
2008-06-29 18:13:02 +02:00
inherit (gnome) libsoup;
};
add gssdp and gupnp here too svn path=/nixpkgs/trunk/; revision=12152
2008-06-18 21:40:56 +02:00
gupnp-tools and releated packages: fix and update
2014-01-11 13:28:12 +01:00
gupnp_av = callPackage ../development/libraries/gupnp-av {};
gupnp-igd svn path=/nixpkgs/trunk/; revision=33039
2012-03-13 20:06:17 +01:00
gupnp_igd = callPackage ../development/libraries/gupnp-igd {};
Add version numbers to name and remove comment
2014-01-11 21:26:05 +01:00
gupnptools = callPackage ../tools/networking/gupnp-tools {};
add gupnp-tools. I can't actually run them, since there seems to be some issue with fontconfig that has not been configured correctly and i don't know why svn path=/nixpkgs/trunk/; revision=12154
2008-06-19 00:34:49 +02:00
Adding GVPE - a protected virtual multinode ethernet svn path=/nixpkgs/trunk/; revision=16913
2009-09-01 22:12:01 +02:00
gvpe = builderDefsPackage ../tools/networking/gvpe {
Fix /sbin/ reference. On Linux just replace it with an "ip link" reference svn path=/nixpkgs/trunk/; revision=16918
2009-09-02 00:42:05 +02:00
inherit openssl gmp nettools iproute;
Adding GVPE - a protected virtual multinode ethernet svn path=/nixpkgs/trunk/; revision=16913
2009-09-01 22:12:01 +02:00
};
new expression: gvolicon
2014-03-13 16:24:15 +01:00
gvolicon = callPackage ../tools/audio/gvolicon {};
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
gzip = callPackage ../tools/compression/gzip { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Add gzrt, gzip Recovery Toolkit
2013-10-17 18:35:24 +02:00
gzrt = callPackage ../tools/compression/gzrt { };
partclone, partimage. both are used by clonezilla and drbl (which I haven't packaged yet)
2013-05-16 11:41:58 +02:00
partclone = callPackage ../tools/backup/partclone { };
partimage = callPackage ../tools/backup/partimage { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pigz = callPackage ../tools/compression/pigz { };
pigz: an implementation of gzip that can take advantage of multi-core CPUs Initial version. svn path=/nixpkgs/trunk/; revision=17707
2009-10-07 22:18:11 +02:00
add haproxy svn path=/nixpkgs/trunk/; revision=34165
2012-05-18 09:50:10 +02:00
haproxy = callPackage ../tools/networking/haproxy { };
add haveged: A simple entropy daemon
2013-10-06 17:18:44 +02:00
haveged = callPackage ../tools/security/haveged { };
add haproxy svn path=/nixpkgs/trunk/; revision=34165
2012-05-18 09:50:10 +02:00
hawkthorne: Initial commit, license issue still unresolved
2014-08-31 08:41:46 +02:00
hawkthorne = callPackage ../games/hawkthorne { love = love_0_9; };
hardlink: initial version Hardlink consolidates duplicate files in a directory hierarchy with hardlinks, similar to "nix-store --optimise". IHMO, this program should be run by the default builder after $out has been set up, to remove redundancy in the generated closures. svn path=/nixpkgs/trunk/; revision=31934
2012-01-30 12:40:20 +01:00
hardlink = callPackage ../tools/system/hardlink { };
hashcat: version 0.47 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-31 17:56:02 +02:00
hashcat = callPackage ../tools/security/hashcat { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
halibut = callPackage ../tools/typesetting/halibut { };
Adding the halibut typesetting system. svn path=/nixpkgs/trunk/; revision=14759
2009-03-29 22:32:22 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hddtemp = callPackage ../tools/misc/hddtemp { };
hddtemp (tool to get harddisk temperatures) added and unfinished qgis expression (in case someone else want's to continue working on it) svn path=/nixpkgs/trunk/; revision=9903
2007-12-10 23:36:52 +01:00
disable szip for hdf5 because of its unfree nature
2014-06-23 23:13:50 +02:00
hdf5 = callPackage ../tools/misc/hdf5 {
szip = null;
hdf5: Offer openmpi version of the package
2014-07-01 15:55:29 +02:00
mpi = null;
};
hdf5-mpi = hdf5.override {
szip = null;
mpi = pkgs.openmpi;
disable szip for hdf5 because of its unfree nature
2014-06-23 23:13:50 +02:00
};
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
svn path=/nixpkgs/trunk/; revision=28716
2011-08-21 02:10:12 +02:00
heimdall = callPackage ../tools/misc/heimdall { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hevea = callPackage ../tools/typesetting/hevea { };
Added the first release of xpf, Xml Pipes and Filters. svn path=/nixpkgs/trunk/; revision=1308
2004-08-21 00:06:36 +02:00
highlight: Update to 3.5 svn path=/nixpkgs/trunk/; revision=29064
2011-09-06 19:10:08 +02:00
highlight = callPackage ../tools/text/highlight {
lua = lua5;
};
Added ViewMTN and dependency; currently ViewMTN has to be manually symlinked in corresponding directory. svn path=/nixpkgs/trunk/; revision=12060
2008-06-12 17:59:59 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
host = callPackage ../tools/networking/host { };
Add `host', a DNS query utility. svn path=/nixpkgs/trunk/; revision=13459
2008-11-27 14:54:49 +01:00
hping: New package, version 20051105. Quite a lot of patching involved here, but the upstream package is no longer maintained anymore. Nevertheless the tool is still useful in some environments. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-12 06:27:01 +01:00
hping = callPackage ../tools/networking/hping { };
Added httpie HTTPie is a command line HTTP client. Its goal is to make CLI interaction with web services as human-friendly as possible.
2012-12-28 23:28:34 +01:00
httpie = callPackage ../tools/networking/httpie { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
httpfs2 = callPackage ../tools/filesystems/httpfs { };
Add HTTPFS2, for Linux. svn path=/nixpkgs/trunk/; revision=22308
2010-06-17 14:44:40 +02:00
Hydra: Comment out for now. svn path=/nixpkgs/trunk/; revision=30659
2011-12-01 23:43:10 +01:00
# FIXME: This Hydra snapshot is outdated and depends on the `nixPerl',
# which no longer exists.
#
# hydra = callPackage ../development/tools/misc/hydra {
# nix = nixUnstable;
# };
add hydra svn path=/nixpkgs/trunk/; revision=25567
2011-01-14 15:47:48 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iasl = callPackage ../development/compilers/iasl { };
Fixing commits I did, which didn't follow well the writing rules. svn path=/nixpkgs/trunk/; revision=13868
2009-01-25 22:03:07 +01:00
- icecast-2.3.3, libshout-2.3.1
2012-10-15 08:48:46 +02:00
icecast = callPackage ../servers/icecast { };
Adding icoutils svn path=/nixpkgs/trunk/; revision=31265
2012-01-04 10:42:38 +01:00
icoutils = callPackage ../tools/graphics/icoutils { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
idutils = callPackage ../tools/misc/idutils { };
Add GNU Idutils, a text searching utility. svn path=/nixpkgs/trunk/; revision=11300
2008-03-27 12:09:40 +01:00
Adding idle3-tools (for WD Green HDDs)
2013-03-07 21:40:28 +01:00
idle3tools = callPackage ../tools/system/idle3tools { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iftop = callPackage ../tools/networking/iftop { };
added eggdrop, iftop svn path=/nixpkgs/trunk/; revision=17710
2009-10-08 09:01:55 +02:00
Adding imapproxy svn path=/nixpkgs/trunk/; revision=30360
2011-11-09 19:25:55 +01:00
imapproxy = callPackage ../tools/networking/imapproxy { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
imapsync = callPackage ../tools/networking/imapsync {
Adding imapsync, with the two needed perl packages. svn path=/nixpkgs/trunk/; revision=15967
2009-06-15 20:37:42 +02:00
inherit (perlPackages) MailIMAPClient;
Add GNU Idutils, a text searching utility. svn path=/nixpkgs/trunk/; revision=11300
2008-03-27 12:09:40 +01:00
};
Adding inadyn, a dynamic dns client. svn path=/nixpkgs/trunk/; revision=26743
2011-04-07 22:26:26 +02:00
inadyn = callPackage ../tools/networking/inadyn { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
inetutils = callPackage ../tools/networking/inetutils { };
Add GNU Inetutils. svn path=/nixpkgs/trunk/; revision=10817
2008-02-21 19:58:11 +01:00
Adding IOping svn path=/nixpkgs/trunk/; revision=27367
2011-06-07 17:56:50 +02:00
ioping = callPackage ../tools/system/ioping {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iodine = callPackage ../tools/networking/iodine { };
Add iodine-0.4.1 svn path=/nixpkgs/trunk/; revision=11824
2008-05-14 10:01:03 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iperf = callPackage ../tools/networking/iperf { };
added iperf (a tool to measure network bandwidth) svn path=/nixpkgs/trunk/; revision=14564
2009-03-16 19:39:04 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
ipmitool = callPackage ../tools/system/ipmitool {
pkgs/top-level/all-packages.nix: prefer makeOverridable over getPkgConfig to customize ipmitool Changed 'ipmitool' expression to allow for argument overriding instead of relying on getPkgConfig. svn path=/nixpkgs/trunk/; revision=21863
2010-05-19 14:25:48 +02:00
static = false;
pkgs/tools/system/ipmitool: command-line interface to IPMI-enabled devices Initial version 1.8.9. svn path=/nixpkgs/trunk/; revision=19542
2010-01-19 16:58:19 +01:00
};
Fixing a stupid typo svn path=/nixpkgs/trunk/; revision=25663
2011-01-21 20:34:54 +01:00
ipmiutil = callPackage ../tools/system/ipmiutil {};
Adding ipmiutil svn path=/nixpkgs/trunk/; revision=25660
2011-01-21 20:15:10 +01:00
Adding ised svn path=/nixpkgs/trunk/; revision=25331
2011-01-01 21:28:38 +01:00
ised = callPackage ../tools/misc/ised {};
Add isl, the integer set library (needed for cloog, an optional dependency for GCC 4.6.0) svn path=/nixpkgs/trunk/; revision=26633
2011-03-31 23:19:39 +02:00
isl = callPackage ../development/libraries/isl { };
Add full llvm build, update libc++ and dragonegg Some packages in the llvm suite (e.g. compiler-rt) cannot be built separate from the build of llvm, and while some others (e.g. clang) can the combined build is much better tested (we've had to work around annoying issues before). So this puts llvm, clang, clang-tools-extra, compiler-rt, lld, lldb, and polly all into one big build (llvmFull). This build includes a static llvm, as dynamic is similarly less tested and has known failures. This also updates libc++ and dragonegg. libc++ now builds against libc++abi as a separate package rather than building it during the libc++ build. The clang purity patch is gone. Instead, we simply set --sysroot to /var/empty for pure builds, as all impure paths are either looked up in the gcc prefix (which we hard-code at compile time) or in the sysroot. This also means that if NIX_ENFORCE_PURITY is 0 then clang will look in the normal Linux paths by default, which is the proper behavior IMO. polly required an updated isl. When stdenv-updates is merged, perhaps we can update the isl used by gcc and avoid having two versions. Since llvm on its own is now separate from the llvm used by clang, I've removed myself as maintainer from llvm and will leave maintenance of that to those who are interested in llvm separate from clang. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 11:23:17 +01:00
isl_0_12 = callPackage ../development/libraries/isl/0.12.2.nix { };
Add isl, the integer set library (needed for cloog, an optional dependency for GCC 4.6.0) svn path=/nixpkgs/trunk/; revision=26633
2011-03-31 23:19:39 +02:00
Adding isync svn path=/nixpkgs/trunk/; revision=25798
2011-02-08 00:07:21 +01:00
isync = callPackage ../tools/networking/isync { };
jd-gui: version 0.3.5 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-17 21:20:54 +02:00
jd-gui = callPackage_i686 ../tools/security/jd-gui { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jdiskreport = callPackage ../tools/misc/jdiskreport { };
- add a whole bunch of packages which were added today already (but also list them here) - enable OOo2 build svn path=/nixpkgs/trunk/; revision=4149
2005-10-26 23:10:31 +02:00
jfsrec: build with boost 1.44.0 Compilation with the latest version, boost 1.47.0, fails as follows: g++ -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -c -o inode.o inode.cpp inode.cpp: In member function 'virtual boost::filesystem3::path jfsrec::Inode::get_full_path()': inode.cpp:70:54: error: invalid conversion from 'bool (*)(const std::string&)' to 'boost::enable_if_c<true, void>::type*' inode.cpp:70:54: error: initializing argument 2 of 'boost::filesystem3::path::path(const Source&, typename boost::enable_if<boost::filesystem3::path_traits::is_pathable<typename boost::decay<Source>::type> >::type*) [with Source = std::basic_string<char>, typename boost::enable_if<boost::filesystem3::path_traits::is_pathable<typename boost::decay<Source>::type> >::type = void]' inode.cpp:72:54: error: invalid conversion from 'bool (*)(const std::string&)' to 'boost::enable_if_c<true, void>::type*' inode.cpp:72:54: error: initializing argument 2 of 'boost::filesystem3::path::path(const Source&, typename boost::enable_if<boost::filesystem3::path_traits::is_pathable<typename boost::decay<Source>::type> >::type*) [with Source = std::basic_string<char>, typename boost::enable_if<boost::filesystem3::path_traits::is_pathable<typename boost::decay<Source>::type> >::type = void]' make[2]: *** [inode.o] Error 1 It appears that jfsrec assumes that fs::path is a string, which isn't true anymore in Boost.FS v3. svn path=/nixpkgs/trunk/; revision=27750
2011-07-13 12:56:52 +02:00
jfsrec = callPackage ../tools/filesystems/jfsrec {
boost = boost144;
};
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jfsutils = callPackage ../tools/filesystems/jfsutils { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jhead = callPackage ../tools/graphics/jhead { };
Adding jhead svn path=/nixpkgs/trunk/; revision=17747
2009-10-11 17:52:14 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jing = callPackage ../tools/text/xml/jing { };
* Removed MythTV from cache * Make the jing library available svn path=/nixpkgs/trunk/; revision=4122
2005-10-24 16:01:08 +02:00
add jmtpfs - a FUSE filesystem for MTP
2014-05-11 21:35:28 +02:00
jmtpfs = callPackage ../tools/filesystems/jmtpfs { };
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
jnettop = callPackage ../tools/networking/jnettop { };
Add Jnettop, a network traffic visualizer. svn path=/nixpkgs/trunk/; revision=13564
2008-12-03 15:22:55 +01:00
Add JohnTheRipper, a fast password cracker
2014-09-04 01:30:04 +02:00
john = callPackage ../tools/security/john { };
Adding jq JSON processor
2013-05-20 09:17:20 +02:00
jq = callPackage ../development/tools/jq {};
jscoverage-0.5.1 svn path=/nixpkgs/trunk/; revision=27508
2011-06-21 09:28:30 +02:00
jscoverage = callPackage ../development/tools/misc/jscoverage { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jwhois = callPackage ../tools/networking/jwhois { };
all-packages.nix: strip trailing whitespace
2014-02-28 11:02:46 +01:00
add kazam
2014-02-27 16:37:29 +01:00
kazam = callPackage ../applications/video/kazam { };
* Added jwhois, the GNU whois client. svn path=/nixpkgs/trunk/; revision=9211
2007-08-28 16:45:00 +02:00
kalibrate-rtl: new package kalibrate-rtl calculates the local oscillator frequency offset in RTL-SDR devices. kalibrate-rtl has no tags/releases, so I'm using the latest commit from git master (dated 2013-12-14). I made an upstream issue about making a release back in May[1], but I've gotten no response yet. [1] https://github.com/steve-m/kalibrate-rtl/issues/7
2014-05-12 19:47:54 +02:00
kalibrate-rtl = callPackage ../tools/misc/kalibrate-rtl { };
Adding kexectools. svn path=/nixpkgs/trunk/; revision=33175
2012-03-16 22:17:13 +01:00
kexectools = callPackage ../os-specific/linux/kexectools { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
keychain = callPackage ../tools/misc/keychain { };
added keychain, a gentoo tool to start gnupg and ssh daemon writing pids to a file so that you can share them easily on different shells svn path=/nixpkgs/trunk/; revision=11693
2008-04-23 12:51:23 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
kismet = callPackage ../applications/networking/sniffers/kismet { };
Adding kismet. svn path=/nixpkgs/trunk/; revision=13938
2009-02-01 22:21:27 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
less = callPackage ../tools/misc/less { };
* Trang (tool for converting to and from RelaxNG schemas). svn path=/nixpkgs/trunk/; revision=5579
2006-07-04 21:17:34 +02:00
add lockfile-progs-0.1.16
2012-08-25 11:13:59 +02:00
lockfileProgs = callPackage ../tools/misc/lockfile-progs { };
Add logstash For now just download the pre-built jar. We may build our own later.
2012-07-11 13:23:14 +02:00
logstash = callPackage ../tools/misc/logstash { };
Add logstash-forwarder.
2014-04-10 13:31:23 +02:00
logstash-forwarder = callPackage ../tools/misc/logstash-forwarder { };
Adds kippo SSH honeypot
2014-01-11 23:15:11 +01:00
kippo = callPackage ../servers/kippo { };
klavaro: add version 1.9.5 Patch submitted by Jan Malakhovski <oxij@oxij.org>.
2012-07-02 16:37:17 +02:00
klavaro = callPackage ../games/klavaro {};
all-packages.nix: strip trailing whitespace
2014-08-20 11:57:56 +02:00
kzipmix: create package
2014-08-14 16:10:30 +02:00
kzipmix = callPackage_i686 ../tools/compression/kzipmix { };
klavaro: add version 1.9.5 Patch submitted by Jan Malakhovski <oxij@oxij.org>.
2012-07-02 16:37:17 +02:00
minidlna: pin to ffmpeg 0.10
2013-12-16 14:35:02 +01:00
minidlna = callPackage ../tools/networking/minidlna {
ffmpeg = ffmpeg_0_10;
};
* Add MiniDLNA 1.0.24, media server
2012-06-24 20:24:58 +02:00
mmv: New package, version 1.01b from Debian. This package as well as the patches are used from Debian, as the upstream version is no longer maintained, plus other distributions seem to use the Debian patched version aswell. And by looking at the patch from Debian, it seems reasonable, because it contains a _lot_ of fixes that accrued over time. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-09-05 01:44:21 +02:00
mmv = callPackage ../tools/misc/mmv { };
* Add MiniDLNA 1.0.24, media server
2012-06-24 20:24:58 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
most = callPackage ../tools/misc/most { };
pkgs/tools/misc/most: added version 5.0.0 Build instructions courtesy of Tim Horton <tmhorton@gmail.com>. svn path=/nixpkgs/trunk/; revision=21452
2010-04-30 11:21:18 +02:00
Add multitail
2013-03-31 19:40:11 +02:00
multitail = callPackage ../tools/misc/multitail { };
Add netperf I will add meta later, I promise, I just need to use this now svn path=/nixpkgs/trunk/; revision=30026
2011-10-25 22:49:22 +02:00
netperf = callPackage ../applications/networking/netperf { };
Added ninka, an experimental sentence based license detector svn path=/nixpkgs/trunk/; revision=27455
2011-06-14 17:15:34 +02:00
ninka = callPackage ../development/tools/misc/ninka { };
all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=27648
2011-07-07 23:32:55 +02:00
Adding node.js, a javascript web development platform svn path=/nixpkgs/trunk/; revision=27168
2011-05-06 00:38:04 +02:00
nodejs = callPackage ../development/web/nodejs {};
Revert "Hide nodePackages from nix-env" Now node packages that aren't just programs have a node- prefix in their names. This reverts commit 2f11bc495b50c36c1984f334df6867c1b9200a91. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-02-03 23:28:12 +01:00
nodePackages = recurseIntoAttrs (import ./node-packages.nix {
Update npm packages to latest npm2nix Signed-off-by: Shea Levy <shea@shealevy.com>
2013-11-14 19:36:08 +01:00
inherit pkgs stdenv nodejs fetchurl fetchgit;
node-packages: ability to build npms that have native extensions
2012-09-13 14:35:35 +02:00
neededNatives = [python] ++ lib.optional (lib.elem system lib.platforms.linux) utillinux;
Make overrides of nodePackages work Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-31 18:50:28 +02:00
self = pkgs.nodePackages;
Revert "Hide nodePackages from nix-env" Now node packages that aren't just programs have a node- prefix in their names. This reverts commit 2f11bc495b50c36c1984f334df6867c1b9200a91. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-02-03 23:28:12 +01:00
});
Add nodePackages attr to all-packages
2012-07-25 23:51:33 +02:00
add ldapvi: interactive LDAP client for Unix terminals. Using it, you can update LDAP entries with a text editor.
2013-11-28 00:15:14 +01:00
ldapvi = callPackage ../tools/misc/ldapvi { };
Updating unbound. svn path=/nixpkgs/trunk/; revision=30174
2011-11-01 23:33:40 +01:00
ldns = callPackage ../development/libraries/ldns { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lftp = callPackage ../tools/networking/lftp { };
Added lftp ftp client. svn path=/nixpkgs/trunk/; revision=9042
2007-08-04 14:41:00 +02:00
Adding libconfig, a simple library for processing config files svn path=/nixpkgs/trunk/; revision=33633
2012-04-05 23:12:12 +02:00
libconfig = callPackage ../development/libraries/libconfig { };
Add rsyslog 7.2.6 and its dependencies
2013-03-14 14:07:56 +01:00
libee = callPackage ../development/libraries/libee { };
libestr = callPackage ../development/libraries/libestr { };
Add evemu tool to emulate and record input device event data [Bjørn Forsman: * wrap some long lines * tweak meta attrs (don't repeat package name, s/meta.maintainer/meta.maintainers/) * provide a version number (v2.0) for 'evemu' (for nix-env) ]
2014-07-22 17:37:13 +02:00
libevdev = callPackage ../development/libraries/libevdev { };
add gnome3.libgdata and liboauth
2014-01-20 16:38:39 +01:00
liboauth = callPackage ../development/libraries/liboauth { };
Add TI-RPC. svn path=/nixpkgs/trunk/; revision=30216
2011-11-03 22:08:32 +01:00
libtirpc = callPackage ../development/libraries/ti-rpc { };
libtirpc: added version 0.2.2 The glibc maintainers in their wisdom have dropped RPC support. That change causes plenty of builds to fail, like PAM. Users are supposed to use libtirpc instead, which, naturally, doesn't compile with glibc 2.14. I'm adding the library anyway, just so that we have it. svn path=/nixpkgs/branches/stdenv-updates/; revision=30029
2011-10-26 12:32:40 +02:00
- icecast-2.3.3, libshout-2.3.1
2012-10-15 08:48:46 +02:00
libshout = callPackage ../development/libraries/libshout { };
libqmi: 1.0 -> 1.8.0, move outside gnome3 namespace, fix build
2014-02-08 20:15:12 +01:00
libqmi = callPackage ../development/libraries/libqmi { };
ModemManager: 0.5.4.0 -> 0.7.991
2014-02-08 20:16:34 +01:00
libmbim = callPackage ../development/libraries/libmbim { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libtorrent = callPackage ../tools/networking/p2p/libtorrent { };
Added libtorrent a bittorent library written in C++ for *nix and rtorrent a ncurses client for libtorrent. svn path=/nixpkgs/trunk/; revision=10842
2008-02-23 13:11:27 +01:00
add logcheck 1.3.15 nixos-module follows soon
2012-08-25 11:14:40 +02:00
logcheck = callPackage ../tools/system/logcheck {
inherit (perlPackages) mimeConstruct;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
logrotate = callPackage ../tools/system/logrotate { };
Adding the logrotate I found in the freebsd ports. I think that is what debian, fedora and freebsd call 'logrotate'. svn path=/nixpkgs/trunk/; revision=21437
2010-04-29 19:55:06 +02:00
logstalgia: fix attribute and directory name typo Change "logstalgica" to "logstalgia".
2014-01-18 21:41:15 +01:00
logstalgia = callPackage ../tools/graphics/logstalgia {};
logstalgica: added version 1.0.3 svn path=/nixpkgs/trunk/; revision=31590
2012-01-16 12:34:00 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lout = callPackage ../tools/typesetting/lout { };
Add Lout, a document layout system based on a purely functional language. svn path=/nixpkgs/trunk/; revision=10634
2008-02-12 10:58:57 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lrzip = callPackage ../tools/compression/lrzip { };
Adding lrzip and rzip. svn path=/nixpkgs/trunk/; revision=14581
2009-03-17 22:17:51 +01:00
Fiddle with priorities to provide a smoother upgrade path. svn path=/nixpkgs/branches/stdenv-updates/; revision=24726
2010-11-17 11:43:04 +01:00
# lsh installs `bin/nettle-lfib-stream' and so does Nettle. Give the
# former a lower priority than Nettle.
lsh = lowPrio (callPackage ../tools/networking/lsh { });
Adding lzop and updating lzo. svn path=/nixpkgs/trunk/; revision=14749
2009-03-28 20:28:59 +01:00
lshw: Packaged svn path=/nixpkgs/trunk/; revision=24688
2010-11-15 10:52:57 +01:00
lshw = callPackage ../tools/system/lshw { };
Move lxc from "applications/virtualization" to "os-specific/linux".
2012-10-20 12:36:44 +02:00
lxc = callPackage ../os-specific/linux/lxc { };
Adding lxc userland tools. svn path=/nixpkgs/trunk/; revision=24502
2010-10-26 23:11:47 +02:00
all-packages.nix: remove redundant texinfo5 overrides Texinfo 5.x is the default version now.
2014-01-21 20:29:34 +01:00
lzip = callPackage ../tools/compression/lzip { };
lzip: add version 1.14-rc3
2013-02-06 13:15:12 +01:00
* Removed the lzma package - it's superseded by xz. svn path=/nixpkgs/branches/stdenv-updates/; revision=19027
2009-12-18 12:25:56 +01:00
lzma = xz;
xlock: fixed build and updated to version 5.24 svn path=/nixpkgs/trunk/; revision=17356
2009-09-22 22:16:38 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xz = callPackage ../tools/compression/xz { };
* Added lzma, a compression program that compresses better than bzip2. svn path=/nixpkgs/trunk/; revision=10513
2008-02-06 14:52:41 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lzop = callPackage ../tools/compression/lzop { };
Add GNU lsh, a GPL'd implementation of SSH, and `liboop', and event loop library. svn path=/nixpkgs/trunk/; revision=10637
2008-02-12 11:51:44 +01:00
maildrop: add version 2.6.0
2013-01-04 04:07:46 +01:00
maildrop = callPackage ../tools/networking/maildrop { };
Add mailpile: A modern, fast web-mail client with user-friendly encryption and privacy features
2014-01-21 14:08:22 +01:00
mailpile = callPackage ../applications/networking/mailreaders/mailpile { };
Prepare for the Guile 2.0 switchover. svn path=/nixpkgs/trunk/; revision=25976
2011-02-15 14:14:29 +01:00
mailutils = callPackage ../tools/networking/mailutils {
guile = guile_1_8;
};
Add GNU Mailutils 2.1. svn path=/nixpkgs/trunk/; revision=17041
2009-09-11 11:38:25 +02:00
Adding mairix svn path=/nixpkgs/trunk/; revision=28122
2011-08-02 16:26:47 +02:00
mairix = callPackage ../tools/text/mairix { };
Add GNU Mailutils 2.1. svn path=/nixpkgs/trunk/; revision=17041
2009-09-11 11:38:25 +02:00
makemkv-1.8.0
2013-02-24 04:35:19 +01:00
makemkv = callPackage ../applications/video/makemkv { };
Add GNU Mailutils 2.1. svn path=/nixpkgs/trunk/; revision=17041
2009-09-11 11:38:25 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
man = callPackage ../tools/misc/man { };
* A more pure man implementation. svn path=/nixpkgs/trunk/; revision=10547
2008-02-07 15:39:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
man_db = callPackage ../tools/misc/man-db { };
* Added cabextract. Might be useful for adding Visual C++. svn path=/nixpkgs/trunk/; revision=5368
2006-06-01 23:25:40 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
memtest86 = callPackage ../tools/misc/memtest86 { };
* Added Memtest86+. svn path=/nixpkgs/trunk/; revision=10059
2008-01-03 16:14:37 +01:00
Move memtest86+ to its own directory
2013-10-02 11:30:47 +02:00
memtest86plus = callPackage ../tools/misc/memtest86+ { };
Adding the memtest86 from memtest86.com, and renaming the top-level attribute name of memtest86+ to memtest86plus. I think it makes more sense for the attribute memtest86 to point to the upstream memtest86.com version. svn path=/nixpkgs/trunk/; revision=33689
2012-04-09 21:54:34 +02:00
Adding meo: Multiple Eyepairs Only I also add the pkcs11helper it needs.
2013-05-20 23:12:21 +02:00
meo = callPackage ../tools/security/meo { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mc = callPackage ../tools/misc/mc { };
Added midnight commander package svn path=/nixpkgs/trunk/; revision=10256
2008-01-23 10:57:11 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mcabber = callPackage ../applications/networking/instant-messengers/mcabber { };
Adding mcabber console jabber client - patch by Lluis Batlle svn path=/nixpkgs/trunk/; revision=13698
2009-01-04 18:11:38 +01:00
Prepare for the Guile 2.0 switchover. svn path=/nixpkgs/trunk/; revision=25976
2011-02-15 14:14:29 +01:00
mcron = callPackage ../tools/system/mcron {
guile = guile_1_8;
};
Add GNU mcron, a `cron' implementation in Guile Scheme. svn path=/nixpkgs/trunk/; revision=14870
2009-04-03 20:46:26 +02:00
Making the current versions of flex/bison the default. Evaluation test passes. Please explicitly pass older versions to any package that can be adversely affected by too-fresh versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=25086
2010-12-12 22:48:29 +01:00
mdbtools = callPackage ../tools/misc/mdbtools { };
Added MDBtools svn path=/nixpkgs/trunk/; revision=11811
2008-05-11 11:45:26 +02:00
all-packages.nix: strip trailing whitespace
2014-05-04 14:39:40 +02:00
mdbtools_git = callPackage ../tools/misc/mdbtools/git.nix {
Update MDBTools Git version
2014-04-12 17:27:26 +02:00
inherit (gnome) scrollkeeper;
};
Add Git version of mdbtools - UCS-2 capable svn path=/nixpkgs/trunk/; revision=24007
2010-09-30 18:50:37 +02:00
Mednafen: add version 0.9.34.1 + server 0.5.1 Mednafen is a portable, CLI-driven, multi-system emulator
2014-05-17 05:02:22 +02:00
mednafen = callPackage ../misc/emulators/mednafen { };
mednafen-server = callPackage ../misc/emulators/mednafen/server.nix { };
Add MegaCli, a command line tool to manage certain RAID cards.
2013-09-16 15:56:55 +02:00
megacli = callPackage ../tools/misc/megacli { };
Adding megatools
2013-05-24 23:43:26 +02:00
megatools = callPackage ../tools/networking/megatools { };
Add mfcuk, tool for hacking mifare classic cards
2014-08-26 01:22:08 +02:00
mfcuk = callPackage ../tools/security/mfcuk { };
Add minecraft Patch by Carles Pagès, minor modification (adding in version number, updating sha256) by me svn path=/nixpkgs/trunk/; revision=33944
2012-04-29 16:09:58 +02:00
minecraft = callPackage ../games/minecraft { };
minecraft-server: version 1.7.5 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-29 10:48:08 +01:00
minecraft-server = callPackage ../games/minecraft-server { };
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
minetest = callPackage ../games/minetest {
libpng = libpng12;
};
Added Minetest-0.4.4.
2013-01-04 11:39:11 +01:00
Update bitcoin to 0.3.21 svn path=/nixpkgs/trunk/; revision=27275
2011-05-17 13:34:18 +02:00
miniupnpc = callPackage ../tools/networking/miniupnpc { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
miniupnpd = callPackage ../tools/networking/miniupnpd { };
* Added miniupnpd, an implementation of the UPnP Internet Gateway Device (IGD) specification. * Updated iptables to 1.4.8. svn path=/nixpkgs/trunk/; revision=21929
2010-05-21 00:11:44 +02:00
Adding ZynAddSubFX, a software synthesizer, and minixml (a dependency of ZynAddSubFX) svn path=/nixpkgs/trunk/; revision=26746
2011-04-08 00:24:56 +02:00
minixml = callPackage ../development/libraries/minixml { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mjpegtools = callPackage ../tools/video/mjpegtools { };
* Converted Mozilla Firebird. svn path=/nixpkgs/trunk/; revision=491
2003-11-07 12:18:47 +01:00
Add mkcue (an optional dep of abcde) svn path=/nixpkgs/trunk/; revision=26175
2011-03-06 17:07:31 +01:00
mkcue = callPackage ../tools/cd-dvd/mkcue { };
Add GNU mkisofs. svn path=/nixpkgs/trunk/; revision=19603
2010-01-21 17:53:16 +01:00
Add mkpasswd, an overfeatured front end to crypt
2013-02-27 12:14:09 +01:00
mkpasswd = callPackage ../tools/security/mkpasswd { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mktemp = callPackage ../tools/security/mktemp { };
* Mac needs Unzip 5.52. svn path=/nixpkgs/trunk/; revision=2434
2005-03-21 15:48:48 +01:00
Adding mktorrent 1.0
2013-03-12 19:43:57 +01:00
mktorrent = callPackage ../tools/misc/mktorrent { };
Add modemmanager svn path=/nixpkgs/trunk/; revision=31263
2012-01-04 10:05:22 +01:00
modemmanager = callPackage ../tools/networking/modemmanager {};
Monit: Bump to 5.8 - Use callPackage etc - Make PAM optional
2014-05-04 09:51:10 +02:00
monit = callPackage ../tools/system/monit { };
Adding monit monitoring tool; in the course of action creating a script to auto-prepare basic autoupdate layout svn path=/nixpkgs/trunk/; revision=16863
2009-08-26 18:22:20 +02:00
Adding mosh. svn path=/nixpkgs/trunk/; revision=33804
2012-04-16 23:44:12 +02:00
mosh = callPackage ../tools/networking/mosh {
Made mosh use boostHeaders, and not boost. A much lighter dependency, of great help on the Sheevaplug. I'm not sure of the name 'boostHeaders' and 'boostHeaders149'. Changes welcome. svn path=/nixpkgs/trunk/; revision=33806
2012-04-17 00:16:38 +02:00
boost = boostHeaders;
Adding mosh. svn path=/nixpkgs/trunk/; revision=33804
2012-04-16 23:44:12 +02:00
inherit (perlPackages) IOTty;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mpage = callPackage ../tools/text/mpage { };
Add Mpage, a tool to print multiple pages per sheet on a PostScript printer. svn path=/nixpkgs/trunk/; revision=11572
2008-04-11 15:22:35 +02:00
Added mr - Multiple Repository management tool
2012-07-07 17:12:18 +02:00
mr = callPackage ../applications/version-management/mr { };
mscgen: added version 0.20 svn path=/nixpkgs/trunk/; revision=29803
2011-10-13 09:38:44 +02:00
mscgen = callPackage ../tools/graphics/mscgen { };
* Removed selectVersion. There's no good reason to write `selectVersion ./foo "bar"' instead of `import ./foo/bar.nix'. * Replaced `with args' with formal function arguments in several packages. * Renamed several files to `default.nix'. As a general rule, version numbers should only be included in the filename when there is a reason to keep multiple versions of a package in Nixpkgs. Otherwise, it just makes it harder to update the package. svn path=/nixpkgs/trunk/; revision=18403
2009-11-18 10:39:59 +01:00
msf = builderDefsPackage (import ../tools/security/metasploit/3.1.nix) {
all-packages.nix changes for all the previous commits svn path=/nixpkgs/trunk/; revision=11564
2008-04-11 11:32:27 +02:00
inherit ruby makeWrapper;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mssys = callPackage ../tools/misc/mssys { };
* Added ms-sys, a program for writing Microsoft compatible boot records. svn path=/nixpkgs/trunk/; revision=10414
2008-01-30 18:08:38 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mtdutils = callPackage ../tools/filesystems/mtdutils { };
Adding mtdutils svn path=/nixpkgs/trunk/; revision=21436
2010-04-29 19:54:51 +02:00
* Added mtools. svn path=/nixpkgs/trunk/; revision=23014
2010-08-06 23:36:54 +02:00
mtools = callPackage ../tools/filesystems/mtools { };
Adding mtr. svn path=/nixpkgs/trunk/; revision=25495
2011-01-10 16:57:23 +01:00
mtr = callPackage ../tools/networking/mtr {};
* Add callPackage etc. svn path=/nixpkgs/trunk/; revision=22876
2010-08-02 15:57:57 +02:00
multitran = recurseIntoAttrs (let callPackage = newScope pkgs.multitran; in rec {
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
multitrandata = callPackage ../tools/text/multitran/data { };
Adding multitran. I added a note in the 'data' expression, regarding a locale that should be added into the system. svn path=/nixpkgs/trunk/; revision=14582
2009-03-17 22:49:39 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libbtree = callPackage ../tools/text/multitran/libbtree { };
Adding multitran. I added a note in the 'data' expression, regarding a locale that should be added into the system. svn path=/nixpkgs/trunk/; revision=14582
2009-03-17 22:49:39 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmtsupport = callPackage ../tools/text/multitran/libmtsupport { };
Adding multitran. I added a note in the 'data' expression, regarding a locale that should be added into the system. svn path=/nixpkgs/trunk/; revision=14582
2009-03-17 22:49:39 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libfacet = callPackage ../tools/text/multitran/libfacet { };
Adding multitran. I added a note in the 'data' expression, regarding a locale that should be added into the system. svn path=/nixpkgs/trunk/; revision=14582
2009-03-17 22:49:39 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmtquery = callPackage ../tools/text/multitran/libmtquery { };
Adding multitran. I added a note in the 'data' expression, regarding a locale that should be added into the system. svn path=/nixpkgs/trunk/; revision=14582
2009-03-17 22:49:39 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mtutils = callPackage ../tools/text/multitran/mtutils { };
* Add callPackage etc. svn path=/nixpkgs/trunk/; revision=22876
2010-08-02 15:57:57 +02:00
});
Adding multitran. I added a note in the 'data' expression, regarding a locale that should be added into the system. svn path=/nixpkgs/trunk/; revision=14582
2009-03-17 22:49:39 +01:00
munge 0.5.10: New package, a credentials handler for clusters
2013-04-22 16:04:41 +02:00
munge = callPackage ../tools/security/munge { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
muscleframework = callPackage ../tools/security/muscleframework { };
Adding more muscle programs and libraries. svn path=/nixpkgs/trunk/; revision=19320
2010-01-09 19:06:37 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
muscletool = callPackage ../tools/security/muscletool { };
Adding more muscle programs and libraries. svn path=/nixpkgs/trunk/; revision=19320
2010-01-09 19:06:37 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mysql2pgsql = callPackage ../tools/misc/mysql2pgsql { };
added mysql2pgsql (mysql dump to postrges sql converter) script svn path=/nixpkgs/trunk/; revision=11943
2008-06-01 00:49:00 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
namazu = callPackage ../tools/text/namazu { };
Add Namazu, a full-text search engine. svn path=/nixpkgs/trunk/; revision=13655
2008-12-17 18:09:29 +01:00
nbd: we don't generate statically linked binaries for that package anymore, so it's no longer necessary to pass a special version of glib to the expression. svn path=/nixpkgs/trunk/; revision=29802
2011-10-13 09:26:44 +02:00
nbd = callPackage ../tools/networking/nbd { };
Added nc6, updated xkeyboard-config svn path=/nixpkgs/trunk/; revision=10469
2008-02-03 09:53:47 +01:00
Add New-DJBDNS
2014-03-29 17:47:23 +01:00
ndjbdns = callPackage ../tools/networking/ndjbdns { };
netatalk-3.0.5
2013-09-16 07:54:57 +02:00
netatalk = callPackage ../tools/filesystems/netatalk { };
added netcdf-4.1.1 svn path=/nixpkgs/trunk/; revision=24722
2010-11-17 11:05:46 +01:00
netcdf = callPackage ../development/libraries/netcdf { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nc6 = callPackage ../tools/networking/nc6 { };
Added ncat - for IPv6 support. svn path=/nixpkgs/trunk/; revision=8964
2007-07-09 09:23:16 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ncat = callPackage ../tools/networking/ncat { };
* added ncftp svn path=/nixpkgs/trunk/; revision=17214
2009-09-17 09:31:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ncftp = callPackage ../tools/networking/ncftp { };
applying patches provided by griswold svn path=/nixpkgs/trunk/; revision=19707
2010-01-27 13:12:35 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ncompress = callPackage ../tools/compression/ncompress { };
add bzip2Static svn path=/nixpkgs/trunk/; revision=6269
2006-08-27 15:00:20 +02:00
* Added ndisc6 (which contains IPv6 related commands such as ndisc6, rdisc6 and rdnssd). svn path=/nixpkgs/trunk/; revision=26492
2011-03-24 15:30:06 +01:00
ndisc6 = callPackage ../tools/networking/ndisc6 { };
all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=26824
2011-04-13 19:53:07 +02:00
Adding netboot svn path=/nixpkgs/trunk/; revision=28872
2011-08-29 12:16:36 +02:00
netboot = callPackage ../tools/networking/netboot {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
netcat = callPackage ../tools/networking/netcat { };
Adding netkit tftp client and server. svn path=/nixpkgs/trunk/; revision=16780
2009-08-19 22:19:27 +02:00
Add netcat-openbsd, TCP/IP swiss army knife, openbsd variant
2013-10-17 14:14:46 +02:00
netcat-openbsd = callPackage ../tools/networking/netcat-openbsd { };
nethogs: Add package nethogs is a small 'net top' tool, grouping bandwidth by process.
2014-04-23 17:51:14 +02:00
nethogs = callPackage ../tools/networking/nethogs { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
netkittftp = callPackage ../tools/networking/netkit/tftp { };
Adding remind and netpbm (maybe without all possible programs). I agree the netpbm installation script is quite ugly, but I left a comment there. svn path=/nixpkgs/trunk/; revision=14253
2009-02-25 23:44:08 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
netpbm = callPackage ../tools/graphics/netpbm { };
* Added netselect. svn path=/nixpkgs/trunk/; revision=9225
2007-08-31 13:14:05 +02:00
Add new package netrw, version 1.3.2. The upstream URL unfortunately wasn't available at this time, so I provided an alternate mirror. I checksummed the file against the hashes from various distributions in order to make sure it's the right one.
2012-07-20 01:45:49 +02:00
netrw = callPackage ../tools/networking/netrw { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
netselect = callPackage ../tools/networking/netselect { };
* Added netselect. svn path=/nixpkgs/trunk/; revision=9225
2007-08-31 13:14:05 +02:00
network-manager: packaged, maybe even works. svn path=/nixpkgs/trunk/; revision=25367
2011-01-03 19:01:10 +01:00
networkmanager = callPackage ../tools/networking/network-manager { };
add networ-manager-openvpn, WIP
2013-04-03 01:08:48 +02:00
networkmanager_openvpn = callPackage ../tools/networking/network-manager/openvpn.nix { };
Add NetworkManager-pptp svn path=/nixpkgs/trunk/; revision=29271
2011-09-14 17:50:14 +02:00
networkmanager_pptp = callPackage ../tools/networking/network-manager/pptp.nix { };
openconnect and vpnc NetworkManager plugins added also openvpn plugin updated to the same version as NetworkManager
2013-07-10 16:18:18 +02:00
networkmanager_vpnc = callPackage ../tools/networking/network-manager/vpnc.nix { };
network-manager: Fix all plugins to use gnome3 and gtk3, like nm-applet does I think this makes sense, because now all the plugins will be gnome3 gtk3 based, the same way nm-applet is. I also removed networkmanager_pptp_gnome variation of networkmanager_pptp package, because i think no variation is needed and gnome support should be on by default like in other packages.
2014-05-20 20:30:44 +02:00
networkmanager_openconnect = callPackage ../tools/networking/network-manager/openconnect.nix { };
openconnect and vpnc NetworkManager plugins added also openvpn plugin updated to the same version as NetworkManager
2013-07-10 16:18:18 +02:00
Fix network-manager-applet startup issue 'GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.' (cherry picked from commit 51dc1ddb7c6e974e36c1a2d8701fbc7c254cbc72) Conflicts: pkgs/tools/networking/network-manager-applet/default.nix
2014-06-26 19:41:43 +02:00
networkmanagerapplet = newScope gnome ../tools/networking/network-manager-applet { dconf = gnome3.dconf; };
nm-applet: packaged svn path=/nixpkgs/trunk/; revision=26526
2011-03-26 19:18:32 +01:00
newsbeuter: add expression
2013-06-02 08:27:00 +02:00
newsbeuter = callPackage ../applications/networking/feedreaders/newsbeuter { };
newsbeuter: add dev expression
2013-11-12 23:23:44 +01:00
newsbeuter-dev = callPackage ../applications/networking/feedreaders/newsbeuter/dev.nix { };
ngrep: new package ngrep is a command-line network packet analyzer. http://ngrep.sourceforge.net/
2014-01-03 15:41:18 +01:00
ngrep = callPackage ../tools/networking/ngrep { };
add ngrok: Reverse proxy that creates a secure tunnel between from a public endpoint to a locally running web service
2013-10-27 14:26:13 +01:00
ngrok = callPackage ../tools/misc/ngrok { };
newsbeuter: add expression
2013-06-02 08:27:00 +02:00
mpack: add version 1.6
2013-08-17 14:42:06 +02:00
mpack = callPackage ../tools/networking/mpack { };
pa-applet: add pulseaudio applet
2013-05-05 23:09:46 +02:00
pa_applet = callPackage ../tools/audio/pa-applet { };
Initial packaging for pnmixer
2014-08-24 03:47:29 +02:00
pnmixer = callPackage ../tools/audio/pnmixer { };
Add nifskope
2014-05-07 00:06:56 +02:00
nifskope = callPackage ../tools/graphics/nifskope { };
Looks like 2.6.35.2 commits a fix that breaks AUFS2 svn path=/nixpkgs/trunk/; revision=23295
2010-08-20 23:39:22 +02:00
nilfs_utils = callPackage ../tools/filesystems/nilfs-utils {};
Nitrogen build working. Missing custom icons in GUI.
2014-06-13 19:32:29 +02:00
nitrogen = callPackage ../tools/X11/nitrogen {};
add some versions of cppunit/boost/protobuf, added binutils with gold, added nlopt svn path=/nixpkgs/trunk/; revision=27132
2011-05-04 12:03:46 +02:00
nlopt = callPackage ../development/libraries/nlopt {};
npapi-sdk: New package NPAPI-SDK is a bundle of NPAPI headers by Mozilla.
2014-03-25 17:29:03 +01:00
npapi_sdk = callPackage ../development/libraries/npapi-sdk {};
npth: successor of the pth library, used by upcoming versions of gnupg and its libraries svn path=/nixpkgs/trunk/; revision=33680
2012-04-09 12:17:32 +02:00
npth = callPackage ../development/libraries/npth {};
nmap: Build the non-graphical version by default
2014-04-03 21:07:52 +02:00
nmap = callPackage ../tools/security/nmap { };
nmap_graphical = callPackage ../tools/security/nmap {
Fix typo from previous commit. svn path=/nixpkgs/trunk/; revision=16230
2009-07-08 00:34:03 +02:00
inherit (pythonPackages) pysqlite;
nmap: Build the non-graphical version by default
2014-04-03 21:07:52 +02:00
graphicalSupport = true;
* Added bsdiff 4.2. Wow, this is even better than zdelta (which in turn appears to be better than vdelta). svn path=/nixpkgs/trunk/; revision=1819
2004-11-29 22:17:29 +01:00
};
notbit: Add Package
2014-03-10 17:03:55 +01:00
notbit = callPackage ../applications/networking/notbit { };
nox: Added expression
2014-08-08 22:07:08 +02:00
nox = callPackage ../tools/package-management/nox {
pythonPackages = python3Packages;
nix = nixUnstable;
};
Add nss-pam-ldapd version 0.8.10 nss-pam-ldapd is a fork of nss_ldap that uses a daemon (nslcd) to connect to the LDAP server, instead of going directly from PAM/NSS. This improves performance and separation, and increases security if you connect to LDAP with a password, since only the nscd daemon needs to know the password, not every user of PAM/NSS. This commit will be followed by a commit to NixOS which enables the use of the nslcd daemon.
2012-09-14 00:06:25 +02:00
nss_pam_ldapd = callPackage ../tools/networking/nss-pam-ldapd {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ntfs3g = callPackage ../tools/filesystems/ntfs-3g { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
Actually upgrade ntfs-3g ntfsprogs collection is now part of ntfs-3g svn path=/nixpkgs/trunk/; revision=31065
2011-12-24 23:28:00 +01:00
# ntfsprogs are merged into ntfs-3g
ntfsprogs = pkgs.ntfs3g;
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
Adding ntop. It runs for me, if using "-P directory". svn path=/nixpkgs/trunk/; revision=33870
2012-04-21 17:04:46 +02:00
ntop = callPackage ../tools/networking/ntop { };
ntopng: new package ntopng is a high-speed web-based traffic analysis and flow collection tool. ntopng => ntop next generation. http://www.ntop.org/products/ntop/
2013-11-05 23:11:57 +01:00
ntopng = callPackage ../tools/networking/ntopng { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ntp = callPackage ../tools/networking/ntp { };
* NTP daemon. svn path=/nixpkgs/trunk/; revision=7459
2006-12-21 23:23:17 +01:00
Add numdiff-5.6.1 A little program that can be used to compare putatively similar files line by line and field by field, ignoring small numeric differences or/and different numeric formats.
2013-06-01 00:49:30 +02:00
numdiff = callPackage ../tools/text/numdiff { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nssmdns = callPackage ../tools/networking/nss-mdns { };
Add `nss-mdns', an NSS plug-in for the `.local' domain, using mDNS. svn path=/nixpkgs/trunk/; revision=11160
2008-03-17 14:41:54 +01:00
nwdiag: new package Nwdiag generates network-diagram image from spec-text file (similar to Graphviz).
2013-09-21 19:48:54 +02:00
nwdiag = pythonPackages.nwdiag;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nylon = callPackage ../tools/networking/nylon { };
Adding nylon. svn path=/nixpkgs/trunk/; revision=14254
2009-02-26 00:21:44 +01:00
* Doh, forgot to commit. svn path=/nixpkgs/trunk/; revision=27059
2011-04-30 11:21:38 +02:00
nzbget = callPackage ../tools/networking/nzbget { };
all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=27648
2011-07-07 23:32:55 +02:00
Adding oath-toolkit and xmlsec I added xmlsec to make it work with oath-toolkit (to build one extra tool there, that I don't need), but I couldn't make it work together.
2013-03-31 00:07:35 +01:00
oathToolkit = callPackage ../tools/security/oath-toolkit { };
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
obex_data_server = callPackage ../tools/bluetooth/obex-data-server { };
* Added Blueman (a Bluetooth application). * Added obex-data-server and python-notify, needed by Blueman. svn path=/nixpkgs/trunk/; revision=22497
2010-07-06 16:54:22 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
obexd = callPackage ../tools/bluetooth/obexd { };
* Added obexd. svn path=/nixpkgs/trunk/; revision=17497
2009-09-29 14:54:08 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
obexfs = callPackage ../tools/bluetooth/obexfs { };
* Various OBEX-related tools. svn path=/nixpkgs/trunk/; revision=16595
2009-08-06 01:24:27 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
obexftp = callPackage ../tools/bluetooth/obexftp { };
* Various OBEX-related tools. svn path=/nixpkgs/trunk/; revision=16595
2009-08-06 01:24:27 +02:00
Moved obnam from pythonPackages to pkgs. svn path=/nixpkgs/trunk/; revision=34336
2012-06-04 07:02:31 +02:00
obnam = callPackage ../tools/backup/obnam { };
odt2txt-0.4 svn path=/nixpkgs/trunk/; revision=29734
2011-10-09 20:22:18 +02:00
odt2txt = callPackage ../tools/text/odt2txt { };
offlineimap: enable support for the sqlite status backend
2013-04-12 13:13:32 +02:00
offlineimap = callPackage ../tools/networking/offlineimap {
inherit (pythonPackages) sqlite3;
};
Adding offlineimap, in a not very elegant way. svn path=/nixpkgs/trunk/; revision=21034
2010-04-12 23:03:22 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
opendbx = callPackage ../development/libraries/opendbx { };
added opendbx 1.4.4 svn path=/nixpkgs/trunk/; revision=19872
2010-02-09 10:05:14 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
opendkim = callPackage ../development/libraries/opendkim { };
added libmilter, opendkim svn path=/nixpkgs/trunk/; revision=19875
2010-02-09 11:32:55 +01:00
Definitions for Open Dylan 2013.2 (Dylan Language Implementation)
2014-05-27 04:28:09 +02:00
opendylan = callPackage ../development/compilers/opendylan {
opendylan-bootstrap = opendylan_bin;
};
opendylan_bin = callPackage ../development/compilers/opendylan/bin.nix { };
openjade: Use default perl
2014-08-21 16:24:45 +02:00
openjade = callPackage ../tools/text/sgml/openjade { };
new: openjade, opensp - by Russell O'Connor svn path=/nixpkgs/trunk/; revision=17926
2009-10-22 17:41:39 +02:00
Add new openntpd package in version 20080406p-10. It's actually a fork from Debian who are providing cross-platform compatibility fixes for it. A big advantage is that it is far more minimal than the ntpd reference implementation and especially useful if you don't want to run an NTP service. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-09-01 14:51:50 +02:00
openntpd = callPackage ../tools/networking/openntpd { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openobex = callPackage ../tools/bluetooth/openobex { };
* Various OBEX-related tools. svn path=/nixpkgs/trunk/; revision=16595
2009-08-06 01:24:27 +02:00
openopc: new package "OPC (OLE for Process Control) toolkit designed for use with Python" This package contains a python module (OpenOPC) and a command line client (opc). The OpenOPC Gateway Service for Windows is also copied to $out, for reference. It only works with python2.7 (not python3.x), so I'm not adding it to python-packages.nix. Also add needed dependency, python-pyro3, a distributed object middleware for Python (IPC/RPC). http://openopc.sourceforge.net/
2014-02-26 23:58:24 +01:00
openopc = callPackage ../tools/misc/openopc {
pythonFull = python27Full.override {
extraLibs = [ python27Packages.pyro3 ];
};
};
* Added openresolv, a program for managing /etc/resolv.conf. svn path=/nixpkgs/trunk/; revision=32337
2012-02-16 19:40:05 +01:00
openresolv = callPackage ../tools/networking/openresolv { };
opensc: update to version 0.13.0
2013-12-02 12:37:24 +01:00
opensc = callPackage ../tools/security/opensc { };
Downgrading the opensc library version to 0.11.7, that required for the Spanish national id smartcard (DNIe). Adding the opensc dnie driver. svn path=/nixpkgs/trunk/; revision=19325
2010-01-10 01:22:29 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
opensc_dnie_wrapper = callPackage ../tools/security/opensc-dnie-wrapper { };
Adding a global wrapper that provides the user with ready-to-use opensc tools and a 'firefox-dnie' that will launch the firefox in the path with the proper environment variables to allow firefox access the Spanish national id SmartCard as a Security Device. For the later to work cleanly, it will require the user to enable the opensc-pkcs11 module as Security Devices in firefox. svn path=/nixpkgs/trunk/; revision=19452
2010-01-15 00:43:56 +01:00
OpenSSH: add Kerberos support
2013-06-15 08:40:01 +02:00
openssh =
callPackage ../tools/networking/openssh {
hpnSupport = false;
withKerberos = false;
etcDir = "/etc/ssh";
pam = if stdenv.isLinux then pam else null;
};
openssh: Update from 6.2p2 -> 6.4p1 This patch also bumps up the HPN version of openssh so that it compiles on top of 6.4. Along with the bump, a package was added for the high performance networking version. The gcmrekey patch was removed as this vulnerability is fixed in version 6.4 onward. http://www.openssh.org/txt/gcmrekey.adv
2013-12-29 17:50:16 +01:00
Make appendToName do the right thing I.e. append a suffix *before* the version, rather than after. So we get "sqlite-interactive-3.8.0.2" instead of "sqlite-3.8.0.2-interactive". The latter is broken since nix-env just sees it the suffix as part of the version, so "nix-env -u" will happily upgrade "sqlite-3.8.0.2-interactive" to "sqlite-3.9".
2014-03-10 15:01:56 +01:00
openssh_hpn = pkgs.appendToName "with-hpn" (openssh.override { hpnSupport = true; });
openssh: Update from 6.2p2 -> 6.4p1 This patch also bumps up the HPN version of openssh so that it compiles on top of 6.4. Along with the bump, a package was added for the high performance networking version. The gcmrekey patch was removed as this vulnerability is fixed in version 6.4 onward. http://www.openssh.org/txt/gcmrekey.adv
2013-12-29 17:50:16 +01:00
Make appendToName do the right thing I.e. append a suffix *before* the version, rather than after. So we get "sqlite-interactive-3.8.0.2" instead of "sqlite-3.8.0.2-interactive". The latter is broken since nix-env just sees it the suffix as part of the version, so "nix-env -u" will happily upgrade "sqlite-3.8.0.2-interactive" to "sqlite-3.9".
2014-03-10 15:01:56 +01:00
openssh_with_kerberos = pkgs.appendToName "with-kerberos" (openssh.override { withKerberos = true; });
* Updates paths in all-packages-generic.fix. svn path=/nixpkgs/trunk/; revision=472
2003-11-03 19:21:30 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
opensp = callPackage ../tools/text/sgml/opensp { };
new: openjade, opensp - by Russell O'Connor svn path=/nixpkgs/trunk/; revision=17926
2009-10-22 17:41:39 +02:00
Add sp compatibility wrapper This wrapper is required by some old programs (e.g., po4a which I'm trying to package) svn path=/nixpkgs/trunk/; revision=25320
2010-12-29 19:04:11 +01:00
spCompat = callPackage ../tools/text/sgml/opensp/compat.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openvpn = callPackage ../tools/networking/openvpn { };
adding openvpn svn path=/nixpkgs/trunk/; revision=14901
2009-04-06 15:07:18 +02:00
openvpn: add openvpn_learnaddress script
2013-10-21 21:47:14 +02:00
openvpn_learnaddress = callPackage ../tools/networking/openvpn/openvpn_learnaddress.nix { };
add openvswitch package + basic nixos module to enable it
2014-06-12 15:16:38 +02:00
openvswitch = callPackage ../os-specific/linux/openvswitch { };
optipng: use system libpng & zlib, fix cross builds and add support for static builds
2014-04-01 01:37:10 +02:00
optipng = callPackage ../tools/graphics/optipng {
libpng = libpng12;
};
Adding optipng, and a basic expression for pdfread. svn path=/nixpkgs/trunk/; revision=20802
2010-03-24 00:04:41 +01:00
Adding oslrd.
2013-05-28 22:37:59 +02:00
oslrd = callPackage ../tools/networking/oslrd { };
Add initial attempt at ossec Note: This will almost certainly not work as-is, but at least it compiles. NixOS module to come.
2012-07-09 17:44:44 +02:00
ossec = callPackage ../tools/security/ossec {};
Adding otpw (a one-time password system)
2013-03-30 20:01:05 +01:00
otpw = callPackage ../os-specific/linux/otpw { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
p7zip = callPackage ../tools/archivers/p7zip { };
* Added p7zip for decompressing 7-zip archives. svn path=/nixpkgs/trunk/; revision=9248
2007-09-04 13:55:19 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
pal = callPackage ../tools/misc/pal { };
Adding the calendar program 'pal' svn path=/nixpkgs/trunk/; revision=23070
2010-08-09 23:13:36 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
panomatic = callPackage ../tools/graphics/panomatic { };
Adding panomatic. svn path=/nixpkgs/trunk/; revision=14981
2009-04-10 11:42:22 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
par2cmdline = callPackage ../tools/networking/par2cmdline { };
added packages: which, libtool aggregation in all-packages-generic: autotools building strategoxt from svn not complete yet since autconf cannot find libtool svn path=/nixpkgs/trunk/; revision=596
2003-12-23 21:51:58 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
parallel = callPackage ../tools/misc/parallel { };
Add GNU Parallel. svn path=/nixpkgs/trunk/; revision=21552
2010-05-02 11:27:32 +02:00
add parcellite-1.1.4
2013-05-18 07:22:49 +02:00
parcellite = callPackage ../tools/misc/parcellite { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
patchutils = callPackage ../tools/text/patchutils { };
added patchutils svn path=/nixpkgs/trunk/; revision=12387
2008-07-19 01:36:28 +02:00
Move GNU/Hurd package attributes under `os-specific/gnu/default.nix'. svn path=/nixpkgs/trunk/; revision=30173
2011-11-01 23:10:51 +01:00
parted = callPackage ../tools/misc/parted { hurd = null; };
* Added GNU wget to the stdenv. svn path=/nixpkgs/trunk/; revision=477
2003-11-04 09:44:46 +01:00
add pitivi 0.93
2014-03-22 15:33:35 +01:00
pitivi = callPackage ../applications/video/pitivi {
gst = gst_all_1;
clutter-gtk = clutter_gtk;
pitivi: fix icons
2014-03-22 16:57:24 +01:00
inherit (gnome3) gnome_icon_theme gnome_icon_theme_symbolic;
add pitivi 0.93
2014-03-22 15:33:35 +01:00
};
p0f: version 3.06b Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-31 18:22:50 +02:00
p0f = callPackage ../tools/security/p0f { };
all-packages.nix: strip trailing whitespace
2014-08-20 11:57:56 +02:00
pngout: Create new package
2014-08-14 15:59:22 +02:00
pngout = callPackage ../tools/graphics/pngout { };
p0f: version 3.06b Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-31 18:22:50 +02:00
Parted (cross-GNU): Only refer to `.hostDrv' when cross-building. svn path=/nixpkgs/branches/stdenv-updates/; revision=25090
2010-12-13 00:35:10 +01:00
hurdPartedCross =
if crossSystem != null && crossSystem.config == "i586-pc-gnu"
hurdPartedCross: Make overridable. svn path=/nixpkgs/trunk/; revision=33630
2012-04-05 19:32:02 +02:00
then (makeOverridable
({ hurd }:
(parted.override {
# Needs the Hurd's libstore.
inherit hurd;
# The Hurd wants a libparted.a.
enableStatic = true;
gettext = null;
readline = null;
devicemapper = null;
Rename hostDrv -> crossDrv, buildDrv -> nativeDrv This is for consistency with terminology in stdenv (and the terms "hostDrv" and "buildDrv" are not very intuitive, even if they're consistent with GNU terminology).
2012-12-28 19:08:19 +01:00
}).crossDrv)
hurdPartedCross: Make overridable. svn path=/nixpkgs/trunk/; revision=33630
2012-04-05 19:32:02 +02:00
{ hurd = gnu.hurdCrossIntermediate; })
Parted (cross-GNU): Only refer to `.hostDrv' when cross-building. svn path=/nixpkgs/branches/stdenv-updates/; revision=25090
2010-12-13 00:35:10 +01:00
else null;
GNU Parted: Allow cross-GNU builds. svn path=/nixpkgs/branches/stdenv-updates/; revision=25088
2010-12-13 00:21:35 +01:00
ipsec-tools: fix build by passing old version of flex
2014-04-11 11:09:59 +02:00
ipsecTools = callPackage ../os-specific/linux/ipsec-tools { flex = flex_2_5_35; };
ipsec-tools: add version 0.8.0
2012-10-20 13:06:09 +02:00
* Delete some obsolete packages. * Make sure that every package in all-packages.nix has a unique name. Not all of them do, but there are now a few helper functions that modify the name of a package for display purposes in nix-env (e.g., you get "zlib-1.2.3" and "zlib-1.2.3-static" in "nix-env -qa"). svn path=/nixpkgs/trunk/; revision=8607
2007-04-26 15:02:30 +02:00
patch = gnupatch;
* The stdenv setup script now defines a generic builder that allows builders for typical Autoconf-style to be much shorten, e.g., . $stdenv/setup genericBuild The generic builder does lots of stuff automatically: - Unpacks source archives specified by $src or $srcs (it knows about gzip, bzip2, tar, zip, and unpacked source trees). - Determines the source tree. - Applies patches specified by $patches. - Fixes libtool not to search for libraries in /lib etc. - Runs `configure'. - Runs `make'. - Runs `make install'. - Strips debug information from static libraries. - Writes nested log information (in the format accepted by `log2xml'). There are also lots of hooks and variables to customise the generic builder. See `stdenv/generic/docs.txt'. * Adapted the base packages (i.e., the ones used by stdenv) to use the generic builder. * We now use `curl' instead of `wget' to download files in `fetchurl'. * Neither `curl' nor `wget' are part of stdenv. We shouldn't encourage people to download stuff in builders (impure!). * Updated some packages. * `buildinputs' is now `buildInputs' (but the old name also works). * `findInputs' in the setup script now prevents inputs from being processed multiple times (which could happen, e.g., if an input was a propagated input of several other inputs; this caused the size variables like $PATH to blow up exponentially in the worst case). * Patched GNU Make to write nested log information in the format accepted by `log2xml'. Also, prior to writing the build command, Make now writes a line `building X' to indicate what is being built. This is unfortunately often obscured by the gigantic tool invocations in many Makefiles. The actual build commands are marked `unimportant' so that they don't clutter pages generated by `log2html'. svn path=/nixpkgs/trunk/; revision=845
2004-03-19 17:53:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pbzip2 = callPackage ../tools/compression/pbzip2 { };
Adding pbzip2 (Parallel bzip2 for multicore machines) svn path=/nixpkgs/trunk/; revision=19011
2009-12-17 12:10:01 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pciutils = callPackage ../tools/system/pciutils { };
* Latest pciutils. svn path=/nixpkgs/trunk/; revision=7914
2007-02-19 21:18:20 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pcsclite = callPackage ../tools/security/pcsclite { };
Adding pcsclite with the opensource ccid usb drivers. This gives a daemon controlling the smartcard reader used to read the Spanish identity card. svn path=/nixpkgs/trunk/; revision=19319
2010-01-09 18:35:57 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pdf2djvu = callPackage ../tools/typesetting/pdf2djvu { };
Adding pdf2djvu, updating djvulibre, and getting more headers from poppler. svn path=/nixpkgs/trunk/; revision=14760
2009-03-29 22:32:41 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pdfjam = callPackage ../tools/typesetting/pdfjam { };
A pkgs/tools/typesetting/pdfjam A pkgs/tools/typesetting/pdfjam/builder.sh A pkgs/tools/typesetting/pdfjam/default.nix Added pdfjam, a package with the following tools: * pdfnup, which allows PDF files to be "n-upped" in roughly the way that psnup does for PostScript files. * pdfjoin, which concatenates the pages of multiple PDF files together into a single file * pdf90, which rotates the pages of one or more PDF files through 90 degrees (anti-clockwise). M pkgs/development/compilers/jdk/jdk6-linux.nix Typo svn path=/nixpkgs/trunk/; revision=8404
2007-03-21 13:53:01 +01:00
Added jbig2enc.
2013-01-16 11:43:53 +01:00
jbig2enc = callPackage ../tools/graphics/jbig2enc { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pdfread = callPackage ../tools/graphics/pdfread { };
Adding optipng, and a basic expression for pdfread. svn path=/nixpkgs/trunk/; revision=20802
2010-03-24 00:04:41 +01:00
Committing some outstanding modifications that I cannot make into smaller chunks anymore. * added briss: a pdf cropper * added compton, an improved fork of xcompmgr * added myself to the maintainers list * minor version bumps: xcompmgr, upower svn path=/nixpkgs/trunk/; revision=34380
2012-06-08 12:16:46 +02:00
briss = callPackage ../tools/graphics/briss { };
bully, a wpa/wpa2 passphrase retriever from wps enabled devices
2014-01-26 21:42:18 +01:00
bully = callPackage ../tools/networking/bully { };
Adding pdnsd svn path=/nixpkgs/trunk/; revision=29438
2011-09-22 13:28:56 +02:00
pdnsd = callPackage ../tools/networking/pdnsd { };
add peco: Simplistic interactive filtering tool
2014-08-03 15:26:06 +02:00
peco = callPackage ../tools/text/peco { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pg_top = callPackage ../tools/misc/pg_top { };
added pg_top svn path=/nixpkgs/trunk/; revision=17711
2009-10-08 10:53:21 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pdsh = callPackage ../tools/networking/pdsh {
Add latest Linux kernel for real i686 platform, not modern amd64-in-32bit-mode svn path=/nixpkgs/trunk/; revision=23173
2010-08-14 18:04:02 +02:00
rsh = true; # enable internal rsh implementation
pkgs/top-level/all-packages.nix: prefer makeOverridable over getPkgConfig to customize pdsh Changed 'pdsh' expression to allow for argument overriding instead of relying on getPkgConfig. svn path=/nixpkgs/trunk/; revision=21867
2010-05-19 14:26:00 +02:00
ssh = openssh;
new: pdsh is a fast and efficient parallel remote shell svn path=/nixpkgs/trunk/; revision=12313
2008-07-08 01:11:36 +02:00
};
pfstools-1.8.3; builds against qt4 svn path=/nixpkgs/trunk/; revision=29403
2011-09-21 00:49:07 +02:00
pfstools = callPackage ../tools/graphics/pfstools { };
Adding qtpfsgui and pfstools. Updating fftw because the src URL didn't work anymore. svn path=/nixpkgs/trunk/; revision=14892
2009-04-05 23:41:13 +02:00
Adding philter mail sorter svn path=/nixpkgs/trunk/; revision=24336
2010-10-18 07:33:31 +02:00
philter = callPackage ../tools/networking/philter { };
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
pinentry = callPackage ../tools/security/pinentry { };
added missing top-level attribute pinentry svn path=/nixpkgs/trunk/; revision=11725
2008-04-26 01:43:14 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pius = callPackage ../tools/security/pius { };
Add PIUS. svn path=/nixpkgs/trunk/; revision=22580
2010-07-13 18:32:14 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pk2cmd = callPackage ../tools/misc/pk2cmd { };
Adding the Microchip software for the PICKit2 programmer: pk2cmd svn path=/nixpkgs/trunk/; revision=21726
2010-05-11 18:17:26 +02:00
plantuml: new package PlantUML draws UML diagrams using a simple and human readable text description.
2013-10-14 19:27:11 +02:00
plantuml = callPackage ../tools/misc/plantuml { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
plan9port = callPackage ../tools/system/plan9port { };
Adding plan9port with X11 support. For acme to work, set the PLAN9 variable, and have the plan9port programs in the PATH. svn path=/nixpkgs/trunk/; revision=14669
2009-03-23 22:31:30 +01:00
Ploticus 2.41. svn path=/nixpkgs/trunk/; revision=34216
2012-05-22 23:18:25 +02:00
ploticus = callPackage ../tools/graphics/ploticus {
libpng = libpng12;
};
add eject, but remove the po subdir svn path=/nixpkgs/trunk/; revision=3766
2005-09-01 18:38:31 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
plotutils = callPackage ../tools/graphics/plotutils { };
adding plotutils svn path=/nixpkgs/trunk/; revision=17862
2009-10-18 06:43:50 +02:00
Add package: plowshare-git20120807
2012-08-26 14:43:25 +02:00
plowshare = callPackage ../tools/misc/plowshare { };
Adding pngcrush svn path=/nixpkgs/trunk/; revision=29411
2011-09-21 09:33:38 +02:00
pngcrush = callPackage ../tools/graphics/pngcrush { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pngnq = callPackage ../tools/graphics/pngnq { };
Adding pngnq. svn path=/nixpkgs/trunk/; revision=20801
2010-03-23 23:40:46 +01:00
Pass libpng-1.2 to pngtoico svn path=/nixpkgs/branches/libpng15/; revision=32555
2012-02-25 04:09:36 +01:00
pngtoico = callPackage ../tools/graphics/pngtoico {
libpng = libpng12;
};
Adding pngtoico. svn path=/nixpkgs/trunk/; revision=31264
2012-01-04 10:29:52 +01:00
Add pngquant, it converts 24/32-bit RGBA PNGs to 8-bit palette with alpha channel preserved.
2013-10-28 18:32:23 +01:00
pngquant = callPackage ../tools/graphics/pngquant { };
Add PODIFF, a tool to diff PO files
2013-01-30 14:36:50 +01:00
podiff = callPackage ../tools/text/podiff { };
add poedit
2013-09-13 20:42:39 +02:00
poedit = callPackage ../tools/text/poedit { };
Polipo: packaged svn path=/nixpkgs/trunk/; revision=27177
2011-05-08 01:41:34 +02:00
polipo = callPackage ../servers/polipo { };
Add polkit-kde-agent Move pinentry and polkit-gnome to tools/security. svn path=/nixpkgs/trunk/; revision=28656
2011-08-18 14:52:50 +02:00
polkit_gnome = callPackage ../tools/security/polkit-gnome { };
Adding ponysay.
2013-08-10 01:21:25 +02:00
ponysay = callPackage ../tools/misc/ponysay { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
povray = callPackage ../tools/graphics/povray { };
Adding povray svn path=/nixpkgs/trunk/; revision=15598
2009-05-14 10:49:46 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ppl = callPackage ../development/libraries/ppl { };
Add the Parma Polyhedra Library (PPL), an optional dependency of GCC 4.4. svn path=/nixpkgs/trunk/; revision=16421
2009-07-18 23:22:13 +02:00
ppp-2.4.5, a few patches svn path=/nixpkgs/trunk/; revision=31279
2012-01-04 16:10:27 +01:00
ppp = callPackage ../tools/networking/ppp { };
Adding ppp and rp-pppoe for different point-to-point connectivity situations. Not tested for trivial reasons, but built OK svn path=/nixpkgs/trunk/; revision=13925
2009-02-01 14:54:20 +01:00
Add pptp client svn path=/nixpkgs/trunk/; revision=29267
2011-09-14 10:39:51 +02:00
pptp = callPackage ../tools/networking/pptp {};
fix eval
2013-10-14 17:13:50 +02:00
prey-bash-client = callPackage ../tools/security/prey { };
add prey: Proven tracking software that helps you find, lock and recover your devices when stolen or missing
2013-10-14 11:57:40 +02:00
add projectM 2.1.0
2014-01-11 08:24:54 +01:00
projectm = callPackage ../applications/audio/projectm { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
proxychains = callPackage ../tools/networking/proxychains { };
Committing Lluís Batlle's submissions from mailing list posting <45219fb00901110456i6f21db35tbd1894eaea2146ff@mail.gmail.com>: * nixpkgs-ccrypt-1.7-new.patch * nixpkgs-cmake-add-ccmake.patch * nixpkgs-cpufrequtils-005-new.patch * nixpkgs-dwm-5.1-fix.patch * nixpkgs-freeimage-3.11.0-new.patch * nixpkgs-proxychains-3.1-new.patch * nixpkgs-psi-to-0.12.patch * nixpkgs-skype-to-2.0.0.72.patch * nixpkgs-truecrypt-6.1a-fix.patch * nixpkgs-vxl-1.11.0-new.patch * nixpkgs-xkb-popular-esperanto-symbols.patch * nixpkgs-xorg-via-video-fix.patch svn path=/nixpkgs/trunk/; revision=13751
2009-01-12 22:12:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
proxytunnel = callPackage ../tools/misc/proxytunnel { };
Added proxy tunnel tool svn path=/nixpkgs/trunk/; revision=12814
2008-09-06 14:33:25 +02:00
added support for cntlm on nixos! svn path=/nixpkgs/trunk/; revision=29736
2011-10-10 00:28:41 +02:00
cntlm = callPackage ../tools/networking/cntlm { };
pastebinit: new package A software that lets you send anything you want directly to a pastebin from the command line https://launchpad.net/pastebinit
2014-04-03 16:39:46 +02:00
pastebinit = callPackage ../tools/misc/pastebinit { };
all-packages.nix: drop trailing whitespace
2014-04-11 10:06:06 +02:00
Moved tools/misc/psmisc to os-specific/linux/psmisc. svn path=/nixpkgs/trunk/; revision=24469
2010-10-25 16:38:37 +02:00
psmisc = callPackage ../os-specific/linux/psmisc { };
* Added psmisc. svn path=/nixpkgs/trunk/; revision=9905
2007-12-11 12:47:23 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pstoedit = callPackage ../tools/graphics/pstoedit { };
adding ps2edit svn path=/nixpkgs/trunk/; revision=17863
2009-10-18 06:43:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pv = callPackage ../tools/misc/pv { };
Adding pipe viewer. svn path=/nixpkgs/trunk/; revision=14643
2009-03-22 13:34:30 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pwgen = callPackage ../tools/security/pwgen { };
* ncurses: added symlinks for bynary packages linked against libncurses. Tested with ghc. I will add 'unicode' option next check in (for cygwin). * pidgin: Got rid of builder.sh, added ncurses to the dependencies, so it builds finch. * xorg: Added glproto and mesaHeaders to xf86videosis dependencies. Now it compiles. * pwgen: Added. * device-mapper: Version bump. Added 'static' option for use in initrd. * lvm2: Version bump. Added 'static' option for use in initrd. svn path=/nixpkgs/trunk/; revision=8923
2007-06-28 11:53:12 +02:00
Adding pwnat.
2013-05-08 22:42:45 +02:00
pwnat = callPackage ../tools/networking/pwnat { };
Add pycangjie [Bjørn Forsman <bjorn.forsman@gmail.com>: expression cleanup]
2014-02-02 14:34:40 +01:00
pycangjie = callPackage ../development/python-modules/pycangjie { };
Moved python debugger into development/tools hierarchy. svn path=/nixpkgs/trunk/; revision=32027
2012-02-04 10:30:53 +01:00
pydb = callPackage ../development/tools/pydb { };
adding pydb, a python debugging with gdb like commands svn path=/nixpkgs/trunk/; revision=15317
2009-04-26 13:06:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pystringtemplate = callPackage ../development/python-modules/stringtemplate { };
Added python's implementation for the www.stringtemplate.org language. svn path=/nixpkgs/trunk/; revision=13199
2008-11-05 21:03:00 +01:00
dbus_* naming reorganization
2013-03-23 20:31:37 +01:00
pythonDBus = dbus_python;
Added Gajim XMPP client in nearly full-feature configuration with all dependencies svn path=/nixpkgs/trunk/; revision=15001
2009-04-12 21:34:20 +02:00
Added xmpppy - python XMPP library and pyIRCt - python IRC transport svn path=/nixpkgs/trunk/; revision=15005
2009-04-13 01:27:55 +02:00
pythonIRClib = builderDefsPackage (import ../development/python-modules/irclib) {
inherit python;
};
Added Gajim XMPP client in nearly full-feature configuration with all dependencies svn path=/nixpkgs/trunk/; revision=15001
2009-04-12 21:34:20 +02:00
pythonSexy = builderDefsPackage (import ../development/python-modules/libsexy) {
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit python libsexy pkgconfig libxml2 pygtk pango gtk glib;
Added Gajim XMPP client in nearly full-feature configuration with all dependencies svn path=/nixpkgs/trunk/; revision=15001
2009-04-12 21:34:20 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openmpi = callPackage ../development/libraries/openmpi { };
* added mcrl, mcrl2 and openmpi to all-packages.nix svn path=/nixpkgs/trunk/; revision=15874
2009-06-05 16:36:35 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
qhull = callPackage ../development/libraries/qhull { };
Adding qhull, and updating octaves. svn path=/nixpkgs/trunk/; revision=14955
2009-04-08 22:06:03 +02:00
tools/misc/qjoypad: New nixbuild. svn path=/nixpkgs/trunk/; revision=29977
2011-10-23 00:12:45 +02:00
qjoypad = callPackage ../tools/misc/qjoypad { };
Add QScintilla.
2014-08-21 00:41:41 +02:00
qscintilla = callPackage ../development/libraries/qscintilla {
qt = qt4;
};
Move qt3/qt4 choice to .nix expressions svn path=/nixpkgs/trunk/; revision=29404
2011-09-21 00:49:13 +02:00
qshowdiff = callPackage ../tools/text/qshowdiff { };
Adding qshowdiff. svn path=/nixpkgs/trunk/; revision=20633
2010-03-15 15:26:52 +01:00
Added quilt-0.63
2014-07-14 14:45:26 +02:00
quilt = callPackage ../development/tools/quilt { };
* Added radvd, the Router Advertisement Daemon. svn path=/nixpkgs/trunk/; revision=26032
2011-02-19 17:04:34 +01:00
radvd = callPackage ../tools/networking/radvd { };
add ranger 1.6.1
2013-12-12 04:04:38 +01:00
ranger = callPackage ../applications/misc/ranger { };
wip: privateer svn path=/nixpkgs/trunk/; revision=31305
2012-01-05 00:05:51 +01:00
privateer = callPackage ../games/privateer { };
Upgrade rtmpdump and get_iplayer
2014-05-07 20:55:21 +02:00
rtmpdump = callPackage ../tools/video/rtmpdump { };
Adding rtmpdump svn path=/nixpkgs/trunk/; revision=21468
2010-04-30 23:46:55 +02:00
Adding reaver-wps.
2013-04-26 15:06:20 +02:00
reaverwps = callPackage ../tools/networking/reaver-wps {};
GNU Recutils 1.0. svn path=/nixpkgs/branches/stdenv-updates/; revision=25227
2010-12-21 17:26:34 +01:00
recutils = callPackage ../tools/misc/recutils { };
recoll-1.18.1
2013-04-02 00:42:41 +02:00
recoll = callPackage ../applications/search/recoll { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
reiser4progs = callPackage ../tools/filesystems/reiser4progs { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
reiserfsprogs = callPackage ../tools/filesystems/reiserfsprogs { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
relfs = callPackage ../tools/filesystems/relfs {
Drop 'gnomevfs = gnome_vfs;' alias s/gnomevfs/gnome_vfs/ in packages svn path=/nixpkgs/trunk/; revision=29718
2011-10-08 14:06:03 +02:00
inherit (gnome) gnome_vfs GConf;
svn path=/nixpkgs/trunk/; revision=9861
2007-12-04 23:06:13 +01:00
};
Add remarkjs 0.6.4, a markdown-driven slideshow tool Also, add required node packages (and update generated node pkgs).
2014-04-20 22:42:55 +02:00
remarkjs = callPackage ../development/web/remarkjs { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
remind = callPackage ../tools/misc/remind { };
Adding remind and netpbm (maybe without all possible programs). I agree the netpbm installation script is quite ugly, but I left a comment there. svn path=/nixpkgs/trunk/; revision=14253
2009-02-25 23:44:08 +01:00
remmina: add version 1.0.0 Patch submitted by Jan Malakhovski <oxij@oxij.org>.
2012-07-02 16:30:13 +02:00
remmina = callPackage ../applications/networking/remote/remmina {};
Add renameutils package.
2013-03-25 12:19:35 +01:00
renameutils = callPackage ../tools/misc/renameutils { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
replace = callPackage ../tools/text/replace { };
Added replace. Maybe abandon sed for substituteAll ? svn path=/nixpkgs/trunk/; revision=8987
2007-07-15 13:59:33 +02:00
Add reptyr, tool to change controlling terminal of a process under Linux
2012-10-04 07:17:09 +02:00
reptyr = callPackage ../os-specific/linux/reptyr {};
rdiff-backup: Fix nix expression. svn path=/nixpkgs/trunk/; revision=29017
2011-09-05 10:32:55 +02:00
rdiff_backup = callPackage ../tools/backup/rdiff-backup { };
rdiff-backup added svn path=/nixpkgs/trunk/; revision=9280
2007-09-08 22:45:23 +02:00
rdmd: Add (D language compiler helper).
2014-01-10 19:10:22 +01:00
rdmd = callPackage ../development/compilers/rdmd { };
rhash: new package Console utility for computing and verifying hash sums of files http://rhash.anz.ru
2014-08-21 00:42:50 +02:00
rhash = callPackage ../tools/security/rhash { };
New pkg: riemann-c-client version 1.1.1 A C client library for the Riemann monitoring system
2014-07-07 18:05:30 +02:00
riemann_c_client = callPackage ../tools/misc/riemann-c-client { };
Add ripmime - MIME attachment extractor tool svn path=/nixpkgs/trunk/; revision=24337
2010-10-18 11:43:17 +02:00
ripmime = callPackage ../tools/networking/ripmime {};
Adding rkflashtool, to flash MK802IV.
2014-05-14 09:59:36 +02:00
rkflashtool = callPackage ../tools/misc/rkflashtool { };
Add rmlint, a tool for removing duplicate files
2013-06-09 20:34:50 +02:00
rmlint = callPackage ../tools/misc/rmlint {};
Add rng-tools
2012-11-22 07:05:45 +01:00
rng_tools = callPackage ../tools/security/rng-tools { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
rsnapshot = callPackage ../tools/backup/rsnapshot {
Add rsnapshot, an rsync-based remote backup tool. svn path=/nixpkgs/trunk/; revision=11009
2008-03-07 10:33:51 +01:00
# For the `logger' command, we can use either `utillinux' or
# GNU Inetutils. The latter is more portable.
logger = inetutils;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rlwrap = callPackage ../tools/misc/rlwrap { };
Added rlwrap - readline wrapper svn path=/nixpkgs/trunk/; revision=10271
2008-01-24 00:39:06 +01:00
Adding rockbox-utility, for installing/updating the rockbox firmware on mp3 players svn path=/nixpkgs/trunk/; revision=26817
2011-04-13 10:38:13 +02:00
rockbox_utility = callPackage ../tools/misc/rockbox-utility { };
Adding ppp and rp-pppoe for different point-to-point connectivity situations. Not tested for trivial reasons, but built OK svn path=/nixpkgs/trunk/; revision=13925
2009-02-01 14:54:20 +01:00
rpPPPoE = builderDefsPackage (import ../tools/networking/rp-pppoe) {
inherit ppp;
};
Move all db4 packages to the default db5
2014-01-31 21:05:37 +01:00
rpm = callPackage ../tools/package-management/rpm { };
* Revived RPM. Damn, RPM is nasty to build. svn path=/nixpkgs/trunk/; revision=8407
2007-03-21 20:25:58 +01:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
rrdtool = callPackage ../tools/misc/rrdtool { };
Adding rrdtool. svn path=/nixpkgs/trunk/; revision=14713
2009-03-25 20:13:24 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rtorrent = callPackage ../tools/networking/p2p/rtorrent { };
Added libtorrent a bittorent library written in C++ for *nix and rtorrent a ncurses client for libtorrent. svn path=/nixpkgs/trunk/; revision=10842
2008-02-23 13:11:27 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rubber = callPackage ../tools/typesetting/rubber { };
Add Rubber, a LaTeX wrapper that does the right thing. svn path=/nixpkgs/trunk/; revision=14551
2009-03-16 11:42:51 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rxp = callPackage ../tools/text/xml/rxp { };
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rzip = callPackage ../tools/compression/rzip { };
Adding lrzip and rzip. svn path=/nixpkgs/trunk/; revision=14581
2009-03-17 22:17:51 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
s3backer = callPackage ../tools/filesystems/s3backer { };
* Added s3backer. svn path=/nixpkgs/trunk/; revision=18811
2009-12-04 16:51:02 +01:00
* Added s3cmd. svn path=/nixpkgs/trunk/; revision=28530
2011-08-13 13:49:23 +02:00
s3cmd = callPackage ../tools/networking/s3cmd { };
Mark s3cmd-1.5-pre-81e3842f7a as low priority.
2014-06-02 12:04:24 +02:00
s3cmd_15_pre_81e3842f7a = lowPrio (callPackage ../tools/networking/s3cmd/git.nix { });
Supplementary derivation for s3cmd, building from git HEAD.
2014-06-02 10:08:36 +02:00
s3sync: Require Ruby 1.8
2012-07-28 00:36:10 +02:00
s3sync = callPackage ../tools/networking/s3sync {
ruby = ruby18;
};
* Added s3sync. svn path=/nixpkgs/trunk/; revision=20496
2010-03-09 16:12:15 +01:00
s6-dns: new package s6-dns is a suite of DNS client programs and libraries for Unix systems, as an alternative to the BIND, djbdns or other DNS clients.
2014-08-30 07:06:42 +02:00
s6Dns = callPackage ../tools/networking/s6-dns { };
s6-linux-utils: new package s6-linux-utils is a set of minimalistic Linux-specific system utilities.
2014-08-30 07:12:38 +02:00
s6LinuxUtils = callPackage ../os-specific/linux/s6-linux-utils { };
s6-networking: new package s6-networking is a suite of small networking utilities for Unix systems including UCSPI Unix and TCP tools, access control tools, and network time management utilities.
2014-08-30 07:07:45 +02:00
s6Networking = callPackage ../tools/networking/s6-networking { };
s6-portable-utils: new package s6-portable-utils is a set of tiny general Unix utilities, often performing well-known tasks such as cut and grep, but optimized for simplicity and small size.
2014-08-30 07:05:23 +02:00
s6PortableUtils = callPackage ../tools/misc/s6-portable-utils { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sablotron = callPackage ../tools/text/xml/sablotron { };
* Added BitTorrent. svn path=/nixpkgs/trunk/; revision=797
2004-02-17 21:03:12 +01:00
add package: "safecopy-1.7"
2012-11-17 20:14:55 +01:00
safecopy = callPackage ../tools/system/safecopy { };
Buildable Salut-à-toi
2012-09-13 12:14:49 +02:00
salut_a_toi = callPackage ../applications/networking/instant-messengers/salut-a-toi {};
samplicator: New package, version 1.3.7-beta6. A small and lightweight UDP redirector if you don't want to bend a fly on the wheel using socat. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-12 06:57:28 +01:00
samplicator = callPackage ../tools/networking/samplicator { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
screen = callPackage ../tools/misc/screen { };
* JDK: put the machine-dependent header files in the right place. * Added SWT for GTK (built from source). * Added Azureus (a Bittorrent client written in Java). svn path=/nixpkgs/trunk/; revision=4438
2005-12-26 01:51:24 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
scrot = callPackage ../tools/graphics/scrot { };
* Added scrot, a command-line screen capture utility. svn path=/nixpkgs/trunk/; revision=16946
2009-09-03 00:56:33 +02:00
scrypt: New package
2013-09-03 03:49:08 +02:00
scrypt = callPackage ../tools/security/scrypt { };
sdcv: add expression
2013-06-02 03:21:30 +02:00
sdcv = callPackage ../applications/misc/sdcv { };
sec: add version 2.7.5
2014-07-12 13:19:08 +02:00
sec = callPackage ../tools/admin/sec { };
pkgs/tools/security/seccure: store the expression in a file called "default.nix"
2013-10-03 16:19:57 +02:00
seccure = callPackage ../tools/security/seccure { };
Added Shamir Secret Sharing Scheme and bmrsa. Fixed libgcrypt svn path=/nixpkgs/trunk/; revision=10928
2008-03-03 13:30:39 +01:00
Adding setserial svn path=/nixpkgs/trunk/; revision=15898
2009-06-09 06:22:46 +02:00
setserial = builderDefsPackage (import ../tools/system/setserial) {
inherit groff;
};
seqdiag: new package Seqdiag generates sequence-diagram image from spec-text file (similar to Graphviz).
2013-09-21 19:19:42 +02:00
seqdiag = pythonPackages.seqdiag;
add screenfetch Signed-off-by: Ricky Elrod <ricky@elrod.me>
2014-05-27 13:11:34 +02:00
screenfetch = callPackage ../tools/misc/screenfetch { };
Add sg3_utils svn path=/nixpkgs/trunk/; revision=23949
2010-09-26 21:39:42 +02:00
sg3_utils = callPackage ../tools/system/sg3_utils { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sharutils = callPackage ../tools/archivers/sharutils { };
all-packages.nix: drop trailing whitespace
2014-04-11 10:06:06 +02:00
Add shotwell 1.15.1
2013-07-14 15:14:37 +02:00
shotwell = callPackage ../applications/graphics/shotwell { };
sharutils added (4.6.3) svn path=/nixpkgs/branches/stdenv-updates/; revision=10744
2008-02-18 21:52:25 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
shebangfix = callPackage ../tools/misc/shebangfix { };
added small script fixing the shebang (#!/bin/...) path. It searches the PATH env variable for the same executable. svn path=/nixpkgs/trunk/; revision=9667
2007-11-14 20:07:38 +01:00
Add shellinabox
2013-12-07 06:13:35 +01:00
shellinabox = callPackage ../servers/shellinabox { };
Adding siege HTTP load tester svn path=/nixpkgs/trunk/; revision=27368
2011-06-07 18:15:05 +02:00
siege = callPackage ../tools/networking/siege {};
Adding silc-client as irssi plugin Alone, with its own irssi, doesn't build.
2013-04-12 21:10:44 +02:00
silc_client = callPackage ../applications/networking/instant-messengers/silc-client { };
silc_server = callPackage ../servers/silc-server { };
silver-search: Add
2014-01-19 13:24:32 +01:00
silver-searcher = callPackage ../tools/text/silver-searcher { };
Add simplescreenrecorder: an excellent screen recorder for linux
2014-03-26 23:02:15 +01:00
simplescreenrecorder = callPackage ../applications/video/simplescreenrecorder { };
Adding The Sleuth Kit svn path=/nixpkgs/trunk/; revision=28130
2011-08-02 22:06:09 +02:00
sleuthkit = callPackage ../tools/system/sleuthkit {};
all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28136
2011-08-03 10:43:56 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
slimrat = callPackage ../tools/networking/slimrat {
Adding slimrat (not the gui, but at least the cli) svn path=/nixpkgs/trunk/; revision=20999
2010-04-10 12:47:30 +02:00
inherit (perlPackages) WWWMechanize LWP;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
slsnif = callPackage ../tools/misc/slsnif { };
slsnif-0.4.4 added svn path=/nixpkgs/trunk/; revision=12679
2008-08-21 13:07:29 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
smartmontools = callPackage ../tools/system/smartmontools { };
* Added smartmontools. svn path=/nixpkgs/trunk/; revision=9466
2007-10-18 15:05:43 +02:00
Adding smbldap-tools. And some CPAN packages as bonus. svn path=/nixpkgs/trunk/; revision=31118
2011-12-27 22:35:50 +01:00
smbldaptools = callPackage ../tools/networking/smbldaptools {
inherit (perlPackages) NetLDAP CryptSmbHash DigestSHA1;
};
Adding SMBNetFS svn path=/nixpkgs/trunk/; revision=26030
2011-02-19 10:56:35 +01:00
smbnetfs = callPackage ../tools/filesystems/smbnetfs {};
* Added smartmontools. svn path=/nixpkgs/trunk/; revision=9466
2007-10-18 15:05:43 +02:00
Add snort-2.9.4.6
2013-05-30 15:05:39 +02:00
snort = callPackage ../applications/networking/ids/snort { };
snx: add version 800007027 of the CheckPoint SSL Network Extender
2013-02-21 15:56:09 +01:00
snx = callPackage_i686 ../tools/networking/snx {
inherit (pkgsi686Linux) pam gcc33;
inherit (pkgsi686Linux.xlibs) libX11;
};
New package: solr 4.7.0, a Java search platform
2014-03-12 23:07:38 +01:00
solr = callPackage ../servers/search/solr { };
add sparsehash-2.0.2
2014-01-01 20:11:11 +01:00
sparsehash = callPackage ../development/libraries/sparsehash { };
spiped: version 1.3.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-06 08:46:28 +02:00
spiped = callPackage ../tools/networking/spiped { };
Add sproxy
2014-04-06 16:54:44 +02:00
sproxy = haskellPackages.callPackage ../tools/networking/sproxy { };
Add sproxy-web
2014-04-06 17:10:01 +02:00
sproxy-web = haskellPackages.callPackage ../tools/networking/sproxy-web { };
all-packages.nix: fixed path to stardict expression svn path=/nixpkgs/trunk/; revision=34540
2012-06-18 11:52:30 +02:00
stardict = callPackage ../applications/misc/stardict/stardict.nix {
inherit (gnome) libgnomeui scrollkeeper;
StarDict is a Cross-Platform and international dictionary Software. Now it is available on NixOS. See https://nixos.org/wiki/Solve_GConf_errors_when_running_GNOME_applications if you want to get it running. svn path=/nixpkgs/trunk/; revision=34531
2012-06-17 20:41:00 +02:00
};
Adding storebrowse, a tool to browse the nix store with a web browser. The build script is a bit long due to the upstream go style of things.
2013-03-16 00:58:35 +01:00
storebrowse = callPackage ../tools/system/storebrowse { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fusesmb = callPackage ../tools/filesystems/fusesmb { };
Added smbfsFuse (executable name fusesmb) svn path=/nixpkgs/trunk/; revision=10285
2008-01-25 11:15:19 +01:00
Adding Steam Locomotive, for the fun
2013-03-25 14:56:45 +01:00
sl = callPackage ../tools/misc/sl { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
socat = callPackage ../tools/networking/socat { };
Added socat, updated zsh svn path=/nixpkgs/trunk/; revision=10470
2008-02-03 12:03:54 +01:00
socate: Update to 1.7.2.2, 2.0.0-b6 CVE-2013-3571
2013-11-04 19:27:57 +01:00
socat2pre = lowPrio (callPackage ../tools/networking/socat/2.x.nix { });
source-highlight: unbreak by using boost 1.53 One of the tests started failing when boost was bumped from 1.53 to 1.54 (in July). Instead of skipping the tests, fix it by using boost 1.53.
2013-09-04 19:49:09 +02:00
sourceHighlight = callPackage ../tools/text/source-highlight {
# Boost 1.54 causes the "test_regexranges" test to fail
boost: Remove 1.53 and 1.54 These don't build against Glibc 2.18, but they're not used anyway (except by source-highlight, which builds fine against 1.49).
2013-12-10 12:02:53 +01:00
boost = boost149;
source-highlight: unbreak by using boost 1.53 One of the tests started failing when boost was bumped from 1.53 to 1.54 (in July). Instead of skipping the tests, fix it by using boost 1.53.
2013-09-04 19:49:09 +02:00
};
pkgs/tools/text/source-highlight: added GNU source highlight version 3.1.3 svn path=/nixpkgs/trunk/; revision=21457
2010-04-30 14:23:26 +02:00
spaceFM: add package
2014-01-11 14:38:06 +01:00
spaceFM = callPackage ../applications/misc/spacefm { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
squashfsTools = callPackage ../tools/filesystems/squashfs { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sshfsFuse = callPackage ../tools/filesystems/sshfs-fuse { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
add sshuttle: Transparent proxy server that works as a poor man's VPN
2013-10-05 16:45:51 +02:00
sshuttle = callPackage ../tools/security/sshuttle { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sudo = callPackage ../tools/security/sudo { };
Added sudo. svn path=/nixpkgs/trunk/; revision=8898
2007-06-20 01:55:02 +02:00
* Added super. svn path=/nixpkgs/trunk/; revision=28739
2011-08-22 17:24:24 +02:00
suidChroot = builderDefsPackage (import ../tools/system/suid-chroot) { };
super = callPackage ../tools/security/super { };
Added setuid-ready chroot utility. svn path=/nixpkgs/trunk/; revision=16331
2009-07-12 10:10:51 +02:00
ssdeep: version 2.10 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-20 19:18:51 +01:00
ssdeep = callPackage ../tools/security/ssdeep { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
ssmtp = callPackage ../tools/networking/ssmtp {
* Build ssmtp with TLS support. * Added gnutls (but it turns out that ssmtp also builds with openssl, so I don't actually use it). svn path=/nixpkgs/trunk/; revision=9604
2007-11-08 18:48:52 +01:00
tlsSupport = true;
* add ssmtp still rather rough around the edges: - example config files are installed to $out/etc/ssmtp - the binary expects config files in /etc/ssmtp - it's the user's responsibility to add the global config files svn path=/nixpkgs/trunk/; revision=9064
2007-08-08 00:22:31 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ssss = callPackage ../tools/security/ssss { };
Added Shamir Secret Sharing Scheme and bmrsa. Fixed libgcrypt svn path=/nixpkgs/trunk/; revision=10928
2008-03-03 13:30:39 +01:00
adding store-backup
2013-08-31 22:16:22 +02:00
storeBackup = callPackage ../tools/backup/store-backup { };
GNU Stow: package - Symlink manager which makes it easy to manage dotfiles
2013-09-05 12:03:02 +02:00
stow = callPackage ../tools/misc/stow { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
stun = callPackage ../tools/networking/stun { };
adding stun svn path=/nixpkgs/trunk/; revision=17860
2009-10-18 06:43:45 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
stunnel = callPackage ../tools/networking/stunnel { };
add stunnel svn path=/nixpkgs/trunk/; revision=14301
2009-03-02 16:23:52 +01:00
su: Make the su package a provider of only the su binary Additionally, provide su with the base system and remove su from the util-linux package as it is now provided by shadow.
2014-04-05 20:41:23 +02:00
su = shadow.su;
* Add a working PAM-enabled su. svn path=/nixpkgs/trunk/; revision=7633
2007-01-11 16:22:59 +01:00
Add surfraw 2.2.8
2012-08-31 10:55:23 +02:00
surfraw = callPackage ../tools/networking/surfraw { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
swec = callPackage ../tools/networking/swec {
Add SWEC (Simple Web Error Checker). svn path=/nixpkgs/trunk/; revision=19637
2010-01-24 20:07:16 +01:00
inherit (perlPackages) LWP URI HTMLParser HTTPServerSimple Parent;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
svnfs = callPackage ../tools/filesystems/svnfs { };
adding svnFS svn path=/nixpkgs/trunk/; revision=21132
2010-04-16 17:56:31 +02:00
Added sysbench 0.4.12
2012-10-26 14:45:16 +02:00
sysbench = callPackage ../development/tools/misc/sysbench {};
system-config-printer: fix runtime errors. Patch by Karn Kallio. svn path=/nixpkgs/trunk/; revision=24899
2010-11-28 10:46:51 +01:00
system_config_printer = callPackage ../tools/misc/system-config-printer {
libxml2 = libxml2Python;
};
Use $NIXPKGS_CONFIG to determine whether ghostscript has cups support. svn path=/nixpkgs/trunk/; revision=14275
2009-02-27 14:44:31 +01:00
* Make sitecopy build against Neon 0.29. svn path=/nixpkgs/trunk/; revision=23461
2010-08-26 15:09:52 +02:00
sitecopy = callPackage ../tools/networking/sitecopy { };
added sitecopy svn path=/nixpkgs/trunk/; revision=17638
2009-10-05 12:37:30 +02:00
nixpkgs: stricat 20140609100300 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-08-21 07:22:42 +02:00
stricat = callPackage ../tools/security/stricat { };
privoxy: update the build script, add documentation dependency
2013-12-04 03:41:25 +01:00
privoxy = callPackage ../tools/networking/privoxy { };
added privoxy svn path=/nixpkgs/trunk/; revision=17645
2009-10-05 16:15:28 +02:00
t1utils: new package t1utils is a collection of simple Type 1 font manipulation programs.
2014-06-11 19:29:34 +02:00
t1utils = callPackage ../tools/misc/t1utils { };
Add tarsnap package.
2012-10-21 03:03:13 +02:00
tarsnap = callPackage ../tools/backup/tarsnap { };
tcpcrypt: add current HEAD of the Github master branch
2013-09-09 12:56:22 +02:00
tcpcrypt = callPackage ../tools/security/tcpcrypt { };
Added trousers, tpm-tools, and tboot. Added lcp_writepol -Z option.
2013-08-14 08:16:52 +02:00
tboot = callPackage ../tools/security/tboot { };
add game 'tcl2048'
2014-08-31 10:48:51 +02:00
tcl2048 = callPackage ../games/tcl2048 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tcpdump = callPackage ../tools/networking/tcpdump { };
all-packages.nix: drop trailing whitespace
2014-04-11 10:06:06 +02:00
Adding TCPFlow: a tool to separate tcp streams when capturing
2014-04-11 09:08:22 +02:00
tcpflow = callPackage ../tools/networking/tcpflow { };
* Added tcpdump. svn path=/nixpkgs/trunk/; revision=7697
2007-01-16 15:35:08 +01:00
Fixing the teamviewer evaluation and builds. Now tested even the tarball, before committing.
2013-03-22 16:16:10 +01:00
teamviewer = callPackage_i686 ../applications/networking/remote/teamviewer { };
teamviewer: adding a work-in-progress lowprio version 8. It requires root running a daemon, just to use the client. Suspicious.
2013-03-22 12:41:16 +01:00
# Work In Progress: it doesn't start unless running a daemon as root
Fixing the teamviewer evaluation and builds. Now tested even the tarball, before committing.
2013-03-22 16:16:10 +01:00
teamviewer8 = lowPrio (callPackage_i686 ../applications/networking/remote/teamviewer/8.nix { });
Adding teamviewer client for linux (www.teamviewer.com) In fact it uses wine.
2013-03-22 12:10:02 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
telnet = callPackage ../tools/networking/telnet { };
* Added a telnet client. svn path=/nixpkgs/trunk/; revision=9431
2007-10-09 11:56:39 +02:00
Merging roconnor's and ludo' texmacs derivations. texmacs now has extra font options. texmacs is abstracted over which tex it uses (AFAIK texmacs only uses metafont). texmacs now depends on aspell, ghostscript soft dependencies. svn path=/nixpkgs/trunk/; revision=24054
2010-10-04 17:07:38 +02:00
texmacs = callPackage ../applications/editors/texmacs {
tex = texLive; /* tetex is also an option */
extraFonts = true;
Prepare for the Guile 2.0 switchover. svn path=/nixpkgs/trunk/; revision=25976
2011-02-15 14:14:29 +01:00
guile = guile_1_8;
Merging roconnor's and ludo' texmacs derivations. texmacs now has extra font options. texmacs is abstracted over which tex it uses (AFAIK texmacs only uses metafont). texmacs now depends on aspell, ghostscript soft dependencies. svn path=/nixpkgs/trunk/; revision=24054
2010-10-04 17:07:38 +02:00
};
Add GNU TeXmacs. svn path=/nixpkgs/trunk/; revision=19985
2010-02-13 20:22:16 +01:00
Added TeXmaker package : an advanced editor for latex
2014-04-24 10:54:09 +02:00
texmaker = callPackage ../applications/editors/texmaker { };
Cleaning up the description and fixing qt to qt4
2014-04-23 12:09:25 +02:00
texstudio = callPackage ../applications/editors/texstudio { };
Creation of a new package for texstudio, an editor for LaTeX documents
2014-04-22 23:26:27 +02:00
add tiled-qt 0.9.1
2013-08-14 03:23:15 +02:00
tiled-qt = callPackage ../applications/editors/tiled-qt { qt = qt4; };
tinc: A VPN daemon with full mesh routing.
2013-01-18 07:52:15 +01:00
tinc = callPackage ../tools/networking/tinc { };
tinc_pre: Add derivation The tinc developer has made significant developments to the next version of tinc including many protocol security fixes. This patch adds the prerelease of the next major tinc release.
2014-08-23 23:05:31 +02:00
tinc_pre = callPackage ../tools/networking/tinc/pre.nix { };
New package: 8086tiny, a tiny 8086 emulator
2014-02-24 04:01:43 +01:00
tiny8086 = callPackage ../applications/virtualization/8086tiny { };
tmpwatch: Add package.
2013-12-13 10:41:38 +01:00
tmpwatch = callPackage ../tools/misc/tmpwatch { };
added tmux svn path=/nixpkgs/trunk/; revision=24904
2010-11-28 13:38:35 +01:00
tmux = callPackage ../tools/misc/tmux { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tor = callPackage ../tools/security/tor { };
Adding tor 0.2.1.26 (Patch sent by roconnor) svn path=/nixpkgs/trunk/; revision=21797
2010-05-16 18:23:32 +02:00
torbutton: package version 1.6.1
2013-08-10 19:07:36 +02:00
torbutton = callPackage ../tools/security/torbutton { };
Add tor-browser
2014-01-12 23:04:14 +01:00
torbrowser = callPackage ../tools/security/tor/torbrowser.nix { };
New derivation for torsocks. This will replace tsocks. svn path=/nixpkgs/trunk/; revision=24011
2010-10-01 04:38:03 +02:00
torsocks = callPackage ../tools/security/tor/torsocks.nix { };
Added tpm-quote-tools for remote attestation.
2013-10-01 22:15:06 +02:00
tpm-quote-tools = callPackage ../tools/security/tpm-quote-tools { };
Added trousers, tpm-tools, and tboot. Added lcp_writepol -Z option.
2013-08-14 08:16:52 +02:00
tpm-tools = callPackage ../tools/security/tpm-tools { };
Add trickle 1.07
2012-07-16 12:06:31 +02:00
trickle = callPackage ../tools/networking/trickle {};
Added trousers, tpm-tools, and tboot. Added lcp_writepol -Z option.
2013-08-14 08:16:52 +02:00
trousers = callPackage ../tools/security/trousers { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ttf2pt1 = callPackage ../tools/misc/ttf2pt1 { };
* Removed applications/msic, a rather obvious typo. svn path=/nixpkgs/trunk/; revision=15149
2009-04-19 13:47:01 +02:00
Adding ttysnoop pty redirector
2013-10-20 16:42:53 +02:00
ttysnoop = callPackage ../os-specific/linux/ttysnoop {};
New package: Twitter Bootstrap 2.3.2, a front-end framework for web development.
2013-07-01 16:14:52 +02:00
twitterBootstrap = callPackage ../development/web/twitter-bootstrap {};
txt2man: new package txt2man converts flat ASCII text to man page format. (Solfege, which is added in the next commit, needs this.)
2013-06-06 19:00:04 +02:00
txt2man = callPackage ../tools/misc/txt2man { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ucl = callPackage ../development/libraries/ucl { };
Adding upx. svn path=/nixpkgs/trunk/; revision=14645
2009-03-22 14:03:37 +01:00
ucspi-tcp: new package ucspi-tcp is command-line tools for building TCP client-server applications. http://cr.yp.to/ucspi-tcp.html
2014-08-07 18:34:45 +02:00
ucspi-tcp = callPackage ../tools/networking/ucspi-tcp { };
Adding UDFtools svn path=/nixpkgs/trunk/; revision=25485
2011-01-10 12:04:20 +01:00
udftools = callPackage ../tools/filesystems/udftools {};
Adding udptunnel (Fixing a semicolon in pwnat expr too)
2013-05-08 22:50:54 +02:00
udptunnel = callPackage ../tools/networking/udptunnel { };
Make nixpkgs ready to gtkLibs attrset removal svn path=/nixpkgs/trunk/; revision=33091
2012-03-14 23:44:41 +01:00
ufraw = callPackage ../applications/graphics/ufraw { };
Add UFRaw. svn path=/nixpkgs/trunk/; revision=17881
2009-10-19 14:50:45 +02:00
* Added UNetbootin, a program for creating bootable USB sticks from ISO images. svn path=/nixpkgs/trunk/; revision=23018
2010-08-07 00:33:14 +02:00
unetbootin = callPackage ../tools/cd-dvd/unetbootin { };
Add UNFS3, a user-space NFSv3 server. svn path=/nixpkgs/trunk/; revision=32753
2012-03-03 17:06:27 +01:00
unfs3 = callPackage ../servers/unfs3 { };
unoconv: new package unoconv is a tool that converts between any document format supported by LibreOffice/OpenOffice. Example of how to convert an .odt file to .pdf: unoconv -f pdf some-file.odt Homepage: http://dag.wieers.com/home-made/unoconv/ Implementation notes: unoconv must use the same python version as libreoffice (unless it will not be able to load the pyuno module from libreoffice). And because we recently switched to libreoffice 4.x, which uses python3, I had to include unoconv-python3.patch. The patch comes from upstream unoconv.git repo, so it will be included in the next release.
2013-09-01 20:30:23 +02:00
unoconv = callPackage ../tools/text/unoconv { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
upx = callPackage ../tools/compression/upx { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=24045
2010-10-04 11:49:25 +02:00
Package urlview 0.9-19 urlview extracts URLs from text. Close #1118.
2013-10-25 18:56:40 +02:00
urlview = callPackage ../applications/misc/urlview {};
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=24045
2010-10-04 11:49:25 +02:00
Add usbmuxd svn path=/nixpkgs/trunk/; revision=23948
2010-09-26 21:39:35 +02:00
usbmuxd = callPackage ../tools/misc/usbmuxd {};
Add Vacuum IM svn path=/nixpkgs/trunk/; revision=23870
2010-09-20 10:40:30 +02:00
vacuum = callPackage ../applications/networking/instant-messengers/vacuum {};
Adding upx. svn path=/nixpkgs/trunk/; revision=14645
2009-03-22 14:03:37 +01:00
Add volatility: memory forensics framework
2014-07-10 20:34:23 +02:00
volatility = callPackage ../tools/security/volatility { };
Vidalia: packaged svn path=/nixpkgs/trunk/; revision=32694
2012-02-29 14:30:06 +01:00
vidalia = callPackage ../tools/security/vidalia { };
Adding vbetool svn path=/nixpkgs/trunk/; revision=17952
2009-10-24 21:58:07 +02:00
vbetool = builderDefsPackage ../tools/system/vbetool {
inherit pciutils libx86 zlib;
};
* Added vde2 (Virtual Distributed Ethernet). svn path=/nixpkgs/trunk/; revision=25518
2011-01-12 14:39:17 +01:00
vde2 = callPackage ../tools/networking/vde2 { };
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
Add vboot_reference: tools needed for installing custom OS on Chromebooks
2013-05-27 12:10:19 +02:00
vboot_reference = callPackage ../tools/system/vboot_reference { };
updates: mr, vcsh and transmission-remote-gtk - mr: copy some more stuff to output - add vcsh package - transmission-remote-gtk: 1.0.1 -> 1.1.1
2014-02-06 01:53:55 +01:00
vcsh = callPackage ../applications/version-management/vcsh { };
Committing patch adding verilog from Antonio Vargas Gonzalez From his original, I adapted some spacing, and removed the release.nix reference (superfluous having set meta.platforms) svn path=/nixpkgs/trunk/; revision=24860
2010-11-25 23:01:14 +01:00
verilog = callPackage ../applications/science/electronics/verilog {};
added vfdecrypt svn path=/nixpkgs/trunk/; revision=25666
2011-01-22 13:14:25 +01:00
vfdecrypt = callPackage ../tools/misc/vfdecrypt { };
callPackage automatically inherits from xlibs
2013-08-10 13:00:43 +02:00
vifm = callPackage ../applications/misc/vifm { };
Adding vifm file manager svn path=/nixpkgs/trunk/; revision=28466
2011-08-10 21:16:27 +02:00
viking: Update to 1.3.
2012-07-01 17:32:03 +02:00
viking = callPackage ../applications/misc/viking {
inherit (gnome) scrollkeeper;
};
Add Viking, a GPS trace editor. svn path=/nixpkgs/trunk/; revision=15804
2009-05-30 22:52:10 +02:00
Move namePrefix="" python packages out of python-packges.nix It doesn't make sense to build tools/applications with three different python interpreter versions, so move them out of python modules list. Also reverts 53ffc6e0ef395a2bd7651423d9783ad8184be1d0.
2013-07-31 13:32:25 +02:00
vnc2flv = callPackage ../tools/video/vnc2flv {};
Adding vncrec - a VNC recorder svn path=/nixpkgs/trunk/; revision=16603
2009-08-07 14:00:00 +02:00
vncrec = builderDefsPackage ../tools/video/vncrec {
inherit (xlibs) imake libX11 xproto gccmakedep libXt
libXmu libXaw libXext xextproto libSM libICE libXpm
libXp;
};
added vobcopy: nice CLI dvd ripper svn path=/nixpkgs/trunk/; revision=34466
2012-06-11 19:40:58 +02:00
vobcopy = callPackage ../tools/cd-dvd/vobcopy { };
Add vobsub2srt-git-20140226-b70b6f5
2013-12-29 04:16:41 +01:00
vobsub2srt = callPackage ../tools/cd-dvd/vobsub2srt { };
Add vorbisgain - replaygain for ogg/vorbis svn path=/nixpkgs/trunk/; revision=26176
2011-03-06 17:07:37 +01:00
vorbisgain = callPackage ../tools/misc/vorbisgain { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vpnc = callPackage ../tools/networking/vpnc { };
Add VPNC, a Cisco-compatible VPN client. svn path=/nixpkgs/trunk/; revision=10618
2008-02-10 22:54:01 +01:00
Added openconnect
2013-05-31 20:19:56 +02:00
openconnect = callPackage ../tools/networking/openconnect.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vtun = callPackage ../tools/networking/vtun { };
Adding vtun. svn path=/nixpkgs/trunk/; revision=15682
2009-05-20 19:51:41 +02:00
New package: wal-e A Postgres WAL-shipping disaster recovery and replication toolkit
2014-03-30 04:26:24 +02:00
wal_e = callPackage ../tools/backup/wal-e { };
watchman: new package This adds `watchman`, a CLI utility that watches files and takes action when they change.
2014-07-05 22:34:51 +02:00
watchman = callPackage ../development/tools/watchman { };
wbox: New package, version 5. Yet another HTTP benchmarking tool, which is really quite minimalistic and in ANSI C. This package maybe isn't even worth putting it in its own file and directory but I did it for the sake of consistency. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-12 06:35:29 +01:00
wbox = callPackage ../tools/networking/wbox {};
Adding Welkin RDF visualizer svn path=/nixpkgs/trunk/; revision=27567
2011-07-01 09:26:38 +02:00
welkin = callPackage ../tools/graphics/welkin {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
testdisk = callPackage ../tools/misc/testdisk { };
* Added TestDisk, a program for fixing unbootable disks. svn path=/nixpkgs/trunk/; revision=9318
2007-09-12 17:49:28 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
htmlTidy = callPackage ../tools/text/html-tidy { };
Add HTML Tidy, an HTML validator. svn path=/nixpkgs/trunk/; revision=16176
2009-07-05 16:07:39 +02:00
Add htm-xml-utils Signed-off-by: Shea Levy <shea@shealevy.com>
2013-10-17 20:11:15 +02:00
html-xml-utils = callPackage ../tools/text/xml/html-xml-utils { };
Adding TFTP-HPA svn path=/nixpkgs/trunk/; revision=28915
2011-08-30 09:02:01 +02:00
tftp_hpa = callPackage ../tools/networking/tftp-hpa {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
tigervnc = callPackage ../tools/admin/tigervnc {
Making the tigervnc server work. svn path=/nixpkgs/trunk/; revision=22584
2010-07-13 19:57:13 +02:00
fontDirectories = [ xorg.fontadobe75dpi xorg.fontmiscmisc xorg.fontcursormisc
xorg.fontbhlucidatypewriter75dpi ];
remove old references to xorgserver_1_13_0
2013-04-24 08:44:43 +02:00
inherit (xorg) xorgserver;
Update TigerVNC to SVN checkout that at least builds..
2012-10-18 18:49:22 +02:00
fltk = fltk13;
TigerVNC (without the server Xvnc still) svn path=/nixpkgs/trunk/; revision=22568
2010-07-13 00:15:36 +02:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
tightvnc = callPackage ../tools/admin/tightvnc {
Making tightvnc use given fonts, instead of depending of an X Font Server started at the usual unix socket. svn path=/nixpkgs/trunk/; revision=15624
2009-05-17 01:04:06 +02:00
fontDirectories = [ xorg.fontadobe75dpi xorg.fontmiscmisc xorg.fontcursormisc
xorg.fontbhlucidatypewriter75dpi ];
* Added gtk-gnutella. * Added a patch to MPlayer to fix the aspect ratio on screens rotated with Xrandr. * Disable toolbus for now because it requires a non-existant package (tcltk). svn path=/nixpkgs/trunk/; revision=5171
2006-04-18 20:46:36 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
time = callPackage ../tools/misc/time { };
* Added the GNU `time' command. svn path=/nixpkgs/trunk/; revision=8599
2007-04-20 10:50:26 +02:00
Add tkabber v0.11.1.
2012-06-04 20:28:40 +02:00
tkabber = callPackage ../applications/networking/instant-messengers/tkabber { };
qfsm: add version 0.53.0
2012-11-11 20:32:41 +01:00
qfsm = callPackage ../applications/science/electronics/qfsm { };
tkgate: add versions 1.8.7 and 2.0-b10
2012-11-08 17:30:44 +01:00
tkgate = callPackage ../applications/science/electronics/tkgate/1.x.nix {
inherit (xlibs) libX11 imake xproto gccmakedep;
};
# The newer package is low-priority because it segfaults at startup.
tkgate2 = lowPrio (callPackage ../applications/science/electronics/tkgate/2.x.nix {
inherit (xlibs) libX11;
});
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tm = callPackage ../tools/system/tm { };
tm (terminal mixer), ts (task spooler) added, provided by viric svn path=/nixpkgs/trunk/; revision=12688
2008-08-21 23:35:14 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
trang = callPackage ../tools/text/xml/trang { };
add groff, needed for dhcp svn path=/nixpkgs/trunk/; revision=3651
2005-08-21 15:59:04 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tre = callPackage ../development/libraries/tre { };
added tre-0.8.0 svn path=/nixpkgs/trunk/; revision=19873
2010-02-09 10:09:25 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ts = callPackage ../tools/system/ts { };
tm (terminal mixer), ts (task spooler) added, provided by viric svn path=/nixpkgs/trunk/; revision=12688
2008-08-21 23:35:14 +02:00
transfig: Keep using libpng 1.2. svn path=/nixpkgs/trunk/; revision=32791
2012-03-05 10:40:36 +01:00
transfig = callPackage ../tools/graphics/transfig {
libpng = libpng12;
};
add a wrapper for dhclient svn path=/nixpkgs/trunk/; revision=3655
2005-08-21 21:46:16 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
truecrypt = callPackage ../applications/misc/truecrypt {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
wxGUI = config.truecrypt.wxGUI or true;
truecrypt svn path=/nixpkgs/trunk/; revision=12389
2008-07-19 18:14:24 +02:00
};
Making the current versions of flex/bison the default. Evaluation test passes. Please explicitly pass older versions to any package that can be adversely affected by too-fresh versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=25086
2010-12-12 22:48:29 +01:00
ttmkfdir = callPackage ../tools/misc/ttmkfdir { };
Added template to use deb-package wrapper. svn path=/nixpkgs/trunk/; revision=10911
2008-03-02 19:41:32 +01:00
uim, gtk-exe-env, qt-plugin-env: Add input method modules for GTK+ and Qt
2014-07-13 08:46:34 +02:00
uim = callPackage ../tools/inputmethods/uim {
inherit (pkgs.kde4) kdelibs;
};
uhub: initial package for version 0.4.1
2014-07-18 19:02:53 +02:00
uhub = callPackage ../servers/uhub { };
unclutter: X cursor management tool Unclutter hides your X mouse cursor when you do not need it, to prevent it from getting in the way. You have only to move the mouse to restore the mouse cursor. Unclutter is very usefull in tiling wm's where you do not need the mouse often. Just run it from your .bash_profile like that: unclutter -idle 1 & svn path=/nixpkgs/trunk/; revision=31431
2012-01-08 15:01:17 +01:00
unclutter = callPackage ../tools/misc/unclutter { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
unbound = callPackage ../tools/networking/unbound { };
unbound 1.4.1 svn path=/nixpkgs/trunk/; revision=19870
2010-02-09 08:28:32 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
units = callPackage ../tools/misc/units { };
Added GNU units - unit conversion tool. svn path=/nixpkgs/trunk/; revision=8907
2007-06-20 17:15:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
unrar = callPackage ../tools/archivers/unrar { };
Added unrar svn path=/nixpkgs/trunk/; revision=8916
2007-06-24 17:34:44 +02:00
Add xar
2014-08-30 23:22:51 +02:00
xar = callPackage ../tools/compression/xar { };
xarchive: add gtk archiver
2013-05-05 22:02:48 +02:00
xarchive = callPackage ../tools/archivers/xarchive { };
add xarchiver: GTK+2 only frontend to 7z,zip,rar,tar,bzip2, gzip,arj, lha, rpm and deb (open and extract only)
2014-02-21 13:18:56 +01:00
xarchiver = callPackage ../tools/archivers/xarchiver { };
xscruiser: initial package expression http://xcruiser.sourceforge.net/
2014-08-05 14:50:24 +02:00
xcruiser = callPackage ../applications/misc/xcruiser { };
Adding unarj svn path=/nixpkgs/trunk/; revision=24430
2010-10-23 16:55:14 +02:00
unarj = callPackage ../tools/archivers/unarj { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
unshield = callPackage ../tools/archivers/unshield { };
* Added unshield, a program for unpacking InstallShield CAB files (which are different from Windows Installer CAB files). svn path=/nixpkgs/trunk/; revision=8797
2007-05-28 19:09:30 +02:00
Remove unzip 5.52, make unzip 6.0 default As per TODO in all-packages.nix comments svn path=/nixpkgs/branches/stdenv-updates/; revision=28101
2011-08-01 06:53:21 +02:00
unzip = callPackage ../tools/archivers/unzip { };
* Unzip 6.0. svn path=/nixpkgs/trunk/; revision=17687
2009-10-07 13:18:54 +02:00
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
unzipNLS = lowPrio (unzip.override { enableNLS = true; });
zip, unzip: add NLS support svn path=/nixpkgs/trunk/; revision=31961
2012-02-01 23:32:16 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
uptimed = callPackage ../tools/system/uptimed { };
* added uptimed 0.3.16 svn path=/nixpkgs/trunk/; revision=17172
2009-09-16 09:31:16 +02:00
urlwatch: add version 1.16
2014-07-29 22:13:47 +02:00
urlwatch = callPackage ../tools/networking/urlwatch { };
adding varnish
2013-04-01 01:24:56 +02:00
varnish = callPackage ../servers/varnish { };
varnish: adding version 2.1.x
2013-11-02 01:45:27 +01:00
varnish2 = callPackage ../servers/varnish/2.1.nix { };
venus: new package
2013-07-23 22:40:36 +02:00
venus = callPackage ../tools/misc/venus {
python = python27;
};
* Added vlan, which provides the vconfig command. svn path=/nixpkgs/branches/modular-python/; revision=26624
2011-03-31 13:10:00 +02:00
vlan = callPackage ../tools/networking/vlan { };
Adding 'wakelan', to use UDP wake on lan on ethernet. svn path=/nixpkgs/trunk/; revision=26912
2011-04-20 22:55:46 +02:00
wakelan = callPackage ../tools/networking/wakelan { };
Adding wavemon svn path=/nixpkgs/trunk/; revision=27557
2011-06-29 11:53:35 +02:00
wavemon = callPackage ../tools/networking/wavemon { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
w3cCSSValidator = callPackage ../tools/misc/w3c-css-validator {
adding w3c CSS validator svn path=/nixpkgs/trunk/; revision=19635
2010-01-24 16:39:42 +01:00
tomcat = tomcat6;
};
Update fuse and make wdfs build with the latest neon. neon026 does not build with the current SSL. We should either remove neon026 or fix it. svn path=/nixpkgs/trunk/; revision=23505
2010-08-29 14:27:41 +02:00
wdfs = callPackage ../tools/filesystems/wdfs { };
new: wdfs-1.4.2 is a user-space file system that allows mounting a webdav share svn path=/nixpkgs/trunk/; revision=12316
2008-07-08 01:24:48 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wdiff = callPackage ../tools/text/wdiff { };
* Added GNU wdiff. svn path=/nixpkgs/trunk/; revision=20817
2010-03-25 12:51:55 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
webalizer = callPackage ../tools/networking/webalizer { };
nix 0.15pre20231 as nixUnstable svn path=/nixpkgs/trunk/; revision=20243
2010-02-25 11:01:33 +01:00
Adding WebDruid log analyzer. In the same time, reworking source autoupdate system a bit svn path=/nixpkgs/trunk/; revision=16859
2009-08-26 13:13:36 +02:00
webdruid = builderDefsPackage ../tools/admin/webdruid {
xlock: fixed build and updated to version 5.24 svn path=/nixpkgs/trunk/; revision=17356
2009-09-22 22:16:38 +02:00
inherit zlib libpng freetype gd which
Adding WebDruid log analyzer. In the same time, reworking source autoupdate system a bit svn path=/nixpkgs/trunk/; revision=16859
2009-08-26 13:13:36 +02:00
libxml2 geoip;
};
Add weighttp 0.3
2013-03-29 15:04:59 +01:00
weighttp = callPackage ../tools/networking/weighttp { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
wget = callPackage ../tools/networking/wget {
GNU wget: Fix test suite runs. svn path=/nixpkgs/trunk/; revision=21057
2010-04-13 12:11:42 +02:00
inherit (perlPackages) LWP;
Added transfig, opefully the ugliest package of this world svn path=/nixpkgs/trunk/; revision=5751
2006-07-17 22:35:02 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
which = callPackage ../tools/system/which { };
* modified tetex to support extra .sty's from other packages * added lazylist and polytable (both tetex packages) * added lhs2tex ebuild, depending on the two above svn path=/nixpkgs/trunk/; revision=4609
2006-01-27 21:51:41 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wicd = callPackage ../tools/networking/wicd { };
Adding wicd, written by roconnor, sent to the nix-dev list on 2010-01-07 svn path=/nixpkgs/trunk/; revision=19297
2010-01-07 18:49:45 +01:00
updated wkhtmltopdf and use patched qt With stock version of qt4 wkthmltopdf lacks a lot of features, including: * Running without an X11 server * Printing more then one HTML document into a PDF file * Adding a document outline to the PDF file * Adding headers and footers to the PDF file * Generating a table of contents * Adding links in the generated PDF file * Printing using the screen media-type * Disabling the smart shrink feature of webkit
2014-08-28 23:58:08 +02:00
wkhtmltopdf = callPackage ../tools/graphics/wkhtmltopdf {
overrideDerivation = lib.overrideDerivation;
inherit (xlibs) libX11 libXext libXrender;
};
* Added wkhtmltopdf. svn path=/nixpkgs/trunk/; revision=31604
2012-01-17 12:04:14 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wv = callPackage ../tools/misc/wv { };
Added wvVare - tools for converting Microsoft Word formats to usable ones. svn path=/nixpkgs/trunk/; revision=9152
2007-08-18 10:32:12 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wv2 = callPackage ../tools/misc/wv2 { };
Added wv2 library svn path=/nixpkgs/trunk/; revision=15777
2009-05-28 21:22:32 +02:00
x86info-1.30
2013-01-09 20:49:41 +01:00
x86info = callPackage ../os-specific/linux/x86info { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
x11_ssh_askpass = callPackage ../tools/networking/x11-ssh-askpass { };
* Added x11-ssh-askpass. svn path=/nixpkgs/trunk/; revision=8529
2007-04-02 15:46:56 +02:00
* Fix an evaluation error in xburst-tools. svn path=/nixpkgs/branches/stdenv-updates/; revision=25311
2010-12-28 18:25:17 +01:00
xbursttools = assert stdenv ? glibc; import ../tools/misc/xburst-tools {
Made xbursttools have libusb and libusb1. Looks like depending on both. svn path=/nixpkgs/trunk/; revision=32969
2012-03-10 12:26:55 +01:00
inherit stdenv fetchgit autoconf automake confuse pkgconfig libusb libusb1;
Making the xburst-tools for the Ben Nanonote build the firmware they need to communicate with it. This involves making a cross-compiler for mipsel. svn path=/nixpkgs/trunk/; revision=22818
2010-07-30 01:26:07 +02:00
# It needs a cross compiler for mipsel to build the firmware it will
# load into the Ben Nanonote
* Fix eval-release.nix by testing whether all attributes of a derivation evaluate inside the tryEval. This catches cases such as aufs2-util, which fails due to an assertion in its dependency aufs2. * Explicitly blacklist "xbursttools" because it gives some evaluation error in cross-OpenSSL. No idea why, probably due to some pass-through attribute. svn path=/nixpkgs/trunk/; revision=23247
2010-08-19 14:37:10 +02:00
gccCross =
let
Making the xburst-tools for the Ben Nanonote build the firmware they need to communicate with it. This involves making a cross-compiler for mipsel. svn path=/nixpkgs/trunk/; revision=22818
2010-07-30 01:26:07 +02:00
pkgsCross = (import ./all-packages.nix) {
inherit system;
inherit bootStdenv noSysDirs gccWithCC gccWithProfiling config;
# Ben Nanonote system
crossSystem = {
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
config = "mipsel-unknown-linux";
Making the xburst-tools for the Ben Nanonote build the firmware they need to communicate with it. This involves making a cross-compiler for mipsel. svn path=/nixpkgs/trunk/; revision=22818
2010-07-30 01:26:07 +02:00
bigEndian = true;
arch = "mips";
float = "soft";
withTLS = true;
libc = "uclibc";
platform = {
name = "ben_nanonote";
kernelMajor = "2.6";
# It's not a bcm47xx processor, but for the headers this should work
kernelHeadersBaseConfig = "bcm47xx_defconfig";
kernelArch = "mips";
};
gcc = {
arch = "mips32";
};
};
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
in
Making the xburst-tools for the Ben Nanonote build the firmware they need to communicate with it. This involves making a cross-compiler for mipsel. svn path=/nixpkgs/trunk/; revision=22818
2010-07-30 01:26:07 +02:00
pkgsCross.gccCrossStageStatic;
Adding xburst-tools to manage the USB_BOOT mode of the Ben Nanonote (reflashing, ...) I add the 'confuse' library as a side effect. svn path=/nixpkgs/trunk/; revision=22817
2010-07-30 01:25:42 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xclip = callPackage ../tools/misc/xclip { };
xclip added svn path=/nixpkgs/trunk/; revision=9355
2007-09-21 23:40:23 +02:00
Add the bspwm window manager to Nix.
2014-08-09 23:31:05 +02:00
xtitle = callPackage ../tools/misc/xtitle { };
* Added xdelta. svn path=/nixpkgs/trunk/; revision=24907
2010-11-28 17:37:48 +01:00
xdelta = callPackage ../tools/compression/xdelta { };
Add new package xdummy, a dummy X server. This is actually a small script which just starts an X server without any real display. Right now only needed for running the test suite of the i3 window manager within the Nix chroot, but might be useful for running other tests needing a DISPLAY. Usage is just like a regular X server, so in order to start an instance for display :666, you just run it like this: xdummy :666 Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-08-01 05:17:23 +02:00
xdummy = callPackage ../tools/misc/xdummy { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xfsprogs = callPackage ../tools/filesystems/xfsprogs { };
* Refactoring: move most filesystem utilities / FUSE filesystems to tools/filesystems. Previously they were all over the place. svn path=/nixpkgs/trunk/; revision=18809
2009-12-04 16:39:49 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
xmlroff = callPackage ../tools/typesetting/xmlroff {
Added pangoxsl and xmlroff svn path=/nixpkgs/trunk/; revision=3574
2005-08-13 23:35:49 +02:00
inherit (gnome) libgnomeprint;
Added jing-tools to the cache svn path=/nixpkgs/trunk/; revision=3570
2005-08-13 20:12:10 +02:00
};
* Added xmlstarlet. svn path=/nixpkgs/trunk/; revision=23271
2010-08-20 12:07:35 +02:00
xmlstarlet = callPackage ../tools/text/xml/xmlstarlet { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xmlto = callPackage ../tools/typesetting/xmlto { };
Add `xmlto', a front-end to an XSL toolchain. svn path=/nixpkgs/trunk/; revision=11048
2008-03-11 09:44:22 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xmltv = callPackage ../tools/misc/xmltv { };
* Qt: add optional support for MySQL. * MythTV: the setup program works :-). * Added XmlTV. This requires a huge number of Perl modules, so... * Added a generic builder for Perl modules. I'm lazy so the modules are defined directly in all-packages-generic.nix. The generic builder also patches Perl scripts to include a hard-coded Perl module search path (i.e., similar to an RPATH in ELF executables). svn path=/nixpkgs/trunk/; revision=2083
2005-01-22 01:19:27 +01:00
Added xmpppy - python XMPP library and pyIRCt - python IRC transport svn path=/nixpkgs/trunk/; revision=15005
2009-04-13 01:27:55 +02:00
xmpppy = builderDefsPackage (import ../development/python-modules/xmpppy) {
inherit python setuptools;
};
Add GNU xorriso, which supersedes GNU mkisofs. svn path=/nixpkgs/trunk/; revision=25703
2011-01-27 21:12:28 +01:00
xorriso = callPackage ../tools/cd-dvd/xorriso { };
Revert "adapted xpf to new libxml2Python" This reverts commit b1f634f3d384a39e015d69e348cf220855457049. svn path=/nixpkgs/branches/stdenv-updates/; revision=32649
2012-02-28 01:07:08 +01:00
xpf = callPackage ../tools/text/xml/xpf {
libxml2 = libxml2Python;
};
- add mktemp - disable tiger, strategoxt, they don't work and give errors - ftp.nl.kernel.org seems to have some problems, replaced with ftp.de.kernel.org should be put back eventually svn path=/nixpkgs/trunk/; revision=1215
2004-08-03 17:41:08 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xsel = callPackage ../tools/misc/xsel { };
also add nmap here svn path=/nixpkgs/trunk/; revision=1238
2004-08-06 12:01:15 +02:00
Adding TFTP-HPA svn path=/nixpkgs/trunk/; revision=28915
2011-08-30 09:02:01 +02:00
xtreemfs = callPackage ../tools/filesystems/xtreemfs {};
xvfb-run: add some runtime dependencies to wrapper, set FONTCONFIG_FILE
2012-08-07 03:27:00 +02:00
xvfb_run = callPackage ../tools/misc/xvfb-run { inherit (texFunctions) fontsConf; };
Add xvfb-run, a wrapper script for Xvfb.
2012-08-07 03:14:17 +02:00
youtube-dl: upgrade to 2013.06.21
2013-06-23 09:38:44 +02:00
youtubeDL = callPackage ../tools/misc/youtube-dl { };
youtube-dl: new package (download clips from youtube) svn path=/nixpkgs/trunk/; revision=31654
2012-01-18 21:32:37 +01:00
Fix ZBar build by passing it gtk2
2013-03-21 08:59:07 +01:00
zbar = callPackage ../tools/graphics/zbar {
pygtk = lib.overrideDerivation pygtk (x: {
gtk = gtk2;
});
};
Adding ZBar svn path=/nixpkgs/trunk/; revision=29001
2011-09-04 11:12:00 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
zdelta = callPackage ../tools/compression/zdelta { };
* GnuPG updated to 1.4.2. Added support to optionally build it with IDEA support (requires a license). svn path=/nixpkgs/trunk/; revision=4399
2005-12-18 23:14:31 +01:00
zfstools: Add new package zfstools is an OpenSolaris-like and compatible auto snapshotting script for ZFS, which also supports auto snapshotting mysql databases.
2014-01-21 19:47:04 +01:00
zfstools = callPackage ../tools/filesystems/zfstools {
zfs = linuxPackages.zfs;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
zile = callPackage ../applications/editors/zile { };
Add GNU Zile, a tiny Emacs clone. svn path=/nixpkgs/trunk/; revision=14249
2009-02-25 21:24:18 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
zip = callPackage ../tools/archivers/zip { };
* Added Xauth (pilfered from the modular X.org tree). svn path=/nixpkgs/trunk/; revision=3466
2005-07-29 12:06:49 +02:00
Adding reference to ZPAQ in all-packages
2013-03-09 13:36:37 +01:00
zpaq = callPackage ../tools/archivers/zpaq { };
Fix/split ZPAQ after upgrade
2013-10-20 20:30:40 +02:00
zpaqd = callPackage ../tools/archivers/zpaq/zpaqd.nix { };
Adding reference to ZPAQ in all-packages
2013-03-09 13:36:37 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
zsync = callPackage ../tools/compression/zsync { };
* TightVNC. svn path=/nixpkgs/trunk/; revision=5698
2006-07-13 16:54:24 +02:00
* dhclient: don't flush IPv6 addresses/routes. svn path=/nixpkgs/trunk/; revision=26455
2011-03-22 13:55:55 +01:00
* Updates paths in all-packages-generic.fix. svn path=/nixpkgs/trunk/; revision=472
2003-11-03 19:21:30 +01:00
### SHELLS
shells/bash/4.1,2.nix have been replaced by default.nix svn path=/nixpkgs/branches/stdenv-updates/; revision=29542
2011-09-29 23:48:33 +02:00
bash = lowPrio (callPackage ../shells/bash {
* Turn vim/default.nix into a regular package. We don't need two configurable VIMs. svn path=/nixpkgs/trunk/; revision=22784
2010-07-28 14:52:54 +02:00
texinfo = null;
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
});
* bash: updated to 4.0 patchlevel 17. Removed the dietlibc patch, we don't need it anymore. svn path=/nixpkgs/branches/stdenv-updates/; revision=15018
2009-04-13 20:38:45 +02:00
shells/bash/4.1,2.nix have been replaced by default.nix svn path=/nixpkgs/branches/stdenv-updates/; revision=29542
2011-09-29 23:48:33 +02:00
bashInteractive = appendToName "interactive" (callPackage ../shells/bash {
* Yes! Finally! Bash built with ncurses support! This fixes the annoying problem with lines longer than 80 (?) characters. svn path=/nixpkgs/trunk/; revision=8248
2007-03-06 23:46:03 +01:00
interactive = true;
Adding GNU readline 6.3 apart I set bashInteractive to use it, as it has many relevant fixes.
2014-03-20 13:00:46 +01:00
readline = readline63; # Includes many vi mode fixes
* Delete some obsolete packages. * Make sure that every package in all-packages.nix has a unique name. Not all of them do, but there are now a few helper functions that modify the name of a package for display purposes in nix-env (e.g., you get "zlib-1.2.3" and "zlib-1.2.3-static" in "nix-env -qa"). svn path=/nixpkgs/trunk/; revision=8607
2007-04-26 15:02:30 +02:00
});
* Yes! Finally! Bash built with ncurses support! This fixes the annoying problem with lines longer than 80 (?) characters. svn path=/nixpkgs/trunk/; revision=8248
2007-03-06 23:46:03 +01:00
all-packages.nix: added package bash-completion svn path=/nixpkgs/trunk/; revision=27895
2011-07-22 00:02:01 +02:00
bashCompletion = callPackage ../shells/bash-completion { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dash = callPackage ../shells/dash { };
* Added dash. svn path=/nixpkgs/trunk/; revision=22088
2010-06-01 19:05:29 +02:00
fish: fix 'fish_config' by providing python ncurses module Gets rid of the "ImportError: No module named _curses" (and failure to display page) when clicking the "prompt" page in the 'fish_config' web UI.
2014-06-30 20:39:02 +02:00
fish = callPackage ../shells/fish {
python = python27Full;
};
fish: Add fish 2.0.0
2013-06-04 11:20:30 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tcsh = callPackage ../shells/tcsh { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rush = callPackage ../shells/rush { };
Add GNU SASL, GNU GSS-API, and GNU Rush. Contributed by Brian Gough <bjg@gnu.org>. svn path=/nixpkgs/trunk/; revision=21315
2010-04-26 10:59:25 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
zsh = callPackage ../shells/zsh { };
Added zsh svn path=/nixpkgs/trunk/; revision=8900
2007-06-20 12:02:10 +02:00
* Updates paths in all-packages-generic.fix. svn path=/nixpkgs/trunk/; revision=472
2003-11-03 19:21:30 +01:00
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
### DEVELOPMENT / COMPILERS
* Updates paths in all-packages-generic.fix. svn path=/nixpkgs/trunk/; revision=472
2003-11-03 19:21:30 +01:00
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
abc =
abcPatchable [];
add nixStatic and binutilsStatic svn path=/nixpkgs/trunk/; revision=6055
2006-08-05 13:02:17 +02:00
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
abcPatchable = patches :
* Remove redundant parentheses. svn path=/nixpkgs/trunk/; revision=6758
2006-10-18 12:32:45 +02:00
import ../development/compilers/abc/default.nix {
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
inherit stdenv fetchurl patches jre apacheAnt;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
javaCup = callPackage ../development/libraries/java/cup { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
};
move binutils-arm to binutils-cross. Also, add binutils for mips-linux in a more generic way. Still, there is a lot of room for improvement. svn path=/nixpkgs/trunk/; revision=4458
2005-12-31 04:46:20 +01:00
Add aldor.
2013-07-17 18:17:38 +02:00
aldor = callPackage ../development/compilers/aldor { };
Alice ML 1.4 programming language
2014-05-29 03:05:30 +02:00
aliceml = callPackage ../development/compilers/aliceml { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
aspectj = callPackage ../development/compilers/aspectj { };
* Added patchelf. svn path=/nixpkgs/trunk/; revision=1505
2004-09-25 21:32:23 +02:00
Adding ATS1, updating ATS2 package.
2014-03-25 04:51:35 +01:00
ats = callPackage ../development/compilers/ats { };
Add ats Signed-off-by: Shea Levy <shea@shealevy.com>
2013-10-25 19:33:32 +02:00
ats2 = callPackage ../development/compilers/ats2 { };
avra-1.3.0: Assember for the Atmel AVR microcontroller family Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-08-14 23:37:17 +02:00
avra = callPackage ../development/compilers/avra { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bigloo = callPackage ../development/compilers/bigloo { };
bigloo is now compiling svn path=/nixpkgs/trunk/; revision=10549
2008-02-08 02:35:01 +01:00
Add chicken-4.8.1
2013-03-26 15:52:54 +01:00
chicken = callPackage ../development/compilers/chicken { };
Added Clozure CL svn path=/nixpkgs/trunk/; revision=20211
2010-02-24 10:04:29 +01:00
ccl = builderDefsPackage ../development/compilers/ccl {};
llvm: Split llvmFull into separate derivations Now most packages in the llvm suite are built as separate derivations. The exceptions are: * compiler-rt must currently be built with llvm. This increases llvm's size by 6 MB * clang-tools-extra must be built with clang In addition, the top-level llvm attribute is defaulted to llvm 3.4, and llvm 3.3 must be accessed by the llvm_33 attribute. This is to make the out-of-date packages obvious in the hope that eventually all will be updated to work with 3.4 and 3.3 can be removed. I think we should keep this policy in the future (latest llvm gets top-level name, the rest are versioned until they can be removed). The llvm packages (except libc++, which exception I will try to remove on the next update) can all be accessed via the llvmPackages attribute, and there are also aliases for the packages that already existed (llvm, clang, and dragonegg). Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 02:19:53 +01:00
clang = wrapClang llvmPackages.clang;
Enable building clang separately from llvm Note that there is some duplication when building clang now. The llvm source is unpacked twice, ./configure is run twice, and two small unit test libraries are compiled twice. IMO this is a fair tradeoff for having llvm be a separate build unaffected by changes to clang svn path=/nixpkgs/trunk/; revision=29919
2011-10-19 22:57:18 +02:00
clang_34: make it evaluate to 3.4 even on Darwin
2014-04-11 10:10:24 +02:00
clang_34 = wrapClang llvmPackages_34.clang;
llvm: Enable also building of LLVM 3.[12] & Clang 3.[123].
2014-01-26 20:42:12 +01:00
clang_33 = wrapClang (clangUnwrapped llvm_33 ../development/compilers/llvm/3.3/clang.nix);
nixpkgs: clang-analyzer 3.4 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-30 02:36:43 +02:00
clangAnalyzer = callPackage ../development/tools/analysis/clang-analyzer {
clang = clang_34;
llvmPackages = llvmPackages_34;
};
llvm: Enable also building of LLVM 3.[12] & Clang 3.[123].
2014-01-26 20:42:12 +01:00
clangUnwrapped = llvm: pkg: callPackage pkg {
Hack to fix llvm/clang build on Darwin (Or at least restore it to the same level as brokenness as before the staging merge. I.e. it depends on gcc-apple, which doesn't build on standard 10.9 systems.)
2014-08-09 23:31:00 +02:00
stdenv = if stdenv.isDarwin then stdenvApple else stdenv;
inherit llvm;
llvm: Enable also building of LLVM 3.[12] & Clang 3.[123].
2014-01-26 20:42:12 +01:00
};
llvm: Split llvmFull into separate derivations Now most packages in the llvm suite are built as separate derivations. The exceptions are: * compiler-rt must currently be built with llvm. This increases llvm's size by 6 MB * clang-tools-extra must be built with clang In addition, the top-level llvm attribute is defaulted to llvm 3.4, and llvm 3.3 must be accessed by the llvm_33 attribute. This is to make the out-of-date packages obvious in the hope that eventually all will be updated to work with 3.4 and 3.3 can be removed. I think we should keep this policy in the future (latest llvm gets top-level name, the rest are versioned until they can be removed). The llvm packages (except libc++, which exception I will try to remove on the next update) can all be accessed via the llvmPackages attribute, and there are also aliases for the packages that already existed (llvm, clang, and dragonegg). Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 02:19:53 +01:00
clangSelf = clangWrapSelf llvmPackagesSelf.clang;
all-packages: Add a self-hosted variant of clang.
2013-09-07 11:05:53 +02:00
clangWrapSelf = build: (import ../build-support/clang-wrapper) {
Fix indentation
2014-01-07 10:48:14 +01:00
clang = build;
stdenv = clangStdenv;
libc = glibc;
binutils = binutils;
shell = bash;
inherit libcxx coreutils zlib;
nativeTools = false;
nativeLibc = false;
all-packages: Add a self-hosted variant of clang.
2013-09-07 11:05:53 +02:00
};
Bootstrap clang with itself svn path=/nixpkgs/trunk/; revision=29901
2011-10-19 19:11:26 +02:00
#Use this instead of stdenv to build with clang
Mark alternative stdenvs as lowPrio
2012-09-19 19:13:11 +02:00
clangStdenv = lowPrio (stdenvAdapters.overrideGCC stdenv clang);
llvm: Split llvmFull into separate derivations Now most packages in the llvm suite are built as separate derivations. The exceptions are: * compiler-rt must currently be built with llvm. This increases llvm's size by 6 MB * clang-tools-extra must be built with clang In addition, the top-level llvm attribute is defaulted to llvm 3.4, and llvm 3.3 must be accessed by the llvm_33 attribute. This is to make the out-of-date packages obvious in the hope that eventually all will be updated to work with 3.4 and 3.3 can be removed. I think we should keep this policy in the future (latest llvm gets top-level name, the rest are versioned until they can be removed). The llvm packages (except libc++, which exception I will try to remove on the next update) can all be accessed via the llvmPackages attribute, and there are also aliases for the packages that already existed (llvm, clang, and dragonegg). Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 02:19:53 +01:00
libcxxStdenv = stdenvAdapters.overrideGCC stdenv (clangWrapSelf llvmPackages.clang);
Making clang build for llvm 2.7 (I've not tested the usage of c++ headers though, but it builds c and c++ simple programs) svn path=/nixpkgs/trunk/; revision=22236
2010-06-12 23:52:39 +02:00
Add Concurrent Clean to NixPkgs. svn path=/nixpkgs/trunk/; revision=25276
2010-12-25 16:13:07 +01:00
clean = callPackage ../development/compilers/clean { };
New package: Google Closure compiler version 20130603. A JavaScript optimizing compiler.
2013-07-01 14:52:57 +02:00
closurecompiler = callPackage ../development/compilers/closure { };
Add CMUCL Common Lisp compiler svn path=/nixpkgs/trunk/; revision=24618
2010-11-08 09:58:50 +01:00
cmucl_binary = callPackage ../development/compilers/cmucl/binary.nix { };
compcert: add missing semicolon in all-packages.nix
2014-07-01 23:59:35 +02:00
compcert = callPackage ../development/compilers/compcert {};
nixpkgs: add CompCert Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-02 02:09:37 +02:00
cryptol: add 1.8.x expression This also includes support for the verification tools I'm using. Cryptol 2 is still the default obviously. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-30 00:50:20 +02:00
cryptol1 = lowPrio (callPackage ../development/compilers/cryptol/1.8.x.nix {});
Move 'cryptol' and 'darcs' from the generic Haskell package set into all-packages.nix. These packages need very a version of GHC to compile.
2014-08-20 11:57:38 +02:00
cryptol2 = with haskellPackages_ghc763; callPackage ../development/compilers/cryptol/2.0.x.nix {
Cabal = Cabal_1_18_1_3;
cabalInstall = cabalInstall_1_18_0_3;
process = process_1_2_0_0;
};
nixpkgs: Add cryptol2 expression This is just a convenient shorthand so people don't have to spell out haskellPackages.cryptol Note that the top-level expression is named 'cryptol2' but the package isn't. That's because Cryptol is a library and other things could depend on it (hence the vanilla name), but also the full name will be disambiguated as 'haskell-cryptol-ghc7.6.3' anyway. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-25 13:51:24 +02:00
refactor cython into pythonPackages, fixes #1803
2014-02-27 16:35:37 +01:00
cython = pythonPackages.cython;
cython3 = python3Packages.cython;
Add Cython, because it's needed to build xpra.
2012-06-05 15:18:34 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
dylan = callPackage ../development/compilers/gwydion-dylan {
* Fix evaluation errors. svn path=/nixpkgs/trunk/; revision=29955
2011-10-21 16:43:18 +02:00
dylan = callPackage ../development/compilers/gwydion-dylan/binary.nix { };
* A much newer version of flex. The old (GNU) one was from 1997. svn path=/nixpkgs/trunk/; revision=727
2004-01-30 11:10:06 +01:00
};
Build ECL with DFFI svn path=/nixpkgs/trunk/; revision=25610
2011-01-18 18:36:25 +01:00
ecl = callPackage ../development/compilers/ecl { };
ECL entry in all-packages svn path=/nixpkgs/trunk/; revision=19556
2010-01-20 06:41:18 +01:00
Add EQL (Embeddable Common Lisp + Qt) svn path=/nixpkgs/trunk/; revision=23842
2010-09-17 21:52:50 +02:00
eql = callPackage ../development/compilers/eql {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
adobe_flex_sdk = callPackage ../development/compilers/adobe-flex-sdk { };
adding open source adobe flex sdk svn path=/nixpkgs/trunk/; revision=14902
2009-04-06 15:07:21 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fpc = callPackage ../development/compilers/fpc { };
Added Free Pascal Compiler. svn path=/nixpkgs/trunk/; revision=9102
2007-08-11 22:55:40 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gambit = callPackage ../development/compilers/gambit { };
Top-level entry for gambit commit svn path=/nixpkgs/trunk/; revision=22028
2010-05-28 08:08:50 +02:00
Switch stdenv to GCC 4.8.0.
2013-04-04 15:15:57 +02:00
gcc = gcc48;
* Started adding gcc 3.4. svn path=/nixpkgs/trunk/; revision=1103
2004-06-29 10:25:55 +02:00
* Move all gcc versions to development/compilers/gcc. svn path=/nixpkgs/branches/stdenv-updates/; revision=32371
2012-02-17 22:47:08 +01:00
gcc33 = wrapGCC (import ../development/compilers/gcc/3.3 {
* Regularize the treatment of the "gcc" attributes in all-packages.nix. All "gcc*" attributes are wrapped GCC instances now. svn path=/nixpkgs/trunk/; revision=5671
2006-07-10 17:42:19 +02:00
inherit fetchurl stdenv noSysDirs;
});
* Move all gcc versions to development/compilers/gcc. svn path=/nixpkgs/branches/stdenv-updates/; revision=32371
2012-02-17 22:47:08 +01:00
gcc34 = wrapGCC (import ../development/compilers/gcc/3.4 {
* Regularize the treatment of the "gcc" attributes in all-packages.nix. All "gcc*" attributes are wrapped GCC instances now. svn path=/nixpkgs/trunk/; revision=5671
2006-07-10 17:42:19 +02:00
inherit fetchurl stdenv noSysDirs;
});
Remove gcc 4.7 There is really no reason to keep it around, given that it was never the default in Nixpkgs.
2014-01-07 10:36:15 +01:00
gcc48_realCross = lib.addMetaAttrs { hydraPlatforms = []; }
(callPackage ../development/compilers/gcc/4.8 {
inherit noSysDirs;
Changing the crosscompiler to gcc47. gcc from 4.5 to 4.7 have important bugs for mips. https://www.linux-mips.org/cgi-bin/mesg.cgi?a=linux-mips&i=20120906140843.GA17068%40linux-mips.org
2012-11-08 22:33:15 +01:00
binutilsCross = binutilsCross;
libcCross = libcCross;
profiledCompiler = false;
enableMultilib = false;
crossStageStatic = false;
cross = assert crossSystem != null; crossSystem;
});
Remove gcc 4.7 There is really no reason to keep it around, given that it was never the default in Nixpkgs.
2014-01-07 10:36:15 +01:00
gcc_realCross = gcc48_realCross;
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
gccCrossStageStatic = let
Merge 'mingw-w64' and 'darwin' into cross-win-osx. Both branches have quite a lot in common, so it's time for a merge and do the cleanups with respect to both implementations and also generalize both implementations as much as possible. This also closes #1876. Conflicts: pkgs/development/interpreters/lua-5/5.2.nix pkgs/development/libraries/SDL/default.nix pkgs/development/libraries/glew/default.nix pkgs/top-level/all-packages.nix
2014-03-12 10:16:51 +01:00
libcCross1 =
if stdenv.cross.libc == "msvcrt" then windows.mingw_w64_headers
else if stdenv.cross.libc == "libSystem" then darwin.xcode
else null;
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
in
wrapGCCCross {
Set meta.hydraPlatforms instead of meta.platforms for some packages
2013-11-05 00:04:36 +01:00
gcc = forceNativeDrv (lib.addMetaAttrs { hydraPlatforms = []; } (
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
gcc_realCross.override {
crossStageStatic = true;
langCC = false;
libcCross = libcCross1;
enableShared = false;
}));
libc = libcCross1;
binutils = binutilsCross;
cross = assert crossSystem != null; crossSystem;
};
# Only needed for mingw builds
gccCrossMingw2 = wrapGCCCross {
gcc = gccCrossStageStatic.gcc;
Making wxGTK stay wxGTK even cross-built, so I remove the wxMSW code I added to test the crossbuilding with wxGTK. I added a new windows-specific package: wxMSW. svn path=/nixpkgs/trunk/; revision=21634
2010-05-06 21:19:22 +02:00
libc = windows.mingw_headers2;
I removed the function-shape of the cross-toolchain related attributes in the all-packages.nix. That was more complicating than helping. svn path=/nixpkgs/trunk/; revision=20457
2010-03-07 00:36:55 +01:00
binutils = binutilsCross;
Adding assertions for the cross-toolchain attributes, so noone feels tempted to build them without setting a crossSystem to build for. svn path=/nixpkgs/trunk/; revision=20459
2010-03-07 01:05:51 +01:00
cross = assert crossSystem != null; crossSystem;
My first attempt at getting cross compilers in nixpkgs. My idea is to provide special stdenv expressions that will contain in the path additional cross compilers. As most expressions for programs accept a stdenv parameter, we could substitute this parameter with the special stdenv, which will have a generic builder that attempts the usual "--target=..." and can additionally have an env variable like "cross" with the target architecture set. So, finally we could have additional expressions like this: bashRealArm = makeOverridable (import ../shells/bash) { inherit fetchurl bison; stdenv = stdenvCross "armv5tel-unknown-linux-gnueabi"; }; Meanwhile it does not work - I still cannot get the cross-gcc to build. I think it does not fill the previous expressions with a lot of noise, so I think it may be a good path to follow. I only touched some files of the current stdenv: gcc-4.3, kernel headers 2.6.28, glibc 2.9, ... I tried to use the gcc-cross-wrapper, that may be very outdated. Maybe I will update it, or update the gcc-wrapper expression to make it fit the cross tools, but meanwhile I even cannot build gcc, so I have not tested the wrapper. This new idea on cross compiling is not similar to that of the nixpkgs/branches/cross-compilation, which mostly added bare new expressions for anything to be cross compiled, if I understood it correctly. I cared not to break anything of the usual stdenv in all this work. svn path=/nixpkgs/branches/stdenv-updates/; revision=18343
2009-11-14 09:11:30 +01:00
};
I removed the function-shape of the cross-toolchain related attributes in the all-packages.nix. That was more complicating than helping. svn path=/nixpkgs/trunk/; revision=20457
2010-03-07 00:36:55 +01:00
gccCrossStageFinal = wrapGCCCross {
More renames
2012-12-28 19:42:10 +01:00
gcc = forceNativeDrv (gcc_realCross.override {
GCC 4.5: Add support for a separate libpthread; rearrange target flags handling. svn path=/nixpkgs/trunk/; revision=21905
2010-05-19 23:32:19 +02:00
libpthreadCross =
# FIXME: Don't explicitly refer to `i586-pc-gnu'.
if crossSystem != null && crossSystem.config == "i586-pc-gnu"
Move GNU/Hurd package attributes under `os-specific/gnu/default.nix'. svn path=/nixpkgs/trunk/; revision=30173
2011-11-01 23:10:51 +01:00
then gnu.libpthreadCross
GCC 4.5: Add support for a separate libpthread; rearrange target flags handling. svn path=/nixpkgs/trunk/; revision=21905
2010-05-19 23:32:19 +02:00
else null;
cross-gcc: disable `langCC' when targeting MinGW
2013-03-06 00:01:10 +01:00
# XXX: We have troubles cross-compiling libstdc++ on MinGW (see
# <http://hydra.nixos.org/build/4268232>), so don't even try.
langCC = (crossSystem == null
|| crossSystem.config != "i686-pc-mingw32");
GCC 4.5: Add support for a separate libpthread; rearrange target flags handling. svn path=/nixpkgs/trunk/; revision=21905
2010-05-19 23:32:19 +02:00
});
I removed the function-shape of the cross-toolchain related attributes in the all-packages.nix. That was more complicating than helping. svn path=/nixpkgs/trunk/; revision=20457
2010-03-07 00:36:55 +01:00
libc = libcCross;
binutils = binutilsCross;
Adding assertions for the cross-toolchain attributes, so noone feels tempted to build them without setting a crossSystem to build for. svn path=/nixpkgs/trunk/; revision=20459
2010-03-07 01:05:51 +01:00
cross = assert crossSystem != null; crossSystem;
Fixing many things related to the cross compilation in stdenvCross. It still does not work, but I think I already get glibc cross compiled. Next: gcc and g++, and set some setup script hooks on stdenvCross. It took quite enough hours for this commit. svn path=/nixpkgs/branches/stdenv-updates/; revision=18351
2009-11-15 06:28:35 +01:00
};
My first attempt at getting cross compilers in nixpkgs. My idea is to provide special stdenv expressions that will contain in the path additional cross compilers. As most expressions for programs accept a stdenv parameter, we could substitute this parameter with the special stdenv, which will have a generic builder that attempts the usual "--target=..." and can additionally have an env variable like "cross" with the target architecture set. So, finally we could have additional expressions like this: bashRealArm = makeOverridable (import ../shells/bash) { inherit fetchurl bison; stdenv = stdenvCross "armv5tel-unknown-linux-gnueabi"; }; Meanwhile it does not work - I still cannot get the cross-gcc to build. I think it does not fill the previous expressions with a lot of noise, so I think it may be a good path to follow. I only touched some files of the current stdenv: gcc-4.3, kernel headers 2.6.28, glibc 2.9, ... I tried to use the gcc-cross-wrapper, that may be very outdated. Maybe I will update it, or update the gcc-wrapper expression to make it fit the cross tools, but meanwhile I even cannot build gcc, so I have not tested the wrapper. This new idea on cross compiling is not similar to that of the nixpkgs/branches/cross-compilation, which mostly added bare new expressions for anything to be cross compiled, if I understood it correctly. I cared not to break anything of the usual stdenv in all this work. svn path=/nixpkgs/branches/stdenv-updates/; revision=18343
2009-11-14 09:11:30 +01:00
* Move all gcc versions to development/compilers/gcc. svn path=/nixpkgs/branches/stdenv-updates/; revision=32371
2012-02-17 22:47:08 +01:00
gcc44 = lowPrio (wrapGCC (makeOverridable (import ../development/compilers/gcc/4.4) {
gcc: use texinfo4, fix bad mpfr reference
2013-06-30 22:25:30 +02:00
inherit fetchurl stdenv gmp mpfr /* ppl cloogppl */
GCJ 4.4: Provide InfoZIP; remove FastJar hack; don't build C; provide which(1). svn path=/nixpkgs/trunk/; revision=16475
2009-07-27 17:40:01 +02:00
gettext which noSysDirs;
gcc: use texinfo4, fix bad mpfr reference
2013-06-30 22:25:30 +02:00
texinfo = texinfo4;
Add GCC 4.4.0 (and hope for the best). svn path=/nixpkgs/trunk/; revision=16168
2009-07-03 20:54:28 +02:00
profiledCompiler = true;
* GCC 4.3 should be the default. svn path=/nixpkgs/trunk/; revision=17368
2009-09-23 20:33:40 +02:00
}));
Add GCC 4.4.0 (and hope for the best). svn path=/nixpkgs/trunk/; revision=16168
2009-07-03 20:54:28 +02:00
gcc: Fix building 4.5 and 4.6
2014-01-13 19:11:46 +01:00
gcc45 = lowPrio (wrapGCC (callPackage ../development/compilers/gcc/4.5 {
gcc: use texinfo4, fix bad mpfr reference
2013-06-30 22:25:30 +02:00
inherit fetchurl stdenv gmp mpfr mpc libelf zlib perl
GCC 4.5.0. svn path=/nixpkgs/trunk/; revision=21403
2010-04-28 14:37:11 +02:00
gettext which noSysDirs;
gcc: use texinfo4, fix bad mpfr reference
2013-06-30 22:25:30 +02:00
texinfo = texinfo4;
gcc: Fix building 4.5 and 4.6
2014-01-13 19:11:46 +01:00
ppl = null;
cloogppl = null;
Avoiding to make a profiled bootstrap of gcc on armv5tel-linux, because it fails there. svn path=/nixpkgs/branches/stdenv-updates/; revision=22970
2010-08-05 20:40:58 +02:00
# bootstrapping a profiled compiler does not work in the sheevaplug:
# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43944
Clean up redundant "if condition then true else false"
2012-12-28 19:57:47 +01:00
profiledCompiler = !stdenv.isArm;
GCC 4.5: Allow `libcCross != null && cross == null' for `gcc.hostDrv'. svn path=/nixpkgs/trunk/; revision=30401
2011-11-13 00:55:41 +01:00
Rename hostDrv -> crossDrv, buildDrv -> nativeDrv This is for consistency with terminology in stdenv (and the terms "hostDrv" and "buildDrv" are not very intuitive, even if they're consistent with GNU terminology).
2012-12-28 19:08:19 +01:00
# When building `gcc.crossDrv' (a "Canadian cross", with host == target
GCC 4.5: Allow `libcCross != null && cross == null' for `gcc.hostDrv'. svn path=/nixpkgs/trunk/; revision=30401
2011-11-13 00:55:41 +01:00
# and host != build), `cross' must be null but the cross-libc must still
# be passed.
cross = null;
libcCross = if crossSystem != null then libcCross else null;
libpthreadCross =
if crossSystem != null && crossSystem.config == "i586-pc-gnu"
then gnu.libpthreadCross
else null;
GCC 4.5.0. svn path=/nixpkgs/trunk/; revision=21403
2010-04-28 14:37:11 +02:00
}));
Drop pointless gcc_real variables
2014-01-07 10:39:15 +01:00
gcc46 = lowPrio (wrapGCC (callPackage ../development/compilers/gcc/4.6 {
GCC 4.6: Use `callPackage'. svn path=/nixpkgs/trunk/; revision=26713
2011-04-06 14:52:29 +02:00
inherit noSysDirs;
gcc: Fix building 4.5 and 4.6
2014-01-13 19:11:46 +01:00
ppl = null;
cloog = null;
Update to GCC 4.6.0: * Modify the builder to not fail when a static library is in $out/libexec/gcc/*/* * Disable libquadmath when building a static-only bootstrap of GCC, see http://gcc.gnu.org/ml/gcc/2011-03/msg00465.html * Add handling for cloog if it is passed in in place of cloog-ppl svn path=/nixpkgs/trunk/; revision=26639
2011-03-31 23:51:39 +02:00
# bootstrapping a profiled compiler does not work in the sheevaplug:
# http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43944
Fix the right compiler Doh!
2013-12-17 11:29:08 +01:00
profiledCompiler = false;
GCC 4.6: Fix the Canadian cross. svn path=/nixpkgs/trunk/; revision=32621
2012-02-27 18:22:30 +01:00
Rename hostDrv -> crossDrv, buildDrv -> nativeDrv This is for consistency with terminology in stdenv (and the terms "hostDrv" and "buildDrv" are not very intuitive, even if they're consistent with GNU terminology).
2012-12-28 19:08:19 +01:00
# When building `gcc.crossDrv' (a "Canadian cross", with host == target
GCC 4.6: Fix the Canadian cross. svn path=/nixpkgs/trunk/; revision=32621
2012-02-27 18:22:30 +01:00
# and host != build), `cross' must be null but the cross-libc must still
# be passed.
cross = null;
libcCross = if crossSystem != null then libcCross else null;
libpthreadCross =
if crossSystem != null && crossSystem.config == "i586-pc-gnu"
then gnu.libpthreadCross
else null;
explicitly flag gcc 4.6 as needing texinfo 4.13
2013-06-29 19:33:45 +02:00
texinfo = texinfo413;
Update to GCC 4.6.0: * Modify the builder to not fail when a static library is in $out/libexec/gcc/*/* * Disable libquadmath when building a static-only bootstrap of GCC, see http://gcc.gnu.org/ml/gcc/2011-03/msg00465.html * Add handling for cloog if it is passed in in place of cloog-ppl svn path=/nixpkgs/trunk/; revision=26639
2011-03-31 23:51:39 +02:00
}));
Drop pointless gcc_real variables
2014-01-07 10:39:15 +01:00
gcc48 = lowPrio (wrapGCC (callPackage ../development/compilers/gcc/4.8 {
gcc: add version 4.8.0
2013-04-04 13:55:20 +02:00
inherit noSysDirs;
gcc48: turn on PGO on x86*, see #445
2013-04-10 08:59:59 +02:00
# PGO seems to speed up compilation by gcc by ~10%, see #445 discussion
gcc: don't use profiling on darwin Darwin seems to have problems on Hydra, maybe because of this.
2013-10-08 20:52:19 +02:00
profiledCompiler = with stdenv; (!isDarwin && (isi686 || isx86_64));
gcc: add version 4.8.0
2013-04-04 13:55:20 +02:00
# When building `gcc.crossDrv' (a "Canadian cross", with host == target
# and host != build), `cross' must be null but the cross-libc must still
# be passed.
cross = null;
libcCross = if crossSystem != null then libcCross else null;
libpthreadCross =
if crossSystem != null && crossSystem.config == "i586-pc-gnu"
then gnu.libpthreadCross
else null;
}));
Use gcc48_multi for stdenv_32bit Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 22:12:41 +01:00
gcc48_multi =
if system == "x86_64-linux" then lowPrio (
wrapGCCWith (import ../build-support/gcc-wrapper) glibc_multi (gcc48.gcc.override {
stdenv = overrideGCC stdenv (wrapGCCWith (import ../build-support/gcc-wrapper) glibc_multi gcc.gcc);
profiledCompiler = false;
enableMultilib = true;
}))
else throw "Multilib gcc not supported on ‘${system}’";
gcc: add version 4.8.0
2013-04-04 13:55:20 +02:00
gcc48_debug = lowPrio (wrapGCC (callPackage ../development/compilers/gcc/4.8 {
stripped = false;
inherit noSysDirs;
cross = null;
libcCross = null;
binutilsCross = null;
}));
Add gcc-4.9.0
2014-04-23 16:45:00 +02:00
gcc49 = lowPrio (wrapGCC (callPackage ../development/compilers/gcc/4.9 {
inherit noSysDirs;
# PGO seems to speed up compilation by gcc by ~10%, see #445 discussion
profiledCompiler = with stdenv; (!isDarwin && (isi686 || isx86_64));
# When building `gcc.crossDrv' (a "Canadian cross", with host == target
# and host != build), `cross' must be null but the cross-libc must still
# be passed.
cross = null;
libcCross = if crossSystem != null then libcCross else null;
libpthreadCross =
if crossSystem != null && crossSystem.config == "i586-pc-gnu"
then gnu.libpthreadCross
else null;
}));
pkgs/applications/editors/emacs-modes/prolog: initial version of prolog-mode for Emacs svn path=/nixpkgs/trunk/; revision=18675
2009-11-27 18:40:56 +01:00
gccApple =
Remove support for the obsolete powerpc-darwin and i686-darwin platforms
2012-11-29 14:10:49 +01:00
assert stdenv.isDarwin;
wrapGCC (makeOverridable (import ../development/compilers/gcc/4.2-apple64) {
inherit fetchurl noSysDirs;
profiledCompiler = true;
# Since it fails to build with GCC 4.6, build it with the "native"
# Apple-GCC.
stdenv = allStdenvs.stdenvNative;
});
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
gfortran: use 4.8 and remove 4.7 (close #1038) Thanks to @mornfall.
2013-10-29 20:14:45 +01:00
gfortran = gfortran48;
Add gfortran46 svn path=/nixpkgs/trunk/; revision=26641
2011-03-31 23:59:38 +02:00
gfortran: update to 4.8.1
2013-09-20 21:45:42 +02:00
gfortran48 = wrapGCC (gcc48.gcc.override {
name = "gfortran";
langFortran = true;
langCC = false;
langC = false;
profiledCompiler = false;
});
gcj: use 4.8 and drop all others See/complain on discussion #699.
2013-10-30 07:53:38 +01:00
gcj = gcj48;
gcj: add 47 and 48, make 47 default gcj48 doesn't build yet
2013-07-08 09:14:23 +02:00
gcj48 = wrapGCC (gcc48.gcc.override {
name = "gcj";
langJava = true;
langFortran = false;
langCC = false;
langC = false;
profiledCompiler = false;
inherit zip unzip zlib boehmgc gettext pkgconfig perl;
inherit gtk;
inherit (gnome) libart_lgpl;
inherit (xlibs) libX11 libXt libSM libICE libXtst libXi libXrender
libXrandr xproto renderproto xextproto inputproto randrproto;
});
Uh, there were references to gcc44_real still. I hope not anymore. I decided to update gfortran to gfortran45 (it was gfortran43) svn path=/nixpkgs/branches/stdenv-updates/; revision=22276
2010-06-15 14:11:40 +02:00
gnat = gnat45;
Drop pointless gcc_real variables
2014-01-07 10:39:15 +01:00
gnat45 = wrapGCC (gcc45.gcc.override {
Adding first built version of the gnat compiler for gcc 4.4. Some things don't work: - The ghdl expression (it still needs the gcc 4.3.4 src, ...) - The gnat wrappers need to be more generic - now they work only for the given gnatboot (taken from gentoo) and gnats installed to their $out store path. - Using the cloogppl and ppl. We will need our own gnatboot built with c++ libraries for that. svn path=/nixpkgs/branches/stdenv-updates/; revision=19060
2009-12-21 08:49:31 +01:00
name = "gnat";
langCC = false;
langC = true;
langAda = true;
profiledCompiler = false;
inherit gnatboot;
# We can't use the ppl stuff, because we would have
# libstdc++ problems.
cloogppl = null;
ppl = null;
});
Drop pointless gcc_real variables
2014-01-07 10:39:15 +01:00
gnat46 = wrapGCC (gcc46.gcc.override {
Add gnat46. Note that, contrary to my notes when I emailed this patch, this builds now: we use gnat45 as an Ada bootstrap in place of gnatboot. This is not a long-term solution, but it works for now. svn path=/nixpkgs/trunk/; revision=26645
2011-04-01 00:20:11 +02:00
name = "gnat";
langCC = false;
langC = true;
langAda = true;
profiledCompiler = false;
gnatboot = gnat45;
# We can't use the ppl stuff, because we would have
# libstdc++ problems.
ppl = null;
cloog = null;
});
Merging the gnat-wrapper and gcc-wrapper into a single gcc-wrapper. (I will remove the gnat-wrapper files if this works, later) svn path=/nixpkgs/branches/stdenv-updates/; revision=19492
2010-01-16 22:32:44 +01:00
gnatboot = wrapGCC (import ../development/compilers/gnatboot {
Adding first built version of the gnat compiler for gcc 4.4. Some things don't work: - The ghdl expression (it still needs the gcc 4.3.4 src, ...) - The gnat wrappers need to be more generic - now they work only for the given gnatboot (taken from gentoo) and gnats installed to their $out store path. - Using the cloogppl and ppl. We will need our own gnatboot built with c++ libraries for that. svn path=/nixpkgs/branches/stdenv-updates/; revision=19060
2009-12-21 08:49:31 +01:00
inherit fetchurl stdenv;
});
switch default gccgo to 4.8
2013-11-05 16:57:11 +01:00
gccgo = gccgo48;
Add support for the new Go frontend to GCC 4.6.0. This isn't as useful as it could be, since gcc-wrapper doesn't know about the gccgo binary so there is no gccgo wrapper script. Since changing gcc-wrapper would lead to a nearly full rebuild, I thing the change to gcc-wrapper should go into stdenv-updates. svn path=/nixpkgs/trunk/; revision=26668
2011-04-02 17:21:36 +02:00
Drop pointless gcc_real variables
2014-01-07 10:39:15 +01:00
gccgo48 = wrapGCC (gcc48.gcc.override {
gccgo: add 4.8
2013-11-05 16:56:56 +01:00
name = "gccgo";
langCC = true; #required for go.
langC = true;
langGo = true;
});
* Move all gcc versions to development/compilers/gcc. svn path=/nixpkgs/branches/stdenv-updates/; revision=32371
2012-02-17 22:47:08 +01:00
ghdl = wrapGCC (import ../development/compilers/gcc/4.3 {
gcc: use texinfo4, fix bad mpfr reference
2013-06-30 22:25:30 +02:00
inherit stdenv fetchurl gmp mpfr noSysDirs gnat;
texinfo = texinfo4;
Moving most of the ghdl logic outside the middle of the gcc expression. Agreed on a final naming logic for the ghdl package: ghdl-wrapper-0.29 svn path=/nixpkgs/branches/stdenv-updates/; revision=19450
2010-01-15 00:03:31 +01:00
name = "ghdl";
Getting a new gcc-wrapper on the way. After gnat-wrapper, I introduce ghdl-wrapper. I made the gcc-4.3.4 expression allow the 'vhdl' language through ghdl. The ghdl developer recommends this gcc version; maybe it would work with gcc-4.4. If not this ghdl version, maybe next versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=19071
2009-12-22 00:02:06 +01:00
langVhdl = true;
langCC = false;
langC = false;
profiledCompiler = false;
enableMultilib = false;
});
Adding ghdl 0.31 mcode flavour This allows having a recent ghdl, without building it with gcc. The major drawback is the speed.
2014-04-16 10:33:27 +02:00
ghdl_mcode = callPackage ../development/compilers/ghdl { };
Fix wxGTK reference for xchm svn path=/nixpkgs/trunk/; revision=18156
2009-11-05 22:08:53 +01:00
gcl = builderDefsPackage ../development/compilers/gcl {
pkgs/top-level/all-packages.nix: stripped trailing whitespace svn path=/nixpkgs/trunk/; revision=22734
2010-07-26 15:41:09 +02:00
inherit mpfr m4 binutils fetchcvs emacs zlib which
GCL needs gmp4 svn path=/nixpkgs/trunk/; revision=33770
2012-04-13 07:40:05 +02:00
texinfo;
gmp = gmp4;
pkgs/applications/editors/emacs-modes/prolog: initial version of prolog-mode for Emacs svn path=/nixpkgs/trunk/; revision=18675
2009-11-27 18:40:56 +01:00
inherit (xlibs) libX11 xproto inputproto libXi
Try using latest CLisp for SBCL in case SBCL fixed compatibility issues svn path=/nixpkgs/trunk/; revision=18184
2009-11-06 08:39:59 +01:00
libXext xextproto libXt libXaw libXmu;
Apparently fixed GCL build svn path=/nixpkgs/trunk/; revision=22498
2010-07-06 18:48:03 +02:00
inherit stdenv;
Oops, pass needed args svn path=/nixpkgs/trunk/; revision=22542
2010-07-09 06:24:31 +02:00
texLive = texLiveAggregationFun {
paths = [
texLive texLiveExtra
];
};
Fix wxGTK reference for xchm svn path=/nixpkgs/trunk/; revision=18156
2009-11-05 22:08:53 +01:00
};
Add jhc 0.8.0
2012-10-07 17:52:43 +02:00
jhc = callPackage ../development/compilers/jhc {
jhc: 0.8.0 -> 0.8.1 Also, bootstrap the compiler with GHC 7.6.3 instead of 6.12.3. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-18 17:14:03 +02:00
inherit (haskellPackages_ghc763) ghc binary zlib utf8String readline fgl
Drop a bunch of old unused gcc cross/debug variants
2014-01-07 10:46:59 +01:00
regexCompat HsSyck random;
Add jhc 0.8.0
2012-10-07 17:52:43 +02:00
};
Add gcc-arm-embedded. These are packages for precompiled ARM microcontroller compilers from https://launchpad.net/gcc-arm-embedded. [Bjørn: modify commit message (add paragraph).]
2014-03-29 11:00:26 +01:00
gcc-arm-embedded-4_7 = callPackage_i686 ../development/compilers/gcc-arm-embedded {
version = "4.7-2013q3-20130916";
releaseType = "update";
sha256 = "1bd9bi9q80xn2rpy0rn1vvj70rh15kb7dmah0qs4q2rv78fqj40d";
};
gcc-arm-embedded-4_8 = callPackage_i686 ../development/compilers/gcc-arm-embedded {
version = "4.8-2014q1-20140314";
releaseType = "update";
sha256 = "ce92859550819d4a3d1a6e2672ea64882b30afa2c08cf67fa8e1d93788c2c577";
};
gcc-arm-embedded = gcc-arm-embedded-4_8;
Restructured Haskell packages a bit. * There's a new file called haskell-defaults.nix. * The new file contains: - Default package version settings for each compiler version. - All the stuff that previously still was in all-packages.nix. * A relatively small part is left in all-packages.nix. svn path=/nixpkgs/trunk/; revision=34088
2012-05-14 15:09:05 +02:00
# Haskell and GHC
Added GHC HEAD snapshot. svn path=/nixpkgs/trunk/; revision=17227
2009-09-17 13:45:20 +02:00
Restructured Haskell packages a bit. * There's a new file called haskell-defaults.nix. * The new file contains: - Default package version settings for each compiler version. - All the stuff that previously still was in all-packages.nix. * A relatively small part is left in all-packages.nix. svn path=/nixpkgs/trunk/; revision=34088
2012-05-14 15:09:05 +02:00
# Import Haskell infrastructure.
Added GHC HEAD snapshot. svn path=/nixpkgs/trunk/; revision=17227
2009-09-17 13:45:20 +02:00
haskellPackages: use static-enabled 'gmp' to enable statically linked Haskell binaries Pass '-optl-static -optl-pthread' to GHC to enable static linking. Fixes <https://github.com/NixOS/nixpkgs/issues/3193>. Further details can be found at <http://permalink.gmane.org/gmane.linux.distributions.nixos/13526>.
2014-07-06 13:37:46 +02:00
haskell = let pkgs_ = pkgs // { gmp = gmp.override { withStatic = true; }; };
callPackage = newScope pkgs_;
newScope = extra: lib.callPackageWith (pkgs_ // pkgs_.xorg // extra);
in callPackage ./haskell-defaults.nix { pkgs = pkgs_; inherit callPackage newScope; };
* adding ghc-6.8 even though it still segfaults on my machine (it's marked lowPrio for now, so it shouldn't break anything) svn path=/nixpkgs/trunk/; revision=9482
2007-10-19 15:24:29 +02:00
Restructured Haskell packages a bit. * There's a new file called haskell-defaults.nix. * The new file contains: - Default package version settings for each compiler version. - All the stuff that previously still was in all-packages.nix. * A relatively small part is left in all-packages.nix. svn path=/nixpkgs/trunk/; revision=34088
2012-05-14 15:09:05 +02:00
# Available GHC versions.
Make ghc-7.0.4 the default. Add experimental ghc-7.2.1rc1. svn path=/nixpkgs/trunk/; revision=28163
2011-08-05 10:52:35 +02:00
Added GHC HEAD snapshot. svn path=/nixpkgs/trunk/; revision=17227
2009-09-17 13:45:20 +02:00
# For several compiler versions, we export a large set of Haskell-related
# packages.
Disable recurseIntoAttrs for some GHC versions. svn path=/nixpkgs/trunk/; revision=28421
2011-08-09 13:10:24 +02:00
# NOTE (recurseIntoAttrs): After discussion, we originally decided to
# enable it for all GHC versions. However, this is getting too much,
# particularly in connection with Hydra builds for all these packages.
Build all ghcs on hydra
2014-03-27 03:46:05 +01:00
# So we enable it for selected versions only. We build all ghcs, though
ghc = recurseIntoAttrs (lib.mapAttrs' (name: value:
lib.nameValuePair (builtins.substring (builtins.stringLength "packages_") (builtins.stringLength name) name) value.ghc
) (lib.filterAttrs (name: value:
builtins.substring 0 (builtins.stringLength "packages_") name == "packages_"
) haskell));
Added ghc-6.10.3. svn path=/nixpkgs/trunk/; revision=15541
2009-05-10 23:04:58 +02:00
Switch default Haskell compiler to GHC 7.8.3.
2014-07-10 12:15:51 +02:00
haskellPackages = haskellPackages_ghc783;
Re-write the Haskell Platform out of haskell-defaults.nix. 1) Packages formerly called haskell-haskell-platform-ghcXYZ-VVVV.X.Y.Z are now called haskell-platform-VVVV.X.Y.Z. The latest version can be installed by running "nix-env -i haskell-platform". 2) The attributes haskellPackages_ghcXYZ.haskellPlatform no longer exist. Instead, we have attributes like haskellPlatformPackages."2012_4_0_0". (The last numeric bit must be quoted when used in a Nix file, but not on the command line to nix-env, nix-build, etc.) The latest Platform has a top-level alias called simply haskellPlatform. 3) The haskellPackages_ghcXYZ package sets offer the latest version of every library that GHC x.y.z can compile. For example, if 2.7 is the latest version of QuickCheck and if GHC 7.0.4 can compile that version, then haskellPackages_ghc704.QuickCheck refers to version 2.7. 4) All intermediate GHC releases were dropped from all-packages.nix to simplify our configuration. What remains is a haskellPackages_ghcXYZ set for the latest version of every major release branch, i.e. GHC 6.10.4, 6.12.3, 7.0.4, 7.2.2, 7.4.2, 7.6.3, 7.8.2, and 7.9.x (HEAD snapshot). 5) The ghcXYZPrefs functions in haskell-defaults.nix now inherit overrides from newer to older compilers, i.e. an override configured for GHC 7.0.4 will automatically apply to GHC 6.12.3 and 6.10.4, too. This change has reduced the redundancy in those configuration functions. The downside is that overriding an attribute for only one particular GHC version has become more difficult. In practice, this case doesn't occur much, though. 6) The 'cabal' builder has a brand-new argument called 'extension'. That function is "self : super : {}" by default and users can override it to mess with the attribute set passed to cabal.mkDerivation. An example use would be the definition of darcs in all-packages.nix: | darcs = haskellPackages.darcs.override { | cabal = haskellPackages.cabal.override { | extension = self : super : { | isLibrary = false; | configureFlags = "-f-library " + super.configureFlags or ""; | }; | }; | }; In this case, extension disables building the library part of the package to give us an executable-only version that has no dependencies on GHC or any other Haskell packages. The 'self' argument refers to the final version of the attribute set and 'super' refers to the original attribute set. Note that ... - Haskell Platform packages always provide the Haddock binary that came with the compiler. - Haskell Platform 2009.2.0.2 is broken because of build failures in cgi and cabal-install. - Haskell Platform 2010.1.0.0 is broken becasue of build failures in cgi.
2014-05-07 19:36:45 +02:00
haskellPlatform = haskellPlatformPackages."2013_2_0_0";
Added GHC 7.2.2. svn path=/nixpkgs/trunk/; revision=30398
2011-11-12 23:19:03 +01:00
all-packages.nix: cosmetic, no functional change
2013-12-02 20:58:56 +01:00
haskellPackages_ghc6104 = haskell.packages_ghc6104;
haskellPackages_ghc6123 = haskell.packages_ghc6123;
haskellPackages_ghc704 = haskell.packages_ghc704;
haskellPackages_ghc722 = haskell.packages_ghc722;
haskellPackages_ghc742 = haskell.packages_ghc742;
Switch default Haskell compiler to GHC 7.8.3.
2014-07-10 12:15:51 +02:00
haskellPackages_ghc763 = haskell.packages_ghc763;
haskellPackages_ghc783_no_profiling = recurseIntoAttrs haskell.packages_ghc783.noProfiling;
haskellPackages_ghc783_profiling = recurseIntoAttrs haskell.packages_ghc783.profiling;
haskellPackages_ghc783 = recurseIntoAttrs haskell.packages_ghc783.highPrio;
all-packages.nix: cosmetic, no functional change
2013-12-02 20:58:56 +01:00
haskellPackages_ghcHEAD = haskell.packages_ghcHEAD;
Added GHC HEAD snapshot. svn path=/nixpkgs/trunk/; revision=17227
2009-09-17 13:45:20 +02:00
Re-write the Haskell Platform out of haskell-defaults.nix. 1) Packages formerly called haskell-haskell-platform-ghcXYZ-VVVV.X.Y.Z are now called haskell-platform-VVVV.X.Y.Z. The latest version can be installed by running "nix-env -i haskell-platform". 2) The attributes haskellPackages_ghcXYZ.haskellPlatform no longer exist. Instead, we have attributes like haskellPlatformPackages."2012_4_0_0". (The last numeric bit must be quoted when used in a Nix file, but not on the command line to nix-env, nix-build, etc.) The latest Platform has a top-level alias called simply haskellPlatform. 3) The haskellPackages_ghcXYZ package sets offer the latest version of every library that GHC x.y.z can compile. For example, if 2.7 is the latest version of QuickCheck and if GHC 7.0.4 can compile that version, then haskellPackages_ghc704.QuickCheck refers to version 2.7. 4) All intermediate GHC releases were dropped from all-packages.nix to simplify our configuration. What remains is a haskellPackages_ghcXYZ set for the latest version of every major release branch, i.e. GHC 6.10.4, 6.12.3, 7.0.4, 7.2.2, 7.4.2, 7.6.3, 7.8.2, and 7.9.x (HEAD snapshot). 5) The ghcXYZPrefs functions in haskell-defaults.nix now inherit overrides from newer to older compilers, i.e. an override configured for GHC 7.0.4 will automatically apply to GHC 6.12.3 and 6.10.4, too. This change has reduced the redundancy in those configuration functions. The downside is that overriding an attribute for only one particular GHC version has become more difficult. In practice, this case doesn't occur much, though. 6) The 'cabal' builder has a brand-new argument called 'extension'. That function is "self : super : {}" by default and users can override it to mess with the attribute set passed to cabal.mkDerivation. An example use would be the definition of darcs in all-packages.nix: | darcs = haskellPackages.darcs.override { | cabal = haskellPackages.cabal.override { | extension = self : super : { | isLibrary = false; | configureFlags = "-f-library " + super.configureFlags or ""; | }; | }; | }; In this case, extension disables building the library part of the package to give us an executable-only version that has no dependencies on GHC or any other Haskell packages. The 'self' argument refers to the final version of the attribute set and 'super' refers to the original attribute set. Note that ... - Haskell Platform packages always provide the Haddock binary that came with the compiler. - Haskell Platform 2009.2.0.2 is broken because of build failures in cgi and cabal-install. - Haskell Platform 2010.1.0.0 is broken becasue of build failures in cgi.
2014-05-07 19:36:45 +02:00
haskellPlatformPackages = recurseIntoAttrs (import ../development/libraries/haskell/haskell-platform { inherit pkgs; });
haxe: Rewrite package from scratch, version 2.10. As well as for neko, we now have way less cruft within the mkDerivation attribute set. We also now use make to build haxe, which will include haxelib and haxedoc as well. The main reason why I was doing this was because the package didn't build and still was referencing mawercer.de, which does not contain those tarballs anymore. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-10-07 11:24:51 +02:00
haxe = callPackage ../development/compilers/haxe { };
adding haxe svn path=/nixpkgs/trunk/; revision=18708
2009-11-30 02:05:04 +01:00
Add HHVM packages, replacing old hiphop-php expr Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-10 13:12:12 +02:00
hhvm = callPackage ../development/compilers/hhvm { };
Remove old hiphop-vm package Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-10 13:12:40 +02:00
hiphopvm = hhvm; /* Compatibility alias */
Add hiphopvm
2012-12-02 15:24:28 +01:00
Adding Falcon multiparadigm programming language. It has macros and non-trivial syntax at once, which seems interesting in itself.. svn path=/nixpkgs/trunk/; revision=16299
2009-07-10 00:30:19 +02:00
falcon = builderDefsPackage (import ../development/interpreters/falcon) {
inherit cmake;
};
Adding FSharp compiler svn path=/nixpkgs/trunk/; revision=33758
2012-04-12 13:39:40 +02:00
fsharp = callPackage ../development/compilers/fsharp {};
go: setting default to 1.1 I hope it won't break anything.
2013-05-21 23:21:03 +02:00
go_1_0 = callPackage ../development/compilers/go { };
* Add the Go Programming Language compiler. svn path=/nixpkgs/trunk/; revision=18348
2009-11-14 21:14:28 +01:00
Darwin support for Go 1.1 (close #952)
2013-09-10 14:47:43 +02:00
go_1_1 =
if stdenv.isDarwin then
callPackage ../development/compilers/go/1.1-darwin.nix { }
else
callPackage ../development/compilers/go/1.1.nix { };
Adding go 1.1 beta
2013-04-30 09:58:07 +02:00
Adding go 1.2. It doesn't include godoc anymore. I could reproduce this, building this package: http://code.google.com/p/go/issues/detail?id=6999
2013-12-23 09:43:19 +01:00
go_1_2 = callPackage ../development/compilers/go/1.2.nix { };
go 1.3 and darwin support
2014-06-23 05:28:16 +02:00
go_1_3 = callPackage ../development/compilers/go/1.3.nix { };
go = go_1_3;
go: setting default to 1.1 I hope it won't break anything.
2013-05-21 23:21:03 +02:00
Add gox and packer packages
2014-05-14 01:19:41 +02:00
gox = callPackage ../development/compilers/go/gox.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gprolog = callPackage ../development/compilers/gprolog { };
Add GNU Prolog. svn path=/nixpkgs/trunk/; revision=14122
2009-02-19 14:32:07 +01:00
add gwt 2.4.0, patch provided by TermNL svn path=/nixpkgs/trunk/; revision=31711
2012-01-19 20:31:25 +01:00
gwt240 = callPackage ../development/compilers/gwt/2.4.0.nix { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
icedtea7: New package Free Java environment based on OpenJDK 7.0 and the IcedTea project.
2014-03-16 03:37:53 +01:00
icedtea7_jdk = callPackage ../development/compilers/icedtea rec {
jdk = openjdk;
jdkPath = "${openjdk}/lib/openjdk";
} // { outputs = [ "out" ]; };
icedtea7_jre = (lib.setName "icedtea7-${lib.getVersion pkgs.icedtea7_jdk.jre}" (lib.addMetaAttrs
{ description = "Free Java runtime environment based on OpenJDK 7.0 and the IcedTea project"; }
pkgs.icedtea7_jdk.jre)) // { outputs = [ "jre" ]; };
icedtea7_web: New package Java web browser plugin and an implementation of Java Web Start.
2014-03-24 20:52:18 +01:00
icedtea7_web = callPackage ../development/compilers/icedtea-web {
jdk = "${icedtea7_jdk}/lib/icedtea";
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ikarus = callPackage ../development/compilers/ikarus { };
all-packages.nix changes for previous commits svn path=/nixpkgs/trunk/; revision=11758
2008-05-06 09:03:41 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hugs = callPackage ../development/compilers/hugs { };
hugs98 svn path=/nixpkgs/trunk/; revision=9169
2007-08-20 12:34:49 +02:00
Merging from trunk (the callPackage change) svn path=/nixpkgs/branches/stdenv-updates/; revision=22915
2010-08-03 10:14:13 +02:00
path64 = callPackage ../development/compilers/path64 { };
hugs98 svn path=/nixpkgs/trunk/; revision=9169
2007-08-20 12:34:49 +02:00
* Clean up the Ant name, e.g. "ant-openjdk-1.8.0RC1" instead of "ant-<JDK name>". * Remove openjdkDarwin/ecjDarwin/antDarwin attributes. Instead the openjdk attribute refers to the Darwin package on Darwin. svn path=/nixpkgs/trunk/; revision=34505
2012-06-13 16:11:52 +02:00
openjdk =
if stdenv.isDarwin then
callPackage ../development/compilers/openjdk-darwin { }
else
Make "nix-env -i openjdk" do the right thing
2012-11-29 11:31:38 +01:00
let
ant: Update to 1.9.3 Also, Ant no longer has a build-time dependency on a particular JDK. It finds the JDK via $JAVA_HOME or $PATH (by looking up javac). This way, we don't need to have separate packages like apacheAntOpenJDK and apacheAntOracleJDK. It also seems reasonable: after all, installing GNU Make doesn't give you a C compiler either. It does mean that instead of buildInputs = [ ant ]; you now need to write something like buildInputs = [ ant jdk ];
2014-01-03 13:29:06 +01:00
openjdkBootstrap = callPackage ../development/compilers/openjdk/bootstrap.nix { };
openjdk: Ugly hack to fix nix-env installation Nix-env always wants to install all outputs of a derivation, but this failed for openjdk/openjre because openjdk has some symlinks (such as bin/java) to openjre. Also, it prevents installing the openjre without the openjdk. So as a workaround, mess with the "outputs" attribute to fool nix-env. Also, give openjre a separate name and description. Fixes #1535.
2014-01-20 14:54:50 +01:00
in (callPackage ../development/compilers/openjdk {
openjdk: Build only once Since javac doesn't do much optimisation, bootstrapping twice is unlikely to produce a faster compiler.
2014-01-02 14:44:13 +01:00
jdk = openjdkBootstrap;
openjdk: Ugly hack to fix nix-env installation Nix-env always wants to install all outputs of a derivation, but this failed for openjdk/openjre because openjdk has some symlinks (such as bin/java) to openjre. Also, it prevents installing the openjre without the openjdk. So as a workaround, mess with the "outputs" attribute to fool nix-env. Also, give openjre a separate name and description. Fixes #1535.
2014-01-20 14:54:50 +01:00
}) // { outputs = [ "out" ]; };
Add openjdk to all-packages.nix svn path=/nixpkgs/trunk/; revision=28027
2011-08-01 03:07:47 +02:00
openjdk: Ugly hack to fix nix-env installation Nix-env always wants to install all outputs of a derivation, but this failed for openjdk/openjre because openjdk has some symlinks (such as bin/java) to openjre. Also, it prevents installing the openjre without the openjdk. So as a workaround, mess with the "outputs" attribute to fool nix-env. Also, give openjre a separate name and description. Fixes #1535.
2014-01-20 14:54:50 +01:00
# FIXME: Need a way to set per-output meta attributes.
openjre = (lib.setName "openjre-${lib.getVersion pkgs.openjdk.jre}" (lib.addMetaAttrs
{ description = "The open-source Java Runtime Environment"; }
pkgs.openjdk.jre)) // { outputs = [ "jre" ]; };
Add openjre svn path=/nixpkgs/trunk/; revision=28117
2011-08-01 20:48:01 +02:00
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
jdk = if stdenv.isDarwin || stdenv.system == "i686-linux" || stdenv.system == "x86_64-linux"
openjdk: Don't use the official build system's boostrapping, do our own. The openjdk BOOT_CYCLE bootstrap doesn't use the binaries built in the first stage for the second stage, so we get a bunch of errors like: /bin/sh: /nix/store/wdgl7xl9b72hn212l0672ad5sn7vh44y-openjdk-bootstrap/bin/native2ascii: No such file or directory Instead, just build each stage as a separate derivation
2012-10-04 22:56:41 +02:00
then pkgs.openjdk
else pkgs.oraclejdk;
Make openjre default jre on darwin, just like jdk.
2014-06-25 14:19:02 +02:00
jre = if stdenv.isDarwin || stdenv.system == "i686-linux" || stdenv.system == "x86_64-linux"
openjdk: Don't use the official build system's boostrapping, do our own. The openjdk BOOT_CYCLE bootstrap doesn't use the binaries built in the first stage for the second stage, so we get a bunch of errors like: /bin/sh: /nix/store/wdgl7xl9b72hn212l0672ad5sn7vh44y-openjdk-bootstrap/bin/native2ascii: No such file or directory Instead, just build each stage as a separate derivation
2012-10-04 22:56:41 +02:00
then pkgs.openjre
else pkgs.oraclejre;
Update of jdk and jre to jdk-distros, based on Distributor License for Java. D pkgs/development/interpreters/jre Obsolete. jdk and jre are now build by the same expression. D pkgs/development/compilers/blackdown Obsolete. jdk is now downloadable. D pkgs/development/compilers/jdk/jdk5-sun-linux.nix Obsolete A pkgs/development/compilers/jdk/dlj-bundle-builder.sh Build for DLJ bundles. M pkgs/top-level/all-packages.nix Dropped blackdown and ant based on blackdown. A pkgs/development/compilers/jdk/jdk6-construct.sh Copy of DLJ construct script to fix problem with jdk6 bundles. A pkgs/development/compilers/jdk/jdk6-linux.nix New main Nix expression for jdk and jre. Supports mozillaPlugin. A pkgs/development/compilers/jdk/dlj-bundle-builder.sh Include path to libjli in rpath. svn path=/nixpkgs/trunk/; revision=8186
2007-03-05 18:13:53 +01:00
openjdk: Don't use the official build system's boostrapping, do our own. The openjdk BOOT_CYCLE bootstrap doesn't use the binaries built in the first stage for the second stage, so we get a bunch of errors like: /bin/sh: /nix/store/wdgl7xl9b72hn212l0672ad5sn7vh44y-openjdk-bootstrap/bin/native2ascii: No such file or directory Instead, just build each stage as a separate derivation
2012-10-04 22:56:41 +02:00
oraclejdk = pkgs.jdkdistro true false;
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
Add oracle jdk 7 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-09 17:37:03 +01:00
oraclejdk7 = pkgs.oraclejdk7distro true false;
add oraclejdk8
2014-05-11 12:13:52 +02:00
oraclejdk8 = pkgs.oraclejdk8distro true false;
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
oraclejre = lowPrio (pkgs.jdkdistro false false);
jre: by default don't support the plugin svn path=/nixpkgs/trunk/; revision=8461
2007-03-28 20:55:57 +02:00
oraclejre7: Add package (as a variant of oraclejdk7)
2014-01-01 21:13:05 +01:00
oraclejre7 = lowPrio (pkgs.oraclejdk7distro false false);
add oraclejdk8
2014-05-11 12:13:52 +02:00
oraclejre8 = lowPrio (pkgs.oraclejdk8distro false false);
openjdk: Don't use the official build system's boostrapping, do our own. The openjdk BOOT_CYCLE bootstrap doesn't use the binaries built in the first stage for the second stage, so we get a bunch of errors like: /bin/sh: /nix/store/wdgl7xl9b72hn212l0672ad5sn7vh44y-openjdk-bootstrap/bin/native2ascii: No such file or directory Instead, just build each stage as a separate derivation
2012-10-04 22:56:41 +02:00
jrePlugin = lowPrio (pkgs.jdkdistro false true);
Make jdk plugin support optional to avoid deps on gcc 3.3.6 everywhere. svn path=/nixpkgs/trunk/; revision=8452
2007-03-28 17:21:43 +02:00
* Fix the JRE plugin test. svn path=/nixpkgs/trunk/; revision=8577
2007-04-16 12:22:20 +02:00
supportsJDK =
system == "i686-linux" ||
Remove a bunch of unreferenced files Plus a small number of obsolete packages (like old versions of qemu).
2012-11-29 13:43:37 +01:00
system == "x86_64-linux";
* Fix the JRE plugin test. svn path=/nixpkgs/trunk/; revision=8577
2007-04-16 12:22:20 +02:00
* In the JDK packages, don't return false if the platform is unsupported. This gives a type error ("value is a boolean while an attribute set was expected"). svn path=/nixpkgs/trunk/; revision=8576
2007-04-16 12:07:06 +02:00
jdkdistro = installjdk: pluginSupport:
Remove a bunch of unreferenced files Plus a small number of obsolete packages (like old versions of qemu).
2012-11-29 13:43:37 +01:00
assert supportsJDK;
Make appendToName do the right thing I.e. append a suffix *before* the version, rather than after. So we get "sqlite-interactive-3.8.0.2" instead of "sqlite-3.8.0.2-interactive". The latter is broken since nix-env just sees it the suffix as part of the version, so "nix-env -u" will happily upgrade "sqlite-3.8.0.2-interactive" to "sqlite-3.9".
2014-03-10 15:01:56 +01:00
(if pluginSupport then appendToName "with-plugin" else x: x)
Move jdk -> oraclejdk
2014-07-16 18:35:35 +02:00
(callPackage ../development/compilers/oraclejdk/jdk6-linux.nix { });
* Added some missing semicolons. * Some packages needed for the Subversion server. svn path=/nixpkgs/trunk/; revision=586
2003-12-21 21:52:13 +01:00
Add oracle jdk 7 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-09 17:37:03 +01:00
oraclejdk7distro = installjdk: pluginSupport:
assert supportsJDK;
Make appendToName do the right thing I.e. append a suffix *before* the version, rather than after. So we get "sqlite-interactive-3.8.0.2" instead of "sqlite-3.8.0.2-interactive". The latter is broken since nix-env just sees it the suffix as part of the version, so "nix-env -u" will happily upgrade "sqlite-3.8.0.2-interactive" to "sqlite-3.9".
2014-03-10 15:01:56 +01:00
(if pluginSupport then appendToName "with-plugin" else x: x)
Move jdk -> oraclejdk
2014-07-16 18:35:35 +02:00
(callPackage ../development/compilers/oraclejdk/jdk7-linux.nix { inherit installjdk; });
Add oracle jdk 7 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-09 17:37:03 +01:00
add oraclejdk8
2014-05-11 12:13:52 +02:00
oraclejdk8distro = installjdk: pluginSupport:
assert supportsJDK;
(if pluginSupport then appendToName "with-plugin" else x: x)
Move jdk -> oraclejdk
2014-07-16 18:35:35 +02:00
(callPackage ../development/compilers/oraclejdk/jdk8-linux.nix { inherit installjdk; });
Add oracle jdk 7 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-09 17:37:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jikes = callPackage ../development/compilers/jikes { };
Added j2sdk-1.5.0-beta svn path=/nixpkgs/trunk/; revision=1014
2004-05-12 17:06:23 +02:00
add julia 0.2.1 release
2014-03-28 11:39:26 +01:00
juliaGit = callPackage ../development/compilers/julia/git-20131013.nix {
Julia language: update to a fresh version Update julia and some of its dependencies Split PCRE because a lot of packages depend on it and I am not sure we want to test them in a hurry (and Julia specifies exact version).
2012-08-01 17:03:52 +02:00
liblapack = liblapack.override {shared = true;};
llvm: Split llvmFull into separate derivations Now most packages in the llvm suite are built as separate derivations. The exceptions are: * compiler-rt must currently be built with llvm. This increases llvm's size by 6 MB * clang-tools-extra must be built with clang In addition, the top-level llvm attribute is defaulted to llvm 3.4, and llvm 3.3 must be accessed by the llvm_33 attribute. This is to make the out-of-date packages obvious in the hope that eventually all will be updated to work with 3.4 and 3.3 can be removed. I think we should keep this policy in the future (latest llvm gets top-level name, the rest are versioned until they can be removed). The llvm packages (except libc++, which exception I will try to remove on the next update) can all be accessed via the llvmPackages attribute, and there are also aliases for the packages that already existed (llvm, clang, and dragonegg). Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 02:19:53 +01:00
llvm = llvm_33;
openblas: pin all the versions julia requires
2014-08-28 23:07:30 +02:00
openblas = openblas_0_2_2;
Julia language: update to a fresh version Update julia and some of its dependencies Split PCRE because a lot of packages depend on it and I am not sure we want to test them in a hurry (and Julia specifies exact version).
2012-08-01 17:03:52 +02:00
};
add julia 0.2.1 release
2014-03-28 11:39:26 +01:00
julia021 = callPackage ../development/compilers/julia/0.2.1.nix {
liblapack = liblapack.override {shared = true;};
llvm = llvm_33;
openblas: pin all the versions julia requires
2014-08-28 23:07:30 +02:00
openblas = openblas_0_2_2;
add julia 0.2.1 release
2014-03-28 11:39:26 +01:00
};
Adding Julia 0.3.0: some progress, but doesn't work yet
2014-08-21 20:09:39 +02:00
julia030 = let
liblapack = liblapack_3_5_0.override {shared = true;};
in callPackage ../development/compilers/julia/0.3.0.nix {
inherit liblapack;
suitesparse = suitesparse.override {
inherit liblapack;
};
llvm = llvm_34;
openblas: pin all the versions julia requires
2014-08-28 23:07:30 +02:00
openblas = openblas_0_2_10;
Adding Julia 0.3.0: some progress, but doesn't work yet
2014-08-21 20:09:39 +02:00
};
Julia 0.3.0 seems to have no more problems than 0.2.1, so make it default
2014-08-30 22:37:01 +02:00
julia = julia030;
Adding Julia programming language svn path=/nixpkgs/trunk/; revision=33614
2012-04-05 14:22:55 +02:00
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
lazarus = builderDefsPackage (import ../development/compilers/fpc/lazarus.nix) {
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit makeWrapper gtk glib pango atk gdk_pixbuf;
Added Lazarus IDE for Free Pascal Compiler. svn path=/nixpkgs/trunk/; revision=11492
2008-04-08 17:11:34 +02:00
inherit (xlibs) libXi inputproto libX11 xproto libXext xextproto;
Update Lazarus svn path=/nixpkgs/trunk/; revision=27302
2011-05-25 11:04:54 +02:00
fpc = fpc;
Added Lazarus IDE for Free Pascal Compiler. svn path=/nixpkgs/trunk/; revision=11492
2008-04-08 17:11:34 +02:00
};
New package: lessc, version 1.4.0 Compiles LESS to CSS
2013-07-01 15:39:39 +02:00
lessc = callPackage ../development/compilers/lessc { };
llvm(Packages) on darwin: attempts to fix - mark llvm34 as broken on darwin (so it doesn't install by default with nix-env) - don't use our gcc for llvm_34 (might fix the build) - switch also clang default to 3.3 on darwin (llvm was before)
2014-04-10 21:19:40 +02:00
llvm = llvmPackages.llvm;
llvm: Enable also building of LLVM 3.[12] & Clang 3.[123].
2014-01-26 20:42:12 +01:00
llvm(Packages) on darwin: attempts to fix - mark llvm34 as broken on darwin (so it doesn't install by default with nix-env) - don't use our gcc for llvm_34 (might fix the build) - switch also clang default to 3.3 on darwin (llvm was before)
2014-04-10 21:19:40 +02:00
llvm_34 = llvmPackages_34.llvm;
llvm: Enable also building of LLVM 3.[12] & Clang 3.[123].
2014-01-26 20:42:12 +01:00
llvm_33 = llvm_v ../development/compilers/llvm/3.3/llvm.nix;
llvm_v = path: callPackage path {
Hack to fix llvm/clang build on Darwin (Or at least restore it to the same level as brokenness as before the staging merge. I.e. it depends on gcc-apple, which doesn't build on standard 10.9 systems.)
2014-08-09 23:31:00 +02:00
stdenv = if stdenv.isDarwin then stdenvApple else stdenv;
llvm: fix build on darwin
2013-01-22 21:17:09 +01:00
};
llvm: Enable also building of LLVM 3.[12] & Clang 3.[123].
2014-01-26 20:42:12 +01:00
ugly tarball fix for llvmPackages support on Darwin
2014-04-11 21:28:34 +02:00
llvmPackages = if !stdenv.isDarwin then llvmPackages_34 else llvmPackages_34 // {
llvm(Packages) on darwin: attempts to fix - mark llvm34 as broken on darwin (so it doesn't install by default with nix-env) - don't use our gcc for llvm_34 (might fix the build) - switch also clang default to 3.3 on darwin (llvm was before)
2014-04-10 21:19:40 +02:00
# until someone solves build problems with _34
llvm = llvm_33;
clang = clang_33;
};
ugly tarball fix for llvmPackages support on Darwin
2014-04-11 21:28:34 +02:00
llvm(Packages) on darwin: attempts to fix - mark llvm34 as broken on darwin (so it doesn't install by default with nix-env) - don't use our gcc for llvm_34 (might fix the build) - switch also clang default to 3.3 on darwin (llvm was before)
2014-04-10 21:19:40 +02:00
llvmPackages_34 = recurseIntoAttrs (import ../development/compilers/llvm/3.4 {
inherit stdenv newScope fetchurl;
llvm: Attempt to fix build on darwin Signed-off-by: Shea Levy <shea@shealevy.com>
2014-02-04 00:54:25 +01:00
isl = isl_0_12;
});
Don't include llvm self-built packages in nix-env -qa/nix-env -i Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 02:42:49 +01:00
llvmPackagesSelf = import ../development/compilers/llvm/3.4 { inherit newScope fetchurl; isl = isl_0_12; stdenv = libcxxStdenv; };
Attempts to get LLVM-gcc working are not yet succesful; but builder-defs updates are useful. svn path=/nixpkgs/trunk/; revision=11457
2008-04-02 21:55:40 +02:00
Add parallel functional compiler, Manticore
2014-08-19 08:36:57 +02:00
manticore = callPackage ../development/compilers/manticore { };
Add Sourcery CodeBench Lite toolchain(s) Sourcery CodeBench toolchains are prebuilt GCC toolchains from Mentor Graphics. Start out by adding ARM EABI and ARM GNU/Linux toolchains. Sourcery CodeBench is also available for MIPS, Power, SuperH, ColdFire (and more), so it should be easy to add later, if needed. AFAIK, the EABI toolchains use newlib and the GNU/Linux ones use glibc.
2013-04-15 22:47:01 +02:00
mentorToolchains = recurseIntoAttrs (
callPackage_i686 ../development/compilers/mentor {}
);
Add the Mercury compiler to nixpkgs.
2014-05-14 21:45:34 +02:00
mercury = callPackage ../development/compilers/mercury { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mitscheme = callPackage ../development/compilers/mit-scheme { };
Add MIT/GNU Scheme. svn path=/nixpkgs/trunk/; revision=20719
2010-03-17 16:32:12 +01:00
Add package mlton, an optimizing compiler for Standard ML. This commit packages mlton. Note that the documentation has not been built or included. svn path=/nixpkgs/trunk/; revision=23378
2010-08-24 10:23:16 +02:00
mlton = callPackage ../development/compilers/mlton { };
Add moderntimeline extension for moderncv.
2013-06-15 12:58:21 +02:00
mono = callPackage ../development/compilers/mono {
inherit (xlibs) libX11;
Added keepass password manager. Updated mono DLLMap to allow mono to run WinForms applications (keepass).
2013-06-09 23:17:09 +02:00
};
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
monoDLLFixer = callPackage ../build-support/mono-dll-fixer { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mozart = callPackage ../development/compilers/mozart { };
Added ViewMTN and dependency; currently ViewMTN has to be manually symlinked in corresponding directory. svn path=/nixpkgs/trunk/; revision=12060
2008-06-12 17:59:59 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
neko = callPackage ../development/compilers/neko { };
adding neko adding repository locations for haxe* and neko repositories svn path=/nixpkgs/trunk/; revision=18709
2009-11-30 02:05:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nasm = callPackage ../development/compilers/nasm { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
development/compilers/nvidia-cg-toolkit: New nixbuild. svn path=/nixpkgs/trunk/; revision=30395
2011-11-12 18:19:45 +01:00
nvidia_cg_toolkit = callPackage ../development/compilers/nvidia-cg-toolkit { };
Make OCaml 4.01.0 the default version of OCaml. Also change the ocaml attribute to always point to the one of the current ocamlPackages.
2014-01-29 08:46:12 +01:00
ocaml = ocamlPackages.ocaml;
- O'Caml compiler for Object CaML - hevea is an interpreter for latex producing html svn path=/nixpkgs/trunk/; revision=1171
2004-07-17 00:58:15 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ocaml_3_08_0 = callPackage ../development/compilers/ocaml/3.08.0.nix { };
* Make all ocaml versions available in the proper way. svn path=/nixpkgs/trunk/; revision=17805
2009-10-14 17:21:45 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ocaml_3_10_0 = callPackage ../development/compilers/ocaml/3.10.0.nix { };
* Make all ocaml versions available in the proper way. svn path=/nixpkgs/trunk/; revision=17805
2009-10-14 17:21:45 +02:00
Recovered OCaml 3.11 by using version 3.11.2 and a patch from ocaml's bugtracker. svn path=/nixpkgs/trunk/; revision=33399
2012-03-24 23:59:08 +01:00
ocaml_3_11_2 = callPackage ../development/compilers/ocaml/3.11.2.nix { };
Remove lowPrio to ocaml-3.12.1 svn path=/nixpkgs/trunk/; revision=33192
2012-03-17 16:03:12 +01:00
ocaml_3_12_1 = callPackage ../development/compilers/ocaml/3.12.1.nix { };
* Add ocaml 3.12.0 svn path=/nixpkgs/trunk/; revision=25040
2010-12-09 15:03:13 +01:00
OCaml 4.00.1
2012-10-08 00:05:48 +02:00
ocaml_4_00_1 = callPackage ../development/compilers/ocaml/4.00.1.nix { };
Adds Ocaml 4.00.0 (first attempt) Bumps Findlib to 1.3.3 (required for ocaml 4.00)
2012-07-30 18:08:06 +02:00
Add Ocaml 4.01.0. Close #1065.
2013-10-12 12:03:14 +02:00
ocaml_4_01_0 = callPackage ../development/compilers/ocaml/4.01.0.nix { };
add orc 0.4.17
2013-08-11 05:00:45 +02:00
orc = callPackage ../development/compilers/orc { };
adding two versions of metaocaml svn path=/nixpkgs/trunk/; revision=31026
2011-12-21 22:51:35 +01:00
metaocaml_3_09 = callPackage ../development/compilers/ocaml/metaocaml-3.09.nix { };
ber_metaocaml_003 = callPackage ../development/compilers/ocaml/ber-metaocaml-003.nix { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
mkOcamlPackages = ocaml: self: let callPackage = newScope self; in rec {
inherit ocaml;
New package for CamlIDL 1.05 svn path=/nixpkgs/trunk/; revision=29619
2011-10-04 03:40:45 +02:00
camlidl = callPackage ../development/tools/ocaml/camlidl { };
Upgrade camlp5 to version 6.02.3-1 (contributed by Russell O'Connor). Keep the old version 5.15 to allow a smooth migration. svn path=/nixpkgs/trunk/; revision=30575
2011-11-26 20:39:14 +01:00
camlp5_5_strict = callPackage ../development/tools/ocaml/camlp5/5.15.nix { };
* Update camlp5 svn path=/nixpkgs/trunk/; revision=25206
2010-12-20 11:32:22 +01:00
Upgrade camlp5 to version 6.02.3-1 (contributed by Russell O'Connor). Keep the old version 5.15 to allow a smooth migration. svn path=/nixpkgs/trunk/; revision=30575
2011-11-26 20:39:14 +01:00
camlp5_5_transitional = callPackage ../development/tools/ocaml/camlp5/5.15.nix {
* Update camlp5 svn path=/nixpkgs/trunk/; revision=25206
2010-12-20 11:32:22 +01:00
transitional = true;
};
Upgrade camlp5 to version 6.02.3-1 (contributed by Russell O'Connor). Keep the old version 5.15 to allow a smooth migration. svn path=/nixpkgs/trunk/; revision=30575
2011-11-26 20:39:14 +01:00
camlp5_6_strict = callPackage ../development/tools/ocaml/camlp5 { };
camlp5_6_transitional = callPackage ../development/tools/ocaml/camlp5 {
transitional = true;
};
camlp5_strict = camlp5_6_strict;
camlp5_transitional = camlp5_6_transitional;
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
camlzip = callPackage ../development/ocaml-modules/camlzip { };
Update ocaml_batteries and camomile (ocamlPackages) * Add camomile 0.8.3 and 0.8.2 (for ocaml_batteries). * Remove obsolete camomile 0.7.3 and 0.8.1. * Update ocaml_batteries to version 1.3.0 (also add fixes for Darwin). svn path=/nixpkgs/trunk/; revision=27299
2011-05-24 20:21:13 +02:00
camomile_0_8_2 = callPackage ../development/ocaml-modules/camomile/0.8.2.nix { };
camomile = callPackage ../development/ocaml-modules/camomile { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
camlimages = callPackage ../development/ocaml-modules/camlimages {
libpng = libpng12;
Use old giflib for packages which lack new versions/compatibility patches for giflib5
2013-12-08 11:36:46 +01:00
giflib = giflib_4_1;
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
};
New ocaml packages: - ocaml-cairo - camlimages - dypgen - patoline
2013-06-04 20:49:10 +02:00
Adds biniou
2014-07-03 11:09:47 +02:00
biniou = callPackage ../development/ocaml-modules/biniou { };
New ocaml packages: - ocaml-cairo - camlimages - dypgen - patoline
2013-06-04 20:49:10 +02:00
ocaml_cairo = callPackage ../development/ocaml-modules/ocaml-cairo { };
Adds ocaml-cmdliner Cmdliner is an OCaml module for the declarative definition of command line interfaces. Homepage: http://erratique.ch/software/cmdliner
2014-08-22 14:43:23 +02:00
cmdliner = callPackage ../development/ocaml-modules/cmdliner { };
Adds cppo
2014-06-25 10:25:14 +02:00
cppo = callPackage ../development/tools/ocaml/cppo { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
cryptokit = callPackage ../development/ocaml-modules/cryptokit { };
Adds ocaml library “csv” This is a pure OCaml library to read and write CSV files, including all extensions used by Excel — eg. quotes, newlines, 8 bit characters in fields, "0 etc. Homepage: https://forge.ocamlcore.org/projects/csv/
2014-08-17 00:31:35 +02:00
csv = callPackage ../development/ocaml-modules/csv { };
ocaml adding deriving
2013-06-17 12:33:25 +02:00
deriving = callPackage ../development/tools/ocaml/deriving { };
Adds easy-format
2014-06-25 14:08:12 +02:00
easy-format = callPackage ../development/ocaml-modules/easy-format { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
findlib = callPackage ../development/tools/ocaml/findlib { };
Adds javalib and sawja Javalib is a library that parses Java .class files into OCaml data structures. Sawja is a library written in OCaml, relying on Javalib to provide a high level representation of Java bytecode programs. Homepage: http://sawja.inria.fr/
2014-07-06 17:41:40 +02:00
javalib = callPackage ../development/ocaml-modules/javalib {
extlib = ocaml_extlib_maximal;
};
New ocaml packages: - ocaml-cairo - camlimages - dypgen - patoline
2013-06-04 20:49:10 +02:00
dypgen = callPackage ../development/ocaml-modules/dypgen { };
patoline = callPackage ../tools/typesetting/patoline { };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
gmetadom = callPackage ../development/ocaml-modules/gmetadom { };
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
New ocaml packages: - ocaml-cairo - camlimages - dypgen - patoline
2013-06-04 20:49:10 +02:00
lablgl = callPackage ../development/ocaml-modules/lablgl { };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
lablgtk = callPackage ../development/ocaml-modules/lablgtk {
inherit (gnome) libgnomecanvas libglade gtksourceview;
};
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
lablgtkmathview = callPackage ../development/ocaml-modules/lablgtkmathview {
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
gtkmathview = callPackage ../development/libraries/gtkmathview { };
* Update lablgtk2 (and enable hydra build) svn path=/nixpkgs/trunk/; revision=25213
2010-12-20 15:58:56 +01:00
};
add the ocaml 'lambda-term' library (terminal control)
2014-07-20 18:22:16 +02:00
lambdaTerm = callPackage ../development/ocaml-modules/lambda-term { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
menhir = callPackage ../development/ocaml-modules/menhir { };
Adds merlin Merlin is an editor-independant tool to ease the developpement of programs in OCaml. It aims to provide features available in modern IDEs. Homepage: http://the-lambda-church.github.io/merlin/
2014-07-05 17:29:21 +02:00
merlin = callPackage ../development/tools/ocaml/merlin { };
ocaml: native code building for ARM on 3.12 and 4.00 I think it already works. I'll test more throughly tomorrow.
2012-09-23 23:56:48 +02:00
mldonkey = callPackage ../applications/networking/p2p/mldonkey { };
Added OCaml gmp bindings mlgmp
2013-06-16 22:23:51 +02:00
mlgmp = callPackage ../development/ocaml-modules/mlgmp { };
Update OCaml Batteries to version 2.2.0
2014-01-29 17:52:53 +01:00
ocaml_batteries = callPackage ../development/ocaml-modules/batteries { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
ocaml_cryptgps = callPackage ../development/ocaml-modules/cryptgps { };
Add OCaml Oasis OCaml Oasis is a configure/build/install system for OCaml proget (like Cabal for Haskell). This commit also add a few small dependencies that where missing - OCaml Data Notation (odn) - ocamlify - ocamlmod
2014-01-31 06:44:42 +01:00
ocaml_data_notation = callPackage ../development/ocaml-modules/odn { };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
ocaml_expat = callPackage ../development/ocaml-modules/expat { };
Add OPA to Nixpkgs. svn path=/nixpkgs/trunk/; revision=30578
2011-11-28 00:58:46 +01:00
ocamlgraph = callPackage ../development/ocaml-modules/ocamlgraph { };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
ocaml_http = callPackage ../development/ocaml-modules/http { };
Add OCaml Oasis OCaml Oasis is a configure/build/install system for OCaml proget (like Cabal for Haskell). This commit also add a few small dependencies that where missing - OCaml Data Notation (odn) - ocamlify - ocamlmod
2014-01-31 06:44:42 +01:00
ocamlify = callPackage ../development/tools/ocaml/ocamlify { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
ocaml_lwt = callPackage ../development/ocaml-modules/lwt { };
Add OCaml Oasis OCaml Oasis is a configure/build/install system for OCaml proget (like Cabal for Haskell). This commit also add a few small dependencies that where missing - OCaml Data Notation (odn) - ocamlify - ocamlmod
2014-01-31 06:44:42 +01:00
ocamlmod = callPackage ../development/tools/ocaml/ocamlmod { };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
ocaml_mysql = callPackage ../development/ocaml-modules/mysql { };
* Add ocamlnet svn path=/nixpkgs/trunk/; revision=25072
2010-12-12 18:53:13 +01:00
ocamlnet = callPackage ../development/ocaml-modules/ocamlnet { };
Add OCaml Oasis OCaml Oasis is a configure/build/install system for OCaml proget (like Cabal for Haskell). This commit also add a few small dependencies that where missing - OCaml Data Notation (odn) - ocamlify - ocamlmod
2014-01-31 06:44:42 +01:00
ocaml_oasis = callPackage ../development/tools/ocaml/oasis { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
ocaml_pcre = callPackage ../development/ocaml-modules/pcre {
inherit pcre;
};
ocaml_react = callPackage ../development/ocaml-modules/react { };
added OCaml package ocamlsdl
2013-12-05 16:20:32 +01:00
ocamlsdl= callPackage ../development/ocaml-modules/ocamlsdl { };
* Add ocaml-sqlite3 svn path=/nixpkgs/trunk/; revision=25065
2010-12-11 16:05:26 +01:00
ocaml_sqlite3 = callPackage ../development/ocaml-modules/sqlite3 { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
ocaml_ssl = callPackage ../development/ocaml-modules/ssl { };
Add a derivation for ocaml-text
2014-05-15 11:02:32 +02:00
ocaml_text = callPackage ../development/ocaml-modules/ocaml-text { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
ounit = callPackage ../development/ocaml-modules/ounit { };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
Add OPA to Nixpkgs. svn path=/nixpkgs/trunk/; revision=30578
2011-11-28 00:58:46 +01:00
ulex = callPackage ../development/ocaml-modules/ulex { };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
ulex08 = callPackage ../development/ocaml-modules/ulex/0.8 {
Reparing stable build of Matita. Also correcting the version and simplifying the prerelease package of Matita. svn path=/nixpkgs/trunk/; revision=33420
2012-03-25 23:27:30 +02:00
camlp5 = camlp5_transitional;
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
};
Updated the coccinelle package to the latest release (1.0.0-RC9). Added additional ocaml modules which are needed for coccinelle. svn path=/nixpkgs/trunk/; revision=31579
2012-01-16 11:20:13 +01:00
ocaml_typeconv = callPackage ../development/ocaml-modules/typeconv { };
Update OCaml Type_conv to version 109.60.01. Also keep the old version 3.0.5 around for compatibility with OCaml 3.12.1.
2014-01-29 22:09:29 +01:00
ocaml_typeconv_3_0_5 = callPackage ../development/ocaml-modules/typeconv/3.0.5.nix { };
Updated the coccinelle package to the latest release (1.0.0-RC9). Added additional ocaml modules which are needed for coccinelle. svn path=/nixpkgs/trunk/; revision=31579
2012-01-16 11:20:13 +01:00
ocaml_sexplib = callPackage ../development/ocaml-modules/sexplib { };
ocaml_extlib = callPackage ../development/ocaml-modules/extlib { };
Adds javalib and sawja Javalib is a library that parses Java .class files into OCaml data structures. Sawja is a library written in OCaml, relying on Javalib to provide a high level representation of Java bytecode programs. Homepage: http://sawja.inria.fr/
2014-07-06 17:41:40 +02:00
ocaml_extlib_maximal = callPackage ../development/ocaml-modules/extlib {
minimal = false;
};
Updated the coccinelle package to the latest release (1.0.0-RC9). Added additional ocaml modules which are needed for coccinelle. svn path=/nixpkgs/trunk/; revision=31579
2012-01-16 11:20:13 +01:00
pycaml = callPackage ../development/ocaml-modules/pycaml { };
Add opam 0.9.4
2013-03-08 11:56:50 +01:00
Opam: Update to 1.1.0 Also keeps 1.0 for backwards compatibility. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-12-17 23:16:38 +01:00
opam_1_0_0 = callPackage ../development/tools/ocaml/opam/1.0.0.nix { };
Opam 1.1: Constrain supported ocaml versions. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-12-25 14:43:23 +01:00
opam_1_1 = callPackage ../development/tools/ocaml/opam/1.1.nix { };
Opam: Update to 1.1.0 Also keeps 1.0 for backwards compatibility. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-12-17 23:16:38 +01:00
opam = opam_1_1;
ocaml-packages: add zarith 1.2.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-01 09:26:35 +02:00
Adds ocaml-sqlite3EZ and its dependency ocaml+twt ocaml+twt is an alternative syntax for OCaml that uses indentation to group multi-line expressions, like Python and Haskell. Homepage: http://people.csail.mit.edu/mikelin/ocaml+twt/ sqlite3EZ is a thin wrapper for sqlite3-ocaml with a simplified interface. Query results are processed with a functional map/fold, transactions are aborted by exceptions, resource management is handled by the garbage collector, etc. Homepage: https://github.com/mlin/ocaml-sqlite3EZ
2014-08-21 15:24:43 +02:00
sqlite3EZ = callPackage ../development/ocaml-modules/sqlite3EZ { };
twt = callPackage ../development/ocaml-modules/twt { };
add utop (improved ocaml toplevel)
2014-07-20 18:23:42 +02:00
utop = callPackage ../development/tools/ocaml/utop { };
Adds javalib and sawja Javalib is a library that parses Java .class files into OCaml data structures. Sawja is a library written in OCaml, relying on Javalib to provide a high level representation of Java bytecode programs. Homepage: http://sawja.inria.fr/
2014-07-06 17:41:40 +02:00
sawja = callPackage ../development/ocaml-modules/sawja { };
Adds OCaml libraries: uucd, uunf, uutf and xmlm Four OCaml libraries contributed by Daniel Bünzli for unicode and xml processing. - xmlm: Streaming XML codec for OCaml - uutf: Non-blocking streaming Unicode codec for OCaml - uunf: Unicode text normalization for OCaml - uucd: Unicode character database decoder for Ocaml Homepage: http://erratique.ch/software
2014-07-09 09:42:26 +02:00
uucd = callPackage ../development/ocaml-modules/uucd { };
uunf = callPackage ../development/ocaml-modules/uunf { };
uutf = callPackage ../development/ocaml-modules/uutf { };
xmlm = callPackage ../development/ocaml-modules/xmlm { };
Adds yojson. Yojson is an optimized parsing and printing OCaml library for the JSON format, contributed by Martin Jambon. Webpage: http://mjambon.com/yojson.html
2014-07-05 08:50:47 +02:00
yojson = callPackage ../development/ocaml-modules/yojson { };
ocaml-packages: add zarith 1.2.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-01 09:26:35 +02:00
zarith = callPackage ../development/ocaml-modules/zarith { };
add the 'zed' ocaml editor library
2014-07-20 18:21:14 +02:00
zed = callPackage ../development/ocaml-modules/zed { };
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
};
Make OCaml 4.01.0 the default version of OCaml. Also change the ocaml attribute to always point to the one of the current ocamlPackages.
2014-01-29 08:46:12 +01:00
ocamlPackages = recurseIntoAttrs ocamlPackages_4_01_0;
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
ocamlPackages_3_10_0 = mkOcamlPackages ocaml_3_10_0 pkgs.ocamlPackages_3_10_0;
Recovered OCaml 3.11 by using version 3.11.2 and a patch from ocaml's bugtracker. svn path=/nixpkgs/trunk/; revision=33399
2012-03-24 23:59:08 +01:00
ocamlPackages_3_11_2 = mkOcamlPackages ocaml_3_11_2 pkgs.ocamlPackages_3_11_2;
Add ocamlnat (native toplevel for OCaml) svn path=/nixpkgs/trunk/; revision=30926
2011-12-16 10:35:13 +01:00
ocamlPackages_3_12_1 = mkOcamlPackages ocaml_3_12_1 pkgs.ocamlPackages_3_12_1;
Fix evaluation http://hydra.nixos.org/build/3153986
2012-10-09 22:14:29 +02:00
ocamlPackages_4_00_1 = mkOcamlPackages ocaml_4_00_1 pkgs.ocamlPackages_4_00_1;
Add ocaml packages for version 4.01.0
2013-12-06 15:16:58 +01:00
ocamlPackages_4_01_0 = mkOcamlPackages ocaml_4_01_0 pkgs.ocamlPackages_4_01_0;
Create an attribute for latest ocaml packages even when this is not the default version
2014-02-02 16:48:07 +01:00
ocamlPackages_latest = ocamlPackages_4_01_0;
* Add ocaml packages findlib, camlzip, ocaml-ssl, ocaml-batteries, menhir, camomile, ocaml-lwt, cryptokit, ocaml-cryptgps, ounit, ocaml-react svn path=/nixpkgs/trunk/; revision=25041
2010-12-09 16:40:04 +01:00
Updated the coccinelle package to the latest release (1.0.0-RC9). Added additional ocaml modules which are needed for coccinelle. svn path=/nixpkgs/trunk/; revision=31579
2012-01-16 11:20:13 +01:00
ocaml_make = callPackage ../development/ocaml-modules/ocamlmake { };
Update OpaLang; it still doesn't build for a mysterious reason: apparently the missing fields are actually defined…
2014-08-12 14:22:19 +02:00
opa = let callPackage = newScope pkgs.ocamlPackages_4_00_1; in callPackage ../development/compilers/opa { };
Add ocamlnat (native toplevel for OCaml) svn path=/nixpkgs/trunk/; revision=30926
2011-12-16 10:35:13 +01:00
ocamlnat = let callPackage = newScope pkgs.ocamlPackages_3_12_1; in callPackage ../development/ocaml-modules/ocamlnat { };
Opa does not compile with ocaml before version 3.12.0 svn path=/nixpkgs/trunk/; revision=30584
2011-11-28 16:52:46 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
qcmm = callPackage ../development/compilers/qcmm {
fixed ocaml/qcmm problem: -created separate nix expressions for ocaml-3.08.0 and ocaml 3.09.1 -ocam-3.09.1 is standard/default ocaml version (included by ocaml/default.nix) -created ocaml3080 in all-packages-generic.nix -qcmm now uses ocaml3080 instead of ocaml svn path=/nixpkgs/trunk/; revision=4935
2006-03-01 10:18:22 +01:00
lua = lua4;
* Make all ocaml versions available in the proper way. svn path=/nixpkgs/trunk/; revision=17805
2009-10-14 17:21:45 +02:00
ocaml = ocaml_3_08_0;
added version to uuagc added: noweb, lua-5.x, lua-4.x, mk, qc-- (as qcmm) svn path=/nixpkgs/trunk/; revision=4681
2006-02-02 18:07:07 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
roadsend = callPackage ../development/compilers/roadsend { };
added roadsend PHP-Compiler svn path=/nixpkgs/trunk/; revision=10550
2008-02-08 02:57:31 +01:00
rustc: rename rust to rustc, but keep rust attr name for backwards compat
2014-08-01 04:37:07 +02:00
rustc = callPackage ../development/compilers/rustc/0.11.nix {};
rustcMaster = callPackage ../development/compilers/rustc/head.nix {};
Adding afflib svn path=/nixpkgs/trunk/; revision=28129
2011-08-02 21:46:28 +02:00
rustc: rename rust to rustc, but keep rust attr name for backwards compat
2014-08-01 04:37:07 +02:00
rust = rustc;
Adding afflib svn path=/nixpkgs/trunk/; revision=28129
2011-08-02 21:46:28 +02:00
sbcl: use bootstrap binary on darwin
2014-06-26 07:06:25 +02:00
sbclBootstrap = callPackage ../development/compilers/sbcl/bootstrap.nix {};
sbcl = callPackage ../development/compilers/sbcl {
Give up for now: roll back SBCL to 1.2.0, as: 1.2.2 fails on i686; 1.2.1 fails everywhere
2014-08-04 17:56:53 +02:00
clisp = clisp;
Updating CLisp and adding SBCL. SBCL currently has to be symlinked to a writable directory (I am investigating a fix). CLisp 2.47 is somewhat incompatible with lots of software, so I added 2.44.1 as preserved version svn path=/nixpkgs/trunk/; revision=15806
2009-05-31 08:07:25 +02:00
};
scala: add expression for scala 2.10.x branch.
2013-11-09 22:44:05 +01:00
scala_2_9 = callPackage ../development/compilers/scala/2.9.nix { };
scala: Bump to 2.11.0, bump 2.10 to 2.10.4
2014-05-05 08:14:57 +02:00
scala_2_10 = callPackage ../development/compilers/scala/2.10.nix { };
scala_2_11 = callPackage ../development/compilers/scala { };
scala = scala_2_11;
added scala an object oriented and functional programming language svn path=/nixpkgs/trunk/; revision=11593
2008-04-12 00:06:32 +02:00
sdcc: bump 3.3.0 -> 3.4.0 This new sdcc doesn't need older boost, so switch to nixpkgs default version (currently 1.55).
2014-04-13 19:39:32 +02:00
sdcc = callPackage ../development/compilers/sdcc { };
sdcc: new nixpkg (SDCC -> Small Device C Compiler) SDCC is a retargettable, optimizing ANSI - C compiler suite that targets the Intel MCS51 based microprocessors (8031, 8032, 8051, 8052, etc.), Maxim (formerly Dallas) DS80C390 variants, Freescale (formerly Motorola) HC08 based (hc08, s08) and Zilog Z80 based MCUs (z80, z180, gbz80, Rabbit 2000/3000, Rabbit 3000A). Work is in progress on supporting the Microchip PIC16 and PIC18 targets. It can be retargeted for other microprocessors.
2013-03-10 21:23:56 +01:00
smljnBootstrap: new expression for running smlnj on darwin
2014-06-27 00:53:50 +02:00
smlnjBootstrap = callPackage ../development/compilers/smlnj/bootstrap.nix { };
Add smlnj-110.76 Based on patch by Marc Weber: http://lists.science.uu.nl/pipermail/nix-dev/2010-December/005625.html Close #1058.
2013-10-10 17:17:28 +02:00
smlnj = callPackage_i686 ../development/compilers/smlnj { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
stalin = callPackage ../development/compilers/stalin { };
Add Stalin, an efficient Scheme compiler. svn path=/nixpkgs/trunk/; revision=11927
2008-05-29 14:10:10 +02:00
Make Stratego packages visible to nix-env
2013-01-30 13:48:45 +01:00
strategoPackages = recurseIntoAttrs strategoPackages018;
* Added a tool `mono-dll-fixer' to absolutise the DLL maps in the `*.dll.config' files corresponding to CLR assemblies. I.e., the full path to native libraries is included in the maps. In effect this allows us to set the equivalent of an RPATH for assemblies. * gtk-sharp: use the DLL fixer. It's not perfect yet: I still have to set the LD_LIBRARY_PATH for monodoc to include the gtk-sharp lib directory itself, so that it can find the `*sharpglue.so' files. This seems to be gtk-sharp's fault; it doesn't have an entry for those libraries in its DLL maps. svn path=/nixpkgs/trunk/; revision=2330
2005-03-03 18:19:58 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
strategoPackages016 = callPackage ../development/compilers/strategoxt/0.16.nix {
* Make it easier to override parts of stdenv (like gcc or make) per package using the `overrideGCC' and `overrideInStdenv' functions. svn path=/nixpkgs/trunk/; revision=5505
2006-06-23 22:11:36 +02:00
stdenv = overrideInStdenv stdenv [gnumake380];
* Added unstable pre release of Stratego/XT 0.16 * Upgraded bibtex-tools to latest unstable release. svn path=/nixpkgs/trunk/; revision=4176
2005-10-31 15:28:11 +01:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
strategoPackages017 = callPackage ../development/compilers/strategoxt/0.17.nix {
stratego shell svn path=/nixpkgs/trunk/; revision=18677
2009-11-27 21:22:43 +01:00
readline = readline5;
strategoxt-utils svn path=/nixpkgs/trunk/; revision=3271
2005-06-30 18:54:25 +02:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
strategoPackages018 = callPackage ../development/compilers/strategoxt/0.18.nix {
pkgs/development/compilers/swi-prolog/default.nix: updated to version 5.6.64 and enabled GUI support svn path=/nixpkgs/trunk/; revision=18853
2009-12-09 15:07:09 +01:00
readline = readline5;
added stratego 0.18 pre release svn path=/nixpkgs/trunk/; revision=17157
2009-09-15 13:36:41 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
metaBuildEnv = callPackage ../development/compilers/meta-environment/meta-build-env { };
meta-build-env svn path=/nixpkgs/trunk/; revision=14850
2009-04-03 11:22:20 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
swiProlog = callPackage ../development/compilers/swi-prolog { };
* Add swi-prolog without any options. svn path=/nixpkgs/trunk/; revision=11003
2008-03-06 22:53:54 +01:00
tbb: add version 4.0-u5
2012-07-18 12:44:34 +02:00
tbb = callPackage ../development/libraries/tbb { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tinycc = callPackage ../development/compilers/tinycc { };
Add TinyCC (TCC), a small, fast, and embeddable C compiler and interpreter. svn path=/nixpkgs/trunk/; revision=13168
2008-10-31 17:52:44 +01:00
Add Nix expression for Ur/Web. svn path=/nixpkgs/trunk/; revision=23381
2010-08-24 10:25:07 +02:00
urweb = callPackage ../development/compilers/urweb { };
vala: update to 0.23.1, remove old versions set license to lgpl2Plus add myself to maintainers and some cleanup
2014-01-07 10:31:52 +01:00
vala = callPackage ../development/compilers/vala/default.nix { };
vala - Compiler for the GObject type system svn path=/nixpkgs/trunk/; revision=22546
2010-07-09 15:15:40 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
visualcpp = callPackage ../development/compilers/visual-c++ { };
* A wrapper around the Visual C++ compiler and the Windows SDK. TODO: download and unpack into the Nix store Visual C++ (either from Visual C++ Express Edition or from the .NET 2.0 Framework SDK) and the Windows Platform SDK. The command line tools don't seem to need any registry settings... svn path=/nixpkgs/trunk/; revision=5369
2006-06-02 11:56:10 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vs90wrapper = callPackage ../development/compilers/vs90wrapper { };
* A wrapper around the Visual C++ compiler and the Windows SDK. TODO: download and unpack into the Nix store Visual C++ (either from Visual C++ Express Edition or from the .NET 2.0 Framework SDK) and the Windows Platform SDK. The command line tools don't seem to need any registry settings... svn path=/nixpkgs/trunk/; revision=5369
2006-06-02 11:56:10 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
webdsl = callPackage ../development/compilers/webdsl { };
Added WebDSL svn path=/nixpkgs/trunk/; revision=10375
2008-01-29 12:46:34 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
win32hello = callPackage ../development/compilers/visual-c++/test { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Improved support for building 32-bit binaries on x86_64-linux. * glibc_multi: a wrapper that combines the 32-bit and 64-bit Glibcs. This is necessary so that 64-bit GCC can find gnu/stubs-32.h and the 32-bit Glibc libraries. To build glibc_multi on x86_64-linux, you still need either the i686-linux Glibc derivation from a channel, or to have configured Nix with support for forwarding the build to a i686-linux machine. In the future this may become unnecessary by providing a prebuilt binary of 32-bit Glibc somewhere (like the binaries used in the stdenvLinux bootstrap). * With glibc_multi, it becomes possible to build gcc with multilib support (i.e. it builds 32-bit and 64-bit versions of libgcc, libstdc++, etc.). svn path=/nixpkgs/trunk/; revision=12203
2008-06-27 20:26:19 +02:00
wrapGCCWith = gccWrapper: glibc: baseGCC: gccWrapper {
Getting a new gcc-wrapper on the way. After gnat-wrapper, I introduce ghdl-wrapper. I made the gcc-4.3.4 expression allow the 'vhdl' language through ghdl. The ghdl developer recommends this gcc version; maybe it would work with gcc-4.4. If not this ghdl version, maybe next versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=19071
2009-12-22 00:02:06 +01:00
nativeTools = stdenv ? gcc && stdenv.gcc.nativeTools;
nativeLibc = stdenv ? gcc && stdenv.gcc.nativeLibc;
nativePrefix = if stdenv ? gcc then stdenv.gcc.nativePrefix else "";
gcc = baseGCC;
libc = glibc;
I made changes to achieve a working cross-built gcc wrapper. Now, "gcc45.hostDrv" works in the host system, together with libc, binutils, dynamic linker, ... svn path=/nixpkgs/branches/stdenv-updates/; revision=24971
2010-12-04 22:45:37 +01:00
shell = bash;
Getting a new gcc-wrapper on the way. After gnat-wrapper, I introduce ghdl-wrapper. I made the gcc-4.3.4 expression allow the 'vhdl' language through ghdl. The ghdl developer recommends this gcc version; maybe it would work with gcc-4.4. If not this ghdl version, maybe next versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=19071
2009-12-22 00:02:06 +01:00
inherit stdenv binutils coreutils zlib;
};
First try at a clang-wrapper. Hello world compiles\! svn path=/nixpkgs/trunk/; revision=29879
2011-10-18 22:03:09 +02:00
wrapClangWith = clangWrapper: glibc: baseClang: clangWrapper {
Add full llvm build, update libc++ and dragonegg Some packages in the llvm suite (e.g. compiler-rt) cannot be built separate from the build of llvm, and while some others (e.g. clang) can the combined build is much better tested (we've had to work around annoying issues before). So this puts llvm, clang, clang-tools-extra, compiler-rt, lld, lldb, and polly all into one big build (llvmFull). This build includes a static llvm, as dynamic is similarly less tested and has known failures. This also updates libc++ and dragonegg. libc++ now builds against libc++abi as a separate package rather than building it during the libc++ build. The clang purity patch is gone. Instead, we simply set --sysroot to /var/empty for pure builds, as all impure paths are either looked up in the gcc prefix (which we hard-code at compile time) or in the sysroot. This also means that if NIX_ENFORCE_PURITY is 0 then clang will look in the normal Linux paths by default, which is the proper behavior IMO. polly required an updated isl. When stdenv-updates is merged, perhaps we can update the isl used by gcc and avoid having two versions. Since llvm on its own is now separate from the llvm used by clang, I've removed myself as maintainer from llvm and will leave maintenance of that to those who are interested in llvm separate from clang. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 11:23:17 +01:00
nativeTools = stdenv.gcc.nativeTools or false;
nativeLibc = stdenv.gcc.nativeLibc or false;
nativePrefix = stdenv.gcc.nativePrefix or "";
First try at a clang-wrapper. Hello world compiles\! svn path=/nixpkgs/trunk/; revision=29879
2011-10-18 22:03:09 +02:00
clang = baseClang;
libc = glibc;
shell = bash;
clang builds on darwin now Also, get rid of the clang bootstrap, there's no need for it svn path=/nixpkgs/trunk/; revision=30973
2011-12-20 00:58:57 +01:00
binutils = stdenv.gcc.binutils;
inherit stdenv coreutils zlib;
First try at a clang-wrapper. Hello world compiles\! svn path=/nixpkgs/trunk/; revision=29879
2011-10-18 22:03:09 +02:00
};
Add a stdenv adapter ‘useGoldLinker’ to force use of Gold
2014-02-04 16:58:12 +01:00
wrapClang = wrapClangWith (makeOverridable (import ../build-support/clang-wrapper)) glibc;
First try at a clang-wrapper. Hello world compiles\! svn path=/nixpkgs/trunk/; revision=29879
2011-10-18 22:03:09 +02:00
Add a stdenv adapter ‘useGoldLinker’ to force use of Gold
2014-02-04 16:58:12 +01:00
wrapGCC = wrapGCCWith (makeOverridable (import ../build-support/gcc-wrapper)) glibc;
Getting a new gcc-wrapper on the way. After gnat-wrapper, I introduce ghdl-wrapper. I made the gcc-4.3.4 expression allow the 'vhdl' language through ghdl. The ghdl developer recommends this gcc version; maybe it would work with gcc-4.4. If not this ghdl version, maybe next versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=19071
2009-12-22 00:02:06 +01:00
Fixing many things related to the cross compilation in stdenvCross. It still does not work, but I think I already get glibc cross compiled. Next: gcc and g++, and set some setup script hooks on stdenvCross. It took quite enough hours for this commit. svn path=/nixpkgs/branches/stdenv-updates/; revision=18351
2009-11-15 06:28:35 +01:00
wrapGCCCross =
{gcc, libc, binutils, cross, shell ? "", name ? "gcc-cross-wrapper"}:
pkgs/top-level/all-packages.nix: switch to Python 2.6 (except on Darwin) MacOS X can build Python 2.6 just fine, but for some reason a lot of modules don't work, so the resulting binary isn't very useful. svn path=/nixpkgs/branches/stdenv-updates/; revision=19598
2010-01-21 16:39:11 +01:00
More renames
2012-12-28 19:42:10 +01:00
forceNativeDrv (import ../build-support/gcc-cross-wrapper {
Fixing many things related to the cross compilation in stdenvCross. It still does not work, but I think I already get glibc cross compiled. Next: gcc and g++, and set some setup script hooks on stdenvCross. It took quite enough hours for this commit. svn path=/nixpkgs/branches/stdenv-updates/; revision=18351
2009-11-15 06:28:35 +01:00
nativeTools = false;
nativeLibc = false;
Fixed some details on cross compilation. Among others: - Stating better the guile dependencies (native/host) for guile to build - Fixing cross-linking, through --rpath-link (ld(1) explains well about it - Made gcc call the linker and the assembler through the gcc wrapper instead of directly. I thought this was the source of missing -rpath's, but the source of the problem ended up being the lack of --rpath-link. But I think the native gcc calls the wrapped ld and as, so let's do the same cross compiling. - Removed the binutilsCross from the glibc expressions. Now they are built using the gcc-cross-wrapper, and they were built with the direct gcc and binutils before this change. - I think patchelf and strip don't break the cross-compiled binaries, so I reallow them on cross compilation. - I disable the checkPhase on cross compilation. This made gmp and libtool fail when cross compiled, iirc. svn path=/nixpkgs/branches/stdenv-updates/; revision=18498
2009-11-21 03:42:52 +01:00
noLibc = (libc == null);
- Removed all *NoCross expressions I dupilcated in nixpkgs, while maintaining the cross compilation functionality. - I renamed some expected stdenv.mkDerivation parameter attributes so we can keep this branch properly updated from trunk. We agreed with Nicolas Pierron doing a massive renaming, so all current buildInputs become hostInputs (input as build for the host machine, in autotools terminology) , and then buildInputs would mean "input as for the build machine". By now, the specific "input as for the build machine" is specified through buildNativeInputs. We should fix this in the merge to trunk. - I made the generic stdenv understand the buildNativeInputs, otherwise if we start changing nixpkgs expressions so they distinguish the current buildInputs into buildInputs and buildNativeInputs, we could break even more nixpkgs for other platforms. - I changed the default result of mkDerivation so it becomes the derivation for to be run in the build machine. This allows, without any special rewriting, "fetchurl" derivations to be always results for the build machine to use them. - The change above implies that, for anyone wanting to cross-compile, has to build the hostDrv of the wanted derivation. For example, after this commit, the usual test of "nix-build -A bison.hostDrv arm.nix" works. I described the contents of this arm.nix in r18398. svn path=/nixpkgs/branches/stdenv-updates/; revision=18471
2009-11-19 20:03:34 +01:00
inherit stdenv gcc binutils libc shell name cross;
Big fixes in the cross build: - Before this changes, cflags and ldflags for the native and the cross compiler got mixed. Not all the gcc-wrapper/gcc-cross-wrapper variables are independant now, but enough, I think. - Fixed the generic stdenv expression, which did a big mess on buildInputs and buildNativeInputs. Now it distinguishes when there is a stdenvCross or not. Maybe we should have a single stdenv and forget about the stdenvCross adapter - this could end in a stdenv a bit complex, but simpler than the generic stdenv + adapter. - Added basic support in pkgconfig for cross-builds: a single PKG_CONFIG_PATH now works for both the cross and the native compilers, but I think this should work well for most cases I can think of. - I tried to fix the guile expression to cross-biuld; guile is built, but not its manual, so the derivation still fails. Guile requires patching to cross-build, as far as I understnad. - Made the glibcCross build to be done through the usage of a gcc-cross-wrapper over the gcc-cross-stage-static, instead of using it directly. - Trying to make physfs (a neverball dependency) cross build. - Updated the gcc expression to support building a cross compiler without getting derivation variables mixed with those of the stdenvCross. svn path=/nixpkgs/branches/stdenv-updates/; revision=18534
2009-11-22 20:51:45 +01:00
});
Fixing many things related to the cross compilation in stdenvCross. It still does not work, but I think I already get glibc cross compiled. Next: gcc and g++, and set some setup script hooks on stdenvCross. It took quite enough hours for this commit. svn path=/nixpkgs/branches/stdenv-updates/; revision=18351
2009-11-15 06:28:35 +01:00
yap prolog system added svn path=/nixpkgs/trunk/; revision=11090
2008-03-13 02:13:53 +01:00
# prolog
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
yap = callPackage ../development/compilers/yap { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
yasm = callPackage ../development/compilers/yasm { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
Consistent whitespace
2013-06-13 15:18:16 +02:00
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
### DEVELOPMENT / INTERPRETERS
Adding ACL2. ACL2 = A Computational Logic for Applicative Common Lisp. It is a Lisp sublanguage and a correctness prover for it. svn path=/nixpkgs/trunk/; revision=16708
2009-08-13 16:32:52 +02:00
acl2 = builderDefsPackage ../development/interpreters/acl2 {
inherit sbcl;
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Adding AngelScript interpreter library svn path=/nixpkgs/trunk/; revision=26748
2011-04-08 08:52:31 +02:00
angelscript = callPackage ../development/interpreters/angelscript {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
clisp = callPackage ../development/interpreters/clisp { };
Updating CLisp and adding SBCL. SBCL currently has to be symlinked to a writable directory (I am investigating a fix). CLisp 2.47 is somewhat incompatible with lots of software, so I added 2.44.1 as preserved version svn path=/nixpkgs/trunk/; revision=15806
2009-05-31 08:07:25 +02:00
# compatibility issues in 2.47 - at list 2.44.1 is known good
# for sbcl bootstrap
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
clisp_2_44_1 = callPackage ../development/interpreters/clisp/2.44.1.nix {
* Streamline the stdenv bootstrap and resulting closure by removing some redundant builds (e.g., GMP was built three times). * Updated GMP to 5.0.2. * Updated PPL to 0.11.2. * Remove ad hoc flags to build GCC's dependencies statically. Instead, use the ‘makeStaticLibraries’ stdenv adapter. * Build GMP with C++ support by default. svn path=/nixpkgs/branches/stdenv-updates/; revision=30891
2011-12-14 15:31:56 +01:00
libsigsegv = libsigsegv_25;
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Add clojure. (Install with command nix-env -i clojure-wrapper start REPL with command clojure) svn path=/nixpkgs/trunk/; revision=28956
2011-09-01 15:38:59 +02:00
clojure = callPackage ../development/interpreters/clojure { };
clooj: Update to 0.4.4 Also, merge the wrapper into the main package.
2014-01-03 14:59:21 +01:00
clooj = callPackage ../development/interpreters/clojure/clooj.nix { };
Add clojure. (Install with command nix-env -i clojure-wrapper start REPL with command clojure) svn path=/nixpkgs/trunk/; revision=28956
2011-09-01 15:38:59 +02:00
erlangR16: updated to R16B03-1 - couchdb: using erlangR16 (fails to build with R17) - rename erlang attr names to use only major version in attr name
2014-06-05 02:16:50 +02:00
erlangR14 = callPackage ../development/interpreters/erlang/R14.nix { };
erlangR15 = callPackage ../development/interpreters/erlang/R15.nix { };
erlangR16 = callPackage ../development/interpreters/erlang/R16.nix { };
Support odbc in erlang R16 and R17
2014-08-15 03:14:54 +02:00
erlangR16_odbc = callPackage ../development/interpreters/erlang/R16.nix { odbcSupport = true; };
Readding Erlang R16B02: R17 is a major update and it breaks Ejabberd.
2014-05-02 18:50:58 +02:00
erlangR17 = callPackage ../development/interpreters/erlang/R17.nix { };
Support odbc in erlang R16 and R17
2014-08-15 03:14:54 +02:00
erlangR17_odbc = callPackage ../development/interpreters/erlang/R17.nix { odbcSupport = true; };
Readding Erlang R16B02: R17 is a major update and it breaks Ejabberd.
2014-05-02 18:50:58 +02:00
erlang = erlangR17;
Support odbc in erlang R16 and R17
2014-08-15 03:14:54 +02:00
erlang_odbc = erlangR17_odbc;
Ejabberd will use old Erlang for now svn path=/nixpkgs/trunk/; revision=22477
2010-07-05 14:47:35 +02:00
Package elixir and rebar. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-08-07 16:06:11 +02:00
rebar = callPackage ../development/tools/build-managers/rebar { };
elixir = callPackage ../development/interpreters/elixir { };
Ejabberd will use old Erlang for now svn path=/nixpkgs/trunk/; revision=22477
2010-07-05 14:47:35 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
groovy = callPackage ../development/interpreters/groovy { };
add Groovy 1.7.1 patch provided by Francois Perrad svn path=/nixpkgs/trunk/; revision=20862
2010-03-30 01:36:32 +02:00
GNU Guile 2.0.0! svn path=/nixpkgs/trunk/; revision=25990
2011-02-16 14:18:08 +01:00
guile_1_8 = callPackage ../development/interpreters/guile/1.8.nix { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
GNU Guile 2.0.0! svn path=/nixpkgs/trunk/; revision=25990
2011-02-16 14:18:08 +01:00
guile_2_0 = callPackage ../development/interpreters/guile { };
GNU Guile 1.9.3. svn path=/nixpkgs/trunk/; revision=17188
2009-09-16 14:46:17 +02:00
GNU Guile 2.0.0! svn path=/nixpkgs/trunk/; revision=25990
2011-02-16 14:18:08 +01:00
guile = guile_2_0;
GNU Guile 1.9.3. svn path=/nixpkgs/trunk/; revision=17188
2009-09-16 14:46:17 +02:00
hadoop: add version 2.0.1-alpha
2012-08-22 14:13:32 +02:00
hadoop = callPackage ../applications/networking/cluster/hadoop { };
Update Io to version 2011.09.12. svn path=/nixpkgs/trunk/; revision=29862
2011-10-17 10:36:07 +02:00
io = callPackage ../development/interpreters/io { };
Added Io programming language svn path=/nixpkgs/trunk/; revision=13241
2008-11-11 09:53:47 +01:00
Adding J language svn path=/nixpkgs/trunk/; revision=26398
2011-03-17 16:36:38 +01:00
j = callPackage ../development/interpreters/j {};
adding jmeter
2013-10-07 03:58:24 +02:00
jmeter = callPackage ../applications/networking/jmeter {};
Add me to maintainers list Add a derivation for davmail Add a derivation for lxappearance Add both new derivations to all-packages
2014-02-19 16:38:44 +01:00
davmail = callPackage ../applications/networking/davmail {};
lxappearance = callPackage ../applications/misc/lxappearance {};
Adding Kona: a K interpreter svn path=/nixpkgs/trunk/; revision=27098
2011-05-03 08:58:01 +02:00
kona = callPackage ../development/interpreters/kona {};
Support LuaJIT usage when building love2d
2013-11-28 20:01:05 +01:00
love = callPackage ../development/interpreters/love {lua=lua5;};
love_luajit = callPackage ../development/interpreters/love {lua=luajit;};
add love-0.9.0 (use luajit by default)
2013-12-15 07:24:28 +01:00
love_0_9 = callPackage ../development/interpreters/love/0.9.nix { };
Adding LOVE Lua-based game framework/interpreter svn path=/nixpkgs/trunk/; revision=29188
2011-09-11 19:05:48 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lua4 = callPackage ../development/interpreters/lua-4 { };
Added obsolete lua-5.0.3 version, which is required by gravit. svn path=/nixpkgs/trunk/; revision=27692
2011-07-10 16:04:19 +02:00
lua5_0 = callPackage ../development/interpreters/lua-5/5.0.3.nix { };
lua: add version 5.1 The 5.1 build system doesn't seem to support building a shared object anymore?
2012-10-10 19:24:37 +02:00
lua5_1 = callPackage ../development/interpreters/lua-5/5.1.nix { };
lua-5: update default version from 5.1.4 to 5.1.5 and add version 5.2.2
2013-09-16 11:34:45 +02:00
lua5_2 = callPackage ../development/interpreters/lua-5/5.2.nix { };
all-packages.nix: strip trailing whitespace
2014-01-13 16:48:13 +01:00
lua5_2_compat = callPackage ../development/interpreters/lua-5/5.2.nix {
Add a LUA_COMPAT_ALL version of Lua 5.2
2014-01-12 19:15:26 +01:00
compat = true;
};
lua-5: update default version from 5.1.4 to 5.1.5 and add version 5.2.2
2013-09-16 11:34:45 +02:00
lua5 = lua5_1;
lua: add 'lua' attribute pointing to 'lua5'
2014-07-02 23:57:42 +02:00
lua = lua5;
Added obsolete lua-5.0.3 version, which is required by gravit. svn path=/nixpkgs/trunk/; revision=27692
2011-07-10 16:04:19 +02:00
lua5: Add the lua-sockets extension.
2014-01-28 21:44:42 +01:00
lua5_sockets = callPackage ../development/interpreters/lua-5/sockets.nix {};
added luaexpat 1.3.0
2014-06-30 00:38:05 +02:00
lua5_expat = callPackage ../development/interpreters/lua-5/expat.nix {};
added lua-filesystem-1.6.2
2014-07-01 13:34:08 +02:00
lua5_filesystem = callPackage ../development/interpreters/lua-5/filesystem.nix {};
added lua-sec-0.5
2014-07-01 13:05:29 +02:00
lua5_sec = callPackage ../development/interpreters/lua-5/sec.nix {};
lua5: Add the lua-sockets extension.
2014-01-28 21:44:42 +01:00
Luarocks: new package
2013-06-07 12:01:22 +02:00
luarocks = callPackage ../development/tools/misc/luarocks {
lua = lua5;
};
LuaJIT: New package Just-in-time compiler for lua 5.1 with strong focus on performance. Uses the same API as lua 5.1 which makes it extremely easy to integrate.
2013-11-15 17:20:29 +01:00
luajit = callPackage ../development/interpreters/luajit {};
Adding Lush: Lisp Universal SHell
2013-07-30 13:20:46 +02:00
lush2 = callPackage ../development/interpreters/lush {};
maude: build with bison 2.x; version 3.x causes compiler errors
2014-01-23 23:28:20 +01:00
maude = callPackage ../development/interpreters/maude {
bison = bison2;
maude: use old flex version; the new one causes build errors This issue has been fixed in the latest alpha release.
2014-04-11 10:05:53 +02:00
flex = flex_2_5_35;
maude: build with bison 2.x; version 3.x causes compiler errors
2014-01-23 23:28:20 +01:00
};
maude, tecla, buddy: new packages Maude is a high-level specification language. Buddy and libtecla are required to build Maude. svn path=/nixpkgs/trunk/; revision=12358
2008-07-15 11:58:30 +02:00
mesos: Add package Apache Mesos is a cluster manager that simplifies the complexity of running applications on a shared pool of servers.
2014-04-25 15:13:41 +02:00
mesos = callPackage ../applications/networking/cluster/mesos {
sasl = cyrus_sasl;
automake = automake114x;
inherit (pythonPackages) python boto setuptools distutils-cfg wrapPython;
pythonProtobuf = pythonPackages.protobuf;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
octave = callPackage ../development/interpreters/octave {
Building octave with mesa and fltk to have the new fltk graphics toolkit available. I also add more libs octave appreciates for some functions. I've not tested the graphics toolkit, but it builds. svn path=/nixpkgs/trunk/; revision=32465
2012-02-21 23:09:48 +01:00
fltk = fltk13;
A larger Octave build with GUI
2014-01-07 19:02:01 +01:00
qt = null;
ghostscript = null;
llvm = null;
hdf5 = null;
glpk = null;
suitesparse = null;
openjdk = null;
gnuplot = null;
Making more programs use readline63. Specially those I use.
2014-03-21 11:59:57 +01:00
readline = readline63;
A larger Octave build with GUI
2014-01-07 19:02:01 +01:00
};
all-packages.nix: strip trailing whitespace
2014-01-13 16:48:13 +01:00
octaveFull = (lowPrio (callPackage ../development/interpreters/octave {
Fix Octave-full evaluation
2014-01-07 20:50:10 +01:00
fltk = fltk13;
Pass correct Qt version to octaveFull for GUI
2014-01-08 17:26:31 +01:00
qt = qt4;
Fix Octave-full evaluation
2014-01-07 20:50:10 +01:00
}));
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
bleeding edge octave version (without docs) svn path=/nixpkgs/trunk/; revision=13561
2008-12-02 23:55:45 +01:00
# mercurial (hg) bleeding edge version
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
octaveHG = callPackage ../development/interpreters/octave/hg.nix { };
bleeding edge octave version (without docs) svn path=/nixpkgs/trunk/; revision=13561
2008-12-02 23:55:45 +01:00
Adding ocropus, based on an expression from iElectric.
2014-05-28 12:12:26 +02:00
ocropus = callPackage ../applications/misc/ocropus { };
bleeding edge octave version (without docs) svn path=/nixpkgs/trunk/; revision=13561
2008-12-02 23:55:45 +01:00
perl: Add 5.16.1
2012-09-18 21:12:15 +02:00
perl514 = callPackage ../development/interpreters/perl/5.14 { };
perl516 = callPackage ../development/interpreters/perl/5.16 {
* Added Perl 5.14.2. svn path=/nixpkgs/branches/stdenv-updates/; revision=30057
2011-10-27 17:58:25 +02:00
fetchurl = fetchurlBoot;
};
perl: Add 5.20.0
2014-06-25 10:51:20 +02:00
perl520 = callPackage ../development/interpreters/perl/5.20 { };
perl: Add 5.16.1
2012-09-18 21:12:15 +02:00
perl = if system != "i686-cygwin" then perl516 else sysPerl;
* "Fix" Perl on Cygwin. svn path=/nixpkgs/trunk/; revision=18129
2009-11-05 10:11:25 +01:00
php: Add 5.4 We'll keep 5.3 around for a while.
2013-04-22 18:02:01 +02:00
php = php54;
Make php packages available in nix-env
2014-07-03 16:19:57 +02:00
phpPackages = recurseIntoAttrs (import ./php-packages.nix {
Add memcache php module
2014-03-24 13:37:36 +01:00
inherit php pkgs;
Make php packages available in nix-env
2014-07-03 16:19:57 +02:00
});
Add memcache php module
2014-03-24 13:37:36 +01:00
php: Add 5.4 We'll keep 5.3 around for a while.
2013-04-22 18:02:01 +02:00
php53 = callPackage ../development/interpreters/php/5.3.nix { };
Add php 5.3 variant with fpm support
2014-04-25 14:19:45 +02:00
php_fpm53 = callPackage ../development/interpreters/php/5.3.nix {
config = config // {
php = (config.php or {}) // {
fpm = true;
apxs2 = false;
};
};
};
php: Add 5.4 We'll keep 5.3 around for a while.
2013-04-22 18:02:01 +02:00
php54 = callPackage ../development/interpreters/php/5.4.nix { };
PHP with some configuration flags serving as example. Perhaps you can to extend it more easily if you need to svn path=/nixpkgs/trunk/; revision=9588
2007-11-05 22:13:16 +01:00
Adding PicoLisp svn path=/nixpkgs/trunk/; revision=26558
2011-03-28 10:16:15 +02:00
picolisp = callPackage ../development/interpreters/picolisp {};
pltScheme: remove -- didn't build and it's "racket" now
2013-02-24 10:32:47 +01:00
pltScheme = racket; # just to be sure
Added PLT Scheme svn path=/nixpkgs/trunk/; revision=12370
2008-07-17 11:57:47 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
polyml = callPackage ../development/compilers/polyml { };
Add expression for PolyML svn path=/nixpkgs/trunk/; revision=18875
2009-12-10 14:16:06 +01:00
pure: The pure interpreter does not now build with llvm 3.4 on linux.
2014-02-03 21:20:23 +01:00
pure = callPackage ../development/interpreters/pure {
llvm = llvm_33 ;
};
Added Compiz Fusion (main plugins). Also some dependencies, and made wmii build under setup-new-2.sh also. svn path=/nixpkgs/trunk/; revision=9577
2007-11-05 09:32:20 +01:00
python and pythonPackage attr naming - cosmetic changes
2014-07-07 18:55:43 +02:00
python = python2;
python2 = python27;
python3 = python34;
# pythonPackages further below, but assigned here because they need to be in sync
pythonPackages = python2Packages;
python2Packages = python27Packages;
python3Packages = python34Packages;
pythonFull = python2Full;
python2Full = python27Full;
all-packages.nix: switch 'python3' to python 3.4.x
2014-05-13 16:33:05 +02:00
python26 = callPackage ../development/interpreters/python/2.6 { db = db47; };
python27: libX11 is in defaultScope
2014-07-10 16:18:56 +02:00
python27 = callPackage ../development/interpreters/python/2.7 { };
add python32
2013-07-23 11:36:33 +02:00
python32 = callPackage ../development/interpreters/python/3.2 { };
add python 3.4.0rc2
2014-03-03 14:21:07 +01:00
python33 = callPackage ../development/interpreters/python/3.3 { };
all-packages.nix: switch 'python3' to python 3.4.x
2014-05-13 16:33:05 +02:00
python34 = hiPrio (callPackage ../development/interpreters/python/3.4 { });
python 25 proposal svn path=/nixpkgs/trunk/; revision=13547
2008-12-02 13:27:05 +01:00
pypy: correctly bump the version
2014-06-19 17:53:22 +02:00
pypy = callPackage ../development/interpreters/pypy/2.3 { };
WIP: pypy
2013-07-23 22:41:27 +02:00
python26Full and explicit python27Full svn path=/nixpkgs/trunk/; revision=29833
2011-10-14 11:47:30 +02:00
python26Full = callPackage ../development/interpreters/python/wrapper.nix {
python-wrapper: split 'extraLibs' into 'stdLibs' and 'extraLibs', and add 'postBuild' step The default setting for extraLibs used to be the set of modules that come with python by default but aren't usually enabled in our standard python derivation because they require additional libraries. This meant that users who want to *add* libraries to that set had to use a fairly complicated override, to add more entries without loosing the ones set by default. After this patch, the "standard libraries" such as "curses' are listed in stdLibs while the extraLibs argument remains empty by default. This allows users to override extraLibs without overriding the standard libraries. Furthermore, the wrapper environment can be messed around with in an additional 'postBuild' step. One nice application of this build step is to patch scripts and binaries to use the wrapped python interpreter instead of the pristine one, thereby enabling them to pick up all modules that have been configured. The following example shows how this is done for the 'pylint' utility: pkgs.python27Full.override { extraLibs = [pkgs.pylint]; postBuild = '' cd ${pkgs.pylint}/bin for i in *; do rm $out/bin/$i sed -r -e "s|^exec |exec $out/bin/python -- |" <$i >$out/bin/$i chmod +x $out/bin/$i done; ''; };
2013-11-07 15:13:02 +01:00
extraLibs = [];
postBuild = "";
python26Full and explicit python27Full svn path=/nixpkgs/trunk/; revision=29833
2011-10-14 11:47:30 +02:00
python = python26;
fix python26Full expression
2013-01-11 10:35:55 +01:00
inherit (python26Packages) recursivePthLoader;
python26Full and explicit python27Full svn path=/nixpkgs/trunk/; revision=29833
2011-10-14 11:47:30 +02:00
};
python27Full = callPackage ../development/interpreters/python/wrapper.nix {
python-wrapper: split 'extraLibs' into 'stdLibs' and 'extraLibs', and add 'postBuild' step The default setting for extraLibs used to be the set of modules that come with python by default but aren't usually enabled in our standard python derivation because they require additional libraries. This meant that users who want to *add* libraries to that set had to use a fairly complicated override, to add more entries without loosing the ones set by default. After this patch, the "standard libraries" such as "curses' are listed in stdLibs while the extraLibs argument remains empty by default. This allows users to override extraLibs without overriding the standard libraries. Furthermore, the wrapper environment can be messed around with in an additional 'postBuild' step. One nice application of this build step is to patch scripts and binaries to use the wrapped python interpreter instead of the pristine one, thereby enabling them to pick up all modules that have been configured. The following example shows how this is done for the 'pylint' utility: pkgs.python27Full.override { extraLibs = [pkgs.pylint]; postBuild = '' cd ${pkgs.pylint}/bin for i in *; do rm $out/bin/$i sed -r -e "s|^exec |exec $out/bin/python -- |" <$i >$out/bin/$i chmod +x $out/bin/$i done; ''; };
2013-11-07 15:13:02 +01:00
extraLibs = [];
postBuild = "";
python26Full and explicit python27Full svn path=/nixpkgs/trunk/; revision=29833
2011-10-14 11:47:30 +02:00
python = python27;
recursivePthLoader included via wrapper, not propagated by modules
2013-01-11 09:53:28 +01:00
inherit (python27Packages) recursivePthLoader;
* For convenience, provide pythonFull as a wrapper around Python that includes all the internal Python modules. svn path=/nixpkgs/branches/modular-python/; revision=26564
2011-03-28 14:31:56 +02:00
};
pkgs/top-level/all-packages.nix: strip trailing white space svn path=/nixpkgs/trunk/; revision=21416
2010-04-29 10:54:02 +02:00
add python docs
2013-03-02 05:40:20 +01:00
pythonDocs = recurseIntoAttrs (import ../development/interpreters/python/docs {
fix pythondocs (missing lib, doc instead of docs)
2013-03-05 12:28:30 +01:00
inherit stdenv fetchurl lib;
add python docs
2013-03-02 05:40:20 +01:00
});
python-linkme-wrapper
2013-01-21 20:02:57 +01:00
pythonLinkmeWrapper = callPackage ../development/interpreters/python/python-linkme-wrapper.nix { };
python wrapper that sets PYTHONHOME to the profile it is in svn path=/nixpkgs/trunk/; revision=29462
2011-09-23 19:00:13 +02:00
pypi2nix: updated
2013-09-23 05:52:51 +02:00
pypi2nix = python27Packages.pypi2nix;
* Adde xpra. Doesn't quite work yet. * Removed python_alts. svn path=/nixpkgs/trunk/; revision=11161
2008-03-17 14:45:50 +01:00
pyrex = pyrex095;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pyrex095 = callPackage ../development/interpreters/pyrex/0.9.5.nix { };
Added Compiz Fusion (main plugins). Also some dependencies, and made wmii build under setup-new-2.sh also. svn path=/nixpkgs/trunk/; revision=9577
2007-11-05 09:32:20 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pyrex096 = callPackage ../development/interpreters/pyrex/0.9.6.nix { };
Fixed log nesting; added Qi. svn path=/nixpkgs/trunk/; revision=9601
2007-11-08 15:34:54 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
qi = callPackage ../development/compilers/qi { };
Fixed log nesting; added Qi. svn path=/nixpkgs/trunk/; revision=9601
2007-11-08 15:34:54 +01:00
racket: libpng 1.6 now supported
2013-08-12 00:38:05 +02:00
racket = callPackage ../development/interpreters/racket { };
Add Nix expression for Racket. Patch by Karn Kallio <tierpluspluslists@gmail.com>. svn path=/nixpkgs/trunk/; revision=23881
2010-09-21 14:31:11 +02:00
Add Rakudo Star (closes #2054) Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-11 01:12:33 +02:00
rakudo = callPackage ../development/interpreters/rakudo { };
rascal: Add
2014-01-14 10:46:46 +01:00
rascal = callPackage ../development/interpreters/rascal { };
regina = callPackage ../development/interpreters/regina { };
Adding Regina-REXX interpreter svn path=/nixpkgs/trunk/; revision=28969
2011-09-02 10:05:51 +02:00
all-packages.nix: fix typo in path to 'renpy' expression
2013-06-09 11:15:35 +02:00
renpy = callPackage ../development/interpreters/renpy {
add Ren'Py 6.15.5 Ren'Py is a visual novel engine that helps you use words, images, and sounds to tell stories with the computer. This is just the minimal launcher.
2013-06-09 06:45:56 +02:00
wrapPython = pythonPackages.wrapPython;
};
Use ruby 1.9 as the default svn path=/nixpkgs/trunk/; revision=29543
2011-09-29 23:55:12 +02:00
ruby18 = callPackage ../development/interpreters/ruby/ruby-18.nix { };
Ruby: Separate 'install the current version of ruby' from 'install version x of ruby' when x is also the current version svn path=/nixpkgs/trunk/; revision=29600
2011-10-03 17:35:50 +02:00
ruby19 = callPackage ../development/interpreters/ruby/ruby-19.nix { };
Add ruby-2.0.0-p0
2013-02-25 12:16:32 +01:00
ruby2 = lowPrio (callPackage ../development/interpreters/ruby/ruby-2.0.nix { });
ruby: add version 2.1.2
2014-08-30 13:01:02 +02:00
ruby21 = callPackage ../development/interpreters/ruby/ruby-2.1.2.nix { };
pkgs/top-level/all-packages.nix: stripped extraneous whitespace svn path=/nixpkgs/trunk/; revision=32617
2012-02-27 11:12:06 +01:00
* Remove the ruby/default.nix, it's not very useful. svn path=/nixpkgs/trunk/; revision=32572
2012-02-26 12:07:56 +01:00
ruby = ruby19;
all-packages.nix changes for all the previous commits svn path=/nixpkgs/trunk/; revision=11564
2008-04-11 11:32:27 +02:00
Rework ruby gems svn path=/nixpkgs/trunk/; revision=25654
2011-01-21 09:24:52 +01:00
rubyLibs = recurseIntoAttrs (callPackage ../development/interpreters/ruby/libs.nix { });
all-packages.nix changes for all the previous commits svn path=/nixpkgs/trunk/; revision=11564
2008-04-11 11:32:27 +02:00
Get rid of old rake derivation that doesn't build
2013-09-02 22:50:19 +02:00
rake = rubyLibs.rake;
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rubySqlite3 = callPackage ../development/ruby-modules/sqlite3 { };
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
Rework ruby gems svn path=/nixpkgs/trunk/; revision=25654
2011-01-21 09:24:52 +01:00
rubygemsFun = ruby: builderDefsPackage (import ../development/interpreters/ruby/rubygems.nix) {
all-packages.nix changes for all the previous commits svn path=/nixpkgs/trunk/; revision=11564
2008-04-11 11:32:27 +02:00
inherit ruby makeWrapper;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
rubygems will always conflict with ruby's 'gem' command, but if it's installed it should take precedence svn path=/nixpkgs/trunk/; revision=32372
2012-02-17 22:51:06 +01:00
rubygems = hiPrio (rubygemsFun ruby);
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rq = callPackage ../applications/networking/cluster/rq { };
- Some Ruby interpreter bumped version - Kernel headers 2.6.18 added (XEN virtual images) - unifdef package added for kernel headers 2.6.18 - Python Zope and 4suite added - Trying bioconductor packages with R-lang (still failing) - Bumped gmp version - Added rq cluster runner - still requires extra gems (installs, but does not run) svn path=/nixpkgs/trunk/; revision=12766
2008-08-29 15:53:28 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
scsh = callPackage ../development/interpreters/scsh { };
Add packages scsh, The Scheme Shell svn path=/nixpkgs/trunk/; revision=18248
2009-11-07 12:17:53 +01:00
Update xonotic to 0.7. Add scheme48 1.9.
2013-11-18 15:33:19 +01:00
scheme48 = callPackage ../development/interpreters/scheme48 { };
Add Self programming language
2014-07-04 05:19:08 +02:00
self = callPackage_i686 ../development/interpreters/self { };
spark: version 0.9.0 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-02-20 12:54:04 +01:00
spark = callPackage ../applications/networking/cluster/spark { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
spidermonkey = callPackage ../development/interpreters/spidermonkey { };
Add an RC (1.8.0-rc1) of SpiderMonkey by cloning the release expression svn path=/nixpkgs/trunk/; revision=23030
2010-08-07 23:44:13 +02:00
spidermonkey_1_8_0rc1 = callPackage ../development/interpreters/spidermonkey/1.8.0-rc1.nix { };
Adding SpiderMonkey 185 svn path=/nixpkgs/trunk/; revision=30904
2011-12-15 13:13:36 +01:00
spidermonkey_185 = callPackage ../development/interpreters/spidermonkey/185-1.0.0.nix { };
Add gnome3.gjs
2014-01-20 12:34:44 +01:00
spidermonkey_17 = callPackage ../development/interpreters/spidermonkey/17.0.nix { };
Add spidermonkey_24
2014-05-19 01:03:42 +02:00
spidermonkey_24 = callPackage ../development/interpreters/spidermonkey/24.2.nix { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
add SuperCollider 3.6.6
2014-01-04 14:39:35 +01:00
supercollider = callPackage ../development/interpreters/supercollider {
qt = qt4;
fftw = fftwSinglePrec;
};
supercollider: added emacs support
2014-05-11 04:18:03 +02:00
supercollider_scel = supercollider.override { useSCEL = true; };
* Cygwin: provide a Perl setup hook so that Perl dependencies work properly. svn path=/nixpkgs/trunk/; revision=34002
2012-05-07 04:06:29 +02:00
sysPerl = callPackage ../development/interpreters/perl/sys-perl { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tcl = callPackage ../development/interpreters/tcl { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
firefox: Build without xulrunner Fixes #2950.
2014-07-23 15:31:49 +02:00
xulrunner = callPackage ../development/interpreters/xulrunner {
inherit (gnome) libIDL;
inherit (pythonPackages) pysqlite;
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
firefox: bring back version 30.0 for zotero
2014-08-04 18:13:48 +02:00
xulrunner_30 = firefox30Pkgs.xulrunner;
firefox: Disable parallel building http://hydra.nixos.org/build/3348854
2012-11-26 11:50:10 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### DEVELOPMENT / MISC
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Add amdadl-sdk: amd display library sdk, usefull for ati gpu statistics
2013-06-16 23:36:04 +02:00
amdadlsdk = callPackage ../development/misc/amdadl-sdk { };
Add amdapp-sdk: accelerated parallel processing sdk with OpenCL support
2013-06-16 23:35:09 +02:00
amdappsdk26 = callPackage ../development/misc/amdapp-sdk {
version = "2.6";
};
amdappsdk27 = callPackage ../development/misc/amdapp-sdk {
version = "2.7";
};
amdappsdk28 = callPackage ../development/misc/amdapp-sdk {
version = "2.8";
};
amdappsdk = amdappsdk28;
amdappsdkFull = callPackage ../development/misc/amdapp-sdk {
version = "2.8";
samples = true;
};
Use gcc-4.6.0 for avr-gcc-libc
2014-02-02 09:54:04 +01:00
avrgcclibc = callPackage ../development/misc/avr-gcc-with-avr-libc {
gcc = gcc46;
stdenv = overrideGCC stdenv gcc46;
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
avr8burnomat = callPackage ../development/misc/avr8-burn-omat { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
removing old bleeding edge cruft replacing it by a niftier version using source regions which are substituded by the tool nix-repository-manager. See http://github.com/MarcWeber/nix-repository-manager/raw/master/README. sourceByName is called sourceFromHead now. updates: MPlayerTrunk, haxe, neko, netsurf, cinelerra, ctags cinelerra does no longer build due to Xorg update svn path=/nixpkgs/trunk/; revision=18894
2009-12-11 14:58:23 +01:00
sourceFromHead = import ../build-support/source-from-head-fun.nix {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
inherit config;
jdk updated to 1.5.0.15 updated bleeding edge stuff (should now work for the bulidfarm as well because dist files are stored on my server) moved experimental my_env into its own file svn path=/nixpkgs/trunk/; revision=11026
2008-03-09 01:08:45 +01:00
};
- fetchdarcs supports now partial - fetchdarcs_2pre added - flapjax added - no longer used : annotatedDerivations - added bleeding edge repos with a tiny nix repository manager which dowloads and updates repostiries, then creates tar.gz dist files which are used by bleeding_edge_source (darcs tested only by now) - added experimental my_environment with example svn path=/nixpkgs/trunk/; revision=10974
2008-03-06 03:46:29 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ecj = callPackage ../development/eclipse/ecj { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jdtsdk = callPackage ../development/eclipse/jdt-sdk { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
jruby: upgraded to latest version, fixed java dependency svn path=/nixpkgs/trunk/; revision=31648
2012-01-18 21:32:20 +01:00
jruby165 = callPackage ../development/interpreters/jruby { };
adding jruby-1.1.6 cause the one shipping with netbeans can't get uid. svn path=/nixpkgs/trunk/; revision=16060
2009-06-26 18:52:58 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
guileCairo = callPackage ../development/guile-modules/guile-cairo { };
Add Guile-Cairo. svn path=/nixpkgs/trunk/; revision=17653
2009-10-06 00:21:24 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
guileGnome = callPackage ../development/guile-modules/guile-gnome {
Add GNU guile-gnome. svn path=/nixpkgs/trunk/; revision=17657
2009-10-06 00:21:50 +02:00
gconf = gnome.GConf;
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
inherit (gnome) gnome_vfs libglade libgnome libgnomecanvas libgnomeui;
Add GNU guile-gnome. svn path=/nixpkgs/trunk/; revision=17657
2009-10-06 00:21:50 +02:00
};
Guile-Lib 0.1.9. svn path=/nixpkgs/trunk/; revision=23650
2010-09-05 17:19:23 +02:00
guile_lib = callPackage ../development/guile-modules/guile-lib { };
Add Guile-Lib, a collection of useful GNU Guile modules. svn path=/nixpkgs/trunk/; revision=10639
2008-02-12 12:16:53 +01:00
GNU Guile-Ncurses 1.2. svn path=/nixpkgs/trunk/; revision=25646
2011-01-20 23:06:35 +01:00
guile_ncurses = callPackage ../development/guile-modules/guile-ncurses { };
add guile-xcb 1.3
2014-02-08 03:52:59 +01:00
guile-xcb = callPackage ../development/guile-modules/guile-xcb { };
Add the Pharo language and IDE package http://pharo.org I'm one of the developers of Pharo and the creator and maintainer of the Ubuntu PPA : https://launchpad.net/~pharo/+archive/stable.
2014-08-05 15:37:56 +02:00
pharo-vm = callPackage_i686 ../development/pharo/vm { };
srecord: new package The SRecord package is a collection of powerful tools for manipulating EPROM load files. http://srecord.sourceforge.net/
2013-07-19 00:29:50 +02:00
srecord = callPackage ../development/tools/misc/srecord { };
Trying to reinstate the meta-based Hydra builds svn path=/nixpkgs/trunk/; revision=16883
2009-08-28 08:29:21 +02:00
windowssdk = (
Attempt to mark up packages with platform assertions svn path=/nixpkgs/trunk/; revision=16850
2009-08-25 08:36:05 +02:00
import ../development/misc/windows-sdk {
inherit fetchurl stdenv cabextract;
});
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### DEVELOPMENT / TOOLS
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
ansible: conventions, fix module execution
2014-05-21 14:46:37 +02:00
ansible = callPackage ../tools/system/ansible { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
antlr = callPackage ../development/tools/parsing/antlr/2.7.7.nix { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
antlr3 = callPackage ../development/tools/parsing/antlr { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
ant = apacheAnt;
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=24045
2010-10-04 11:49:25 +02:00
* Clean up the Ant name, e.g. "ant-openjdk-1.8.0RC1" instead of "ant-<JDK name>". * Remove openjdkDarwin/ecjDarwin/antDarwin attributes. Instead the openjdk attribute refers to the Darwin package on Darwin. svn path=/nixpkgs/trunk/; revision=34505
2012-06-13 16:11:52 +02:00
apacheAnt = callPackage ../development/tools/build-managers/apache-ant { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
astyle: added initial version 2.02.1 svn path=/nixpkgs/trunk/; revision=31835
2012-01-25 14:52:18 +01:00
astyle = callPackage ../development/tools/misc/astyle { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
autobuild = callPackage ../development/tools/misc/autobuild { };
Add Simon Josefsson's Autobuild tool. svn path=/nixpkgs/trunk/; revision=12442
2008-07-28 23:29:17 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
autoconf = callPackage ../development/tools/misc/autoconf { };
all-packages.nix changes for all those updates svn path=/nixpkgs/trunk/; revision=12119
2008-06-16 15:15:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
autoconf213 = callPackage ../development/tools/misc/autoconf/2.13.nix { };
all-packages.nix changes for my last commits svn path=/nixpkgs/trunk/; revision=13693
2009-01-03 14:44:04 +01:00
Add autocutsel to all-packages
2013-04-21 18:46:16 +02:00
autocutsel = callPackage ../tools/X11/autocutsel{ };
all-packages.nix changes for my last commits svn path=/nixpkgs/trunk/; revision=13693
2009-01-03 14:44:04 +01:00
automake: switch the default to 1.12
2012-07-07 11:24:14 +02:00
automake = automake112x;
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
automake: Update to 1.12.4 Also disable tests, they're really way too slow. http://hydra.nixos.org/build/3082076
2012-10-16 20:09:57 +02:00
automake111x = callPackage ../development/tools/misc/automake/automake-1.11.x.nix { };
GNU Automake 1.11.x: Disable tests on FreeBSD. svn path=/nixpkgs/trunk/; revision=31433
2012-01-08 16:41:17 +01:00
automake: Update to 1.12.4 Also disable tests, they're really way too slow. http://hydra.nixos.org/build/3082076
2012-10-16 20:09:57 +02:00
automake112x = callPackage ../development/tools/misc/automake/automake-1.12.x.nix { };
automake: add version 1.12.1
2012-07-07 11:21:23 +02:00
automake: add version 1.13.1
2013-01-04 20:43:07 +01:00
automake113x = callPackage ../development/tools/misc/automake/automake-1.13.x.nix { };
Add automake 1.14 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-11-24 03:18:37 +01:00
automake114x = callPackage ../development/tools/misc/automake/automake-1.14.x.nix { };
Move automoc4 out of kde-4.x/ kde-4.x/ is for software that is released with kde releases, not for anything hosted on *.kde.org or in kde svn/git. svn path=/nixpkgs/trunk/; revision=26048
2011-02-22 07:19:05 +01:00
automoc4 = callPackage ../development/tools/misc/automoc4 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
avrdude = callPackage ../development/tools/misc/avrdude { };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
AVaRICE: translates between GDB's remote debug protocol and the AVR JTAG ICE protocol
2013-07-16 12:13:47 +02:00
avarice = callPackage ../development/tools/misc/avarice { };
babeltrace: new package Babeltrace is a command-line tool and library to read and convert LTTng tracefiles. Give it a (binary) trace file/dir path and it will print a human readable event log to standard out.
2013-07-04 21:41:34 +02:00
babeltrace = callPackage ../development/tools/misc/babeltrace { };
Update teeworlds svn path=/nixpkgs/trunk/; revision=26814
2011-04-13 07:47:51 +02:00
bam = callPackage ../development/tools/build-managers/bam {};
prevent usage of binutils on darwin
2014-08-01 01:04:29 +02:00
binutils = if stdenv.isDarwin
then stdenv.gcc.binutils
else callPackage ../development/tools/misc/binutils {
inherit noSysDirs;
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
binutils: enable gold by default This doesn't change the default but makes gold available to packages that might want to use it. Required switching to the gzipped tarball for bison, as xz isn't available in the early bootstrap. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-05 01:38:46 +02:00
binutils_nogold = lowPrio (callPackage ../development/tools/misc/binutils {
add some versions of cppunit/boost/protobuf, added binutils with gold, added nlopt svn path=/nixpkgs/trunk/; revision=27132
2011-05-04 12:03:46 +02:00
inherit noSysDirs;
binutils: enable gold by default This doesn't change the default but makes gold available to packages that might want to use it. Required switching to the gzipped tarball for bison, as xz isn't available in the early bootstrap. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-05 01:38:46 +02:00
gold = false;
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
});
add some versions of cppunit/boost/protobuf, added binutils with gold, added nlopt svn path=/nixpkgs/trunk/; revision=27132
2011-05-04 12:03:46 +02:00
gcc-4.8: Hook in cross-darwin libc and binutils. Let's finally hook everything into the existing cross-building infrastructure. We're using --with-sysroot instead of --with-headers here, because the XCode SDK contains references to /usr/lib. I've tried to patch those references, but unfortunately (at least with install_name_tool) it isn't possible to change those refernces in stub dylibs. So after bugging @tpoechtrager with annoying questions (thanks again), I think my initial approach (patching the SDK itself and/or regenerating the dylib stubs) was way to complicated so I ended up with this implementation. Also, I've added a condition to binutilsCross to use cctools if the libc is set to libSystem. This might need some cleanups someday, mainly to figure out how to properly bridge cctools and binutils. So, as an example on how to cross-compile GNU Hello to Darwin, you can use something like this: (import <nixpkgs> { crossSystem = { config = "x86_64-apple-darwin13"; arch = "x86_64"; libc = "libSystem"; platform = {}; }; }).hello.crossDrv Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 04:10:34 +01:00
binutilsCross =
if crossSystem != null && crossSystem.libc == "libSystem" then darwin.cctools
else lowPrio (forceNativeDrv (import ../development/tools/misc/binutils {
Fixing binutils cross-building. Gold is now enabled, and the last time I built this, it was not.
2014-05-18 18:24:25 +02:00
inherit stdenv fetchurl zlib bison;
gcc-4.8: Hook in cross-darwin libc and binutils. Let's finally hook everything into the existing cross-building infrastructure. We're using --with-sysroot instead of --with-headers here, because the XCode SDK contains references to /usr/lib. I've tried to patch those references, but unfortunately (at least with install_name_tool) it isn't possible to change those refernces in stub dylibs. So after bugging @tpoechtrager with annoying questions (thanks again), I think my initial approach (patching the SDK itself and/or regenerating the dylib stubs) was way to complicated so I ended up with this implementation. Also, I've added a condition to binutilsCross to use cctools if the libc is set to libSystem. This might need some cleanups someday, mainly to figure out how to properly bridge cctools and binutils. So, as an example on how to cross-compile GNU Hello to Darwin, you can use something like this: (import <nixpkgs> { crossSystem = { config = "x86_64-apple-darwin13"; arch = "x86_64"; libc = "libSystem"; platform = {}; }; }).hello.crossDrv Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 04:10:34 +01:00
noSysDirs = true;
cross = assert crossSystem != null; crossSystem;
}));
My first attempt at getting cross compilers in nixpkgs. My idea is to provide special stdenv expressions that will contain in the path additional cross compilers. As most expressions for programs accept a stdenv parameter, we could substitute this parameter with the special stdenv, which will have a generic builder that attempts the usual "--target=..." and can additionally have an env variable like "cross" with the target architecture set. So, finally we could have additional expressions like this: bashRealArm = makeOverridable (import ../shells/bash) { inherit fetchurl bison; stdenv = stdenvCross "armv5tel-unknown-linux-gnueabi"; }; Meanwhile it does not work - I still cannot get the cross-gcc to build. I think it does not fill the previous expressions with a lot of noise, so I think it may be a good path to follow. I only touched some files of the current stdenv: gcc-4.3, kernel headers 2.6.28, glibc 2.9, ... I tried to use the gcc-cross-wrapper, that may be very outdated. Maybe I will update it, or update the gcc-wrapper expression to make it fit the cross tools, but meanwhile I even cannot build gcc, so I have not tested the wrapper. This new idea on cross compiling is not similar to that of the nixpkgs/branches/cross-compilation, which mostly added bare new expressions for anything to be cross compiled, if I understood it correctly. I cared not to break anything of the usual stdenv in all this work. svn path=/nixpkgs/branches/stdenv-updates/; revision=18343
2009-11-14 09:11:30 +01:00
bison: add version 3.0
2013-08-03 10:39:07 +02:00
bison2 = callPackage ../development/tools/parsing/bison/2.x.nix { };
all-packages.nix: update to bison 3.x by default Let's see what happens.
2013-09-08 22:55:54 +02:00
bison3 = callPackage ../development/tools/parsing/bison/3.x.nix { };
bison = bison3;
bison: add version 2.6
2012-07-22 18:54:50 +02:00
Add BOSSA. BOSSA is a flash programming utility for Atmel's SAM family of flash-based ARM microcontrollers. The motivation behind BOSSA is to create a simple, easy-to-use, open source utility to replace Atmel's SAM-BA software. BOSSA is an acronym for Basic Open Source SAM-BA Application to reflect that goal.
2014-08-27 12:51:21 +02:00
bossa = callPackage ../development/tools/misc/bossa {
wxGTK = wxGTK30;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
buildbot = callPackage ../development/tools/build-managers/buildbot {
buildbot: bump to version 0.8.7p1 (latest stable) * 0.8.7p1 doesn't contain *.info documentation; use manpage instead * Update meta.description to not contain the package name (redundant) * 0.8.7p1 only builds with python dateutil==1.5, so that has to be added as well Runtime tested with the buildbot slave that is added in the next commit.
2013-05-05 21:53:06 +02:00
inherit (pythonPackages) twisted jinja2 sqlalchemy sqlalchemy_migrate;
dateutil = pythonPackages.dateutil_1_5;
Updated scons and twisted; added buildbot. * Updated scons to version 1.0.0. Also added appropriate makeWrapper calls to ensure that the python binary finds its library files. * Updated Twisted from 2.5 to 8.1. * Added an expression for buildbot. svn path=/nixpkgs/trunk/; revision=12782
2008-09-01 17:11:09 +02:00
};
buildbot-slave: new package Tested with buildbot (master).
2013-05-07 22:56:22 +02:00
buildbotSlave = callPackage ../development/tools/build-managers/buildbot-slave {
Merge the two BuildBot expressions. svn path=/nixpkgs/trunk/; revision=19358
2010-01-11 18:00:46 +01:00
inherit (pythonPackages) twisted;
Updated scons and twisted; added buildbot. * Updated scons to version 1.0.0. Also added appropriate makeWrapper calls to ensure that the python binary finds its library files. * Updated Twisted from 2.5 to 8.1. * Added an expression for buildbot. svn path=/nixpkgs/trunk/; revision=12782
2008-09-01 17:11:09 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
byacc = callPackage ../development/tools/parsing/byacc { };
Added: * dmenu * gftp * micropolis * byacc as a build-time dependency for micropolis contributed by baldo <baldo@quimby.lan> svn path=/nixpkgs/trunk/; revision=12526
2008-08-06 22:39:01 +02:00
new package: casperjs
2012-12-13 17:39:16 +01:00
casperjs = callPackage ../development/tools/casperjs { };
Adding cbrowser. Have cscope on the path to use it (which you should already have, because otherwise how would you have created the database for cbrowser?) svn path=/nixpkgs/trunk/; revision=29831
2011-10-14 09:47:20 +02:00
cbrowser = callPackage ../development/tools/misc/cbrowser { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ccache = callPackage ../development/tools/misc/ccache { };
Add ccache, a compiler cache. svn path=/nixpkgs/trunk/; revision=10644
2008-02-12 14:32:37 +01:00
Modifying the all-packages stdenv changer, so it allows having a global stdenv wrapper. This will fail for crossStdenv, but it allows a wrapper that uses ccache for example. That's so described in all-packages.nix around 'ccache'. svn path=/nixpkgs/trunk/; revision=31747
2012-01-21 01:25:30 +01:00
# Wrapper that works as gcc or g++
# It can be used by setting in nixpkgs config like this, for example:
I made the use of ccacheWrapper somewhat easier. svn path=/nixpkgs/trunk/; revision=31756
2012-01-21 12:22:13 +01:00
# replaceStdenv = { pkgs }: pkgs.ccacheStdenv;
Modifying the all-packages stdenv changer, so it allows having a global stdenv wrapper. This will fail for crossStdenv, but it allows a wrapper that uses ccache for example. That's so described in all-packages.nix around 'ccache'. svn path=/nixpkgs/trunk/; revision=31747
2012-01-21 01:25:30 +01:00
# But if you build in chroot, you should have that path in chroot
Making the ccacheWrapper a bit nicer. More flexible, specifically. svn path=/nixpkgs/trunk/; revision=31753
2012-01-21 02:29:06 +01:00
# If instantiated directly, it will use the HOME/.ccache as cache directory.
I made the use of ccacheWrapper somewhat easier. svn path=/nixpkgs/trunk/; revision=31756
2012-01-21 12:22:13 +01:00
# You can use an override in packageOverrides to set extraConfig:
# packageOverrides = pkgs: {
# ccacheWrapper = pkgs.ccacheWrapper.override {
# extraConfig = ''
# CCACHE_COMPRESS=1
# CCACHE_DIR=/bin/.ccache
# '';
# };
#
ccacheWrapper = makeOverridable ({ extraConfig ? "" }:
wrapGCC (ccache.links extraConfig)) {};
Mark alternative stdenvs as lowPrio
2012-09-19 19:13:11 +02:00
ccacheStdenv = lowPrio (overrideGCC stdenv ccacheWrapper);
Modifying the all-packages stdenv changer, so it allows having a global stdenv wrapper. This will fail for crossStdenv, but it allows a wrapper that uses ccache for example. That's so described in all-packages.nix around 'ccache'. svn path=/nixpkgs/trunk/; revision=31747
2012-01-21 01:25:30 +01:00
cccc: New package 3.1.4
2014-05-09 16:50:36 +02:00
cccc = callPackage ../development/tools/analysis/cccc { };
cgdb: Packaging cgdb 0.6.6
2012-06-27 20:29:56 +02:00
cgdb = callPackage ../development/tools/misc/cgdb { };
Chromedriver: update to 2.0 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-06-20 15:21:25 +02:00
chromedriver = callPackage ../development/tools/selenium/chromedriver { gconf = gnome.GConf; };
Add chromedriver: a server for running Selenium tests in Chrome
2013-02-26 00:40:29 +01:00
chrpath: new package chrpath is a command line tool to adjust the RPATH or RUNPATH of ELF binaries. (Yes, it is similar to our patchelf tool.) gpsd and Yocto/OpenEmbedded depend on chrpath (although we have currently patched that dependency out of gpsd).
2014-06-22 14:05:26 +02:00
chrpath = callPackage ../development/tools/misc/chrpath { };
Adding CL-Launch. CL-Launch is a wrapper for unified launching of various Lisp implementations
2013-08-02 07:39:20 +02:00
"cl-launch" = callPackage ../development/tools/misc/cl-launch {};
Add GNU Complexity. svn path=/nixpkgs/trunk/; revision=27344
2011-06-04 23:46:07 +02:00
complexity = callPackage ../development/tools/misc/complexity { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ctags = callPackage ../development/tools/misc/ctags { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
adding ctags-wropped. A wrapper for ctags adding some language (more) language support for .php .js .nix and .as files svn path=/nixpkgs/trunk/; revision=15476
2009-05-06 18:06:45 +02:00
ctagsWrapped = import ../development/tools/misc/ctags/wrapped.nix {
* Remove some incorrect uses of makeOverridable. svn path=/nixpkgs/trunk/; revision=18483
2009-11-20 13:51:14 +01:00
inherit pkgs ctags writeScriptBin;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cmake = callPackage ../development/tools/build-managers/cmake { };
Added cdrkit to burn DVDs. svn path=/nixpkgs/trunk/; revision=8958
2007-07-08 00:31:37 +02:00
Add cmake-2.6.4 This is the minimum version required for KDE-4, so I need it to ensure that my cmake code works with cmake-2.6.4. svn path=/nixpkgs/trunk/; revision=32504
2012-02-23 12:27:43 +01:00
cmake264 = callPackage ../development/tools/build-managers/cmake/264.nix { };
Update cmake Use system libraries, make curses optional, add optional qt4 gui etc. svn path=/nixpkgs/trunk/; revision=23810
2010-09-15 20:37:21 +02:00
cmakeCurses = cmake.override { useNcurses = true; };
cmakeWithGui = cmakeCurses.override { useQt4 = true; };
* Added "easytag", a GUI for organizing id3tags in mp3s. * Updated some ocaml packages. * Updated coccinelle. svn path=/nixpkgs/trunk/; revision=33674
2012-04-09 11:42:20 +02:00
coccinelle = callPackage ../development/tools/misc/coccinelle { };
Add Coccinelle, a semantic patch interpreter for C. svn path=/nixpkgs/trunk/; revision=18909
2009-12-12 01:47:14 +01:00
nixpkgs: move frama-c to a more appropriate directory Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-02 02:14:08 +02:00
framac = callPackage ../development/tools/analysis/frama-c { };
frama-c: add version 20111001
2012-07-12 17:42:24 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cppi = callPackage ../development/tools/misc/cppi { };
Add GNU cppi. svn path=/nixpkgs/trunk/; revision=20363
2010-03-04 12:10:44 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cproto = callPackage ../development/tools/misc/cproto { };
added cproto ( C function prototype generator ) svn path=/nixpkgs/trunk/; revision=11730
2008-04-27 20:20:57 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cflow = callPackage ../development/tools/misc/cflow { };
Add GNU cflow. svn path=/nixpkgs/trunk/; revision=13129
2008-10-28 09:43:44 +01:00
nixpkgs: cov-build 7.0.2 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-29 23:00:34 +02:00
cov-build = callPackage ../development/tools/analysis/cov-build {};
cppcheck: added version 1.53 svn path=/nixpkgs/trunk/; revision=32302
2012-02-15 17:07:45 +01:00
cppcheck = callPackage ../development/tools/analysis/cppcheck { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cscope = callPackage ../development/tools/misc/cscope { };
Add Cscope, a C code browser. svn path=/nixpkgs/trunk/; revision=12711
2008-08-25 17:34:14 +02:00
Adding csslint, this uses node as an interpreter. It detects problems in CSS files. svn path=/nixpkgs/trunk/; revision=28731
2011-08-21 23:34:17 +02:00
csslint = callPackage ../development/web/csslint { };
Add libc++
2012-10-08 08:32:09 +02:00
libcxx = callPackage ../development/libraries/libc++ { stdenv = pkgs.clangStdenv; };
Add full llvm build, update libc++ and dragonegg Some packages in the llvm suite (e.g. compiler-rt) cannot be built separate from the build of llvm, and while some others (e.g. clang) can the combined build is much better tested (we've had to work around annoying issues before). So this puts llvm, clang, clang-tools-extra, compiler-rt, lld, lldb, and polly all into one big build (llvmFull). This build includes a static llvm, as dynamic is similarly less tested and has known failures. This also updates libc++ and dragonegg. libc++ now builds against libc++abi as a separate package rather than building it during the libc++ build. The clang purity patch is gone. Instead, we simply set --sysroot to /var/empty for pure builds, as all impure paths are either looked up in the gcc prefix (which we hard-code at compile time) or in the sysroot. This also means that if NIX_ENFORCE_PURITY is 0 then clang will look in the normal Linux paths by default, which is the proper behavior IMO. polly required an updated isl. When stdenv-updates is merged, perhaps we can update the isl used by gcc and avoid having two versions. Since llvm on its own is now separate from the llvm used by clang, I've removed myself as maintainer from llvm and will leave maintenance of that to those who are interested in llvm separate from clang. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 11:23:17 +01:00
libcxxabi = callPackage ../development/libraries/libc++abi { stdenv = pkgs.clangStdenv; };
Add libc++
2012-10-08 08:32:09 +02:00
libsigrok: new package libsigrok is the core library of the sigrok signal analysis software suite, which I'm about to package. http://sigrok.org/
2014-05-18 22:15:37 +02:00
libsigrok = callPackage ../development/tools/libsigrok { };
libsigrokdecode: new package libsigrokdecode is a protocol decoding library for the sigrok signal analysis software suite. http://sigrok.org/
2014-05-18 22:28:44 +02:00
libsigrokdecode = callPackage ../development/tools/libsigrokdecode { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dejagnu = callPackage ../development/tools/misc/dejagnu { };
Add DejaGNU, a testing framework. svn path=/nixpkgs/trunk/; revision=11623
2008-04-14 13:47:26 +02:00
Add d-feet, a DBus debugger
2014-01-05 12:55:34 +01:00
dfeet = callPackage ../development/tools/misc/d-feet {
inherit (pythonPackages) pep8;
};
dfu-programmer: New package.
2014-03-07 13:28:19 +01:00
dfu-programmer = callPackage ../development/tools/misc/dfu-programmer { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ddd = callPackage ../development/tools/misc/ddd { };
Add "ddd": Graphical front-end for command-line debuggers. svn path=/nixpkgs/trunk/; revision=12336
2008-07-10 18:56:51 +02:00
pkgs/development/tools/misc/distcc: allow users to override sysconfdir svn path=/nixpkgs/trunk/; revision=24486
2010-10-26 13:14:40 +02:00
distcc = callPackage ../development/tools/misc/distcc { };
distcc 3.1: initial version svn path=/nixpkgs/trunk/; revision=17893
2009-10-20 13:54:49 +02:00
Adding wrappers for distcc, similar to those of ccache.
2012-12-22 19:35:15 +01:00
# distccWrapper: wrapper that works as gcc or g++
# It can be used by setting in nixpkgs config like this, for example:
# replaceStdenv = { pkgs }: pkgs.distccStdenv;
# But if you build in chroot, a default 'nix' will create
# a new net namespace, and won't have network access.
# You can use an override in packageOverrides to set extraConfig:
# packageOverrides = pkgs: {
# distccWrapper = pkgs.distccWrapper.override {
# extraConfig = ''
# DISTCC_HOSTS="myhost1 myhost2"
# '';
# };
#
distccWrapper = makeOverridable ({ extraConfig ? "" }:
wrapGCC (distcc.links extraConfig)) {};
distccStdenv = lowPrio (overrideGCC stdenv distccWrapper);
distcc: Adding a derivation that prepares a masquerade for distccd
2012-12-22 20:01:05 +01:00
distccMasquerade = callPackage ../development/tools/misc/distcc/masq.nix {
gccRaw = gcc.gcc;
Fixing distccMasquerade to have gas too
2012-12-22 22:04:43 +01:00
binutils = binutils;
distcc: Adding a derivation that prepares a masquerade for distccd
2012-12-22 20:01:05 +01:00
};
Added Gajim XMPP client in nearly full-feature configuration with all dependencies svn path=/nixpkgs/trunk/; revision=15001
2009-04-12 21:34:20 +02:00
docutils = builderDefsPackage (import ../development/tools/documentation/docutils) {
inherit python pil makeWrapper;
};
#1728: Build doxygen without checking for qt4 (fails on darwin)
2014-03-07 14:55:44 +01:00
doxygen = callPackage ../development/tools/documentation/doxygen {
qt4 = null;
};
* doxygen: only build the Qt GUI in doxygen_gui. svn path=/nixpkgs/branches/kde-4.7/; revision=27641
2011-07-07 22:02:59 +02:00
#1728: Build doxygen without checking for qt4 (fails on darwin)
2014-03-07 14:55:44 +01:00
doxygen_gui = lowPrio (doxygen.override { inherit qt4; });
Added build expression for doxygen 1.5.7.1. svn path=/nixpkgs/trunk/; revision=13106
2008-10-23 16:23:12 +02:00
drush: add expression
2013-12-05 05:11:35 +01:00
drush = callPackage ../development/tools/misc/drush { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
eggdbus = callPackage ../development/tools/misc/eggdbus { };
* Added PolicyKit and eggdbus. There is a newer version of PolicyKit (0.93), but it doesn't compile with the current glib. svn path=/nixpkgs/trunk/; revision=16704
2009-08-13 09:55:11 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
elfutils = callPackage ../development/tools/misc/elfutils { };
* Revived RPM. Damn, RPM is nasty to build. svn path=/nixpkgs/trunk/; revision=8407
2007-03-21 20:25:58 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
epm = callPackage ../development/tools/misc/epm { };
* More OpenOffice hackery. Added the magic incantations to get it to install (of course there's no "make install", that would be too easy). Also create some wrapper scripts "oowriter", "oodraw" etc. (I haven't done a full build of this yet, I've hacked on a tmpdir left behind by nix-build -K.) svn path=/nixpkgs/trunk/; revision=9260
2007-09-06 17:00:33 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
emma = callPackage ../development/tools/analysis/emma { };
* Added Emma, a Java code coverage tool. svn path=/nixpkgs/trunk/; revision=10865
2008-02-26 16:48:14 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
findbugs = callPackage ../development/tools/analysis/findbugs { };
* Added Findbugs. svn path=/nixpkgs/trunk/; revision=10854
2008-02-25 15:55:30 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pmd = callPackage ../development/tools/analysis/pmd { };
* added checkstyle, pmd, jdepends. * changed version of ant to 1.7 svn path=/nixpkgs/trunk/; revision=15994
2009-06-18 14:51:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jdepend = callPackage ../development/tools/analysis/jdepend { };
* added checkstyle, pmd, jdepends. * changed version of ant to 1.7 svn path=/nixpkgs/trunk/; revision=15994
2009-06-18 14:51:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
checkstyle = callPackage ../development/tools/analysis/checkstyle { };
* added checkstyle, pmd, jdepends. * changed version of ant to 1.7 svn path=/nixpkgs/trunk/; revision=15994
2009-06-18 14:51:51 +02:00
add back old version of flex for grub2
2014-04-09 20:42:08 +02:00
flex_2_5_35 = callPackage ../development/tools/parsing/flex/2.5.35.nix { };
Offer consistently named attributes for the two available flex versions.
2014-04-11 10:05:12 +02:00
flex_2_5_39 = callPackage ../development/tools/parsing/flex/2.5.39.nix { };
flex = flex_2_5_39;
all-packages.nix changes for previous commits svn path=/nixpkgs/trunk/; revision=11217
2008-03-20 10:52:40 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
m4 = gnum4;
* Added wxHaskell. * Added GNU MP, use it in pycrypto. svn path=/nixpkgs/trunk/; revision=7343
2006-12-13 23:29:40 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
global = callPackage ../development/tools/misc/global { };
Add GNU GLOBAL, a source code tag system. svn path=/nixpkgs/trunk/; revision=16333
2009-07-13 11:05:56 +02:00
Move gnome-doc-utils and gtk-doc to top-level Add compatibility attrs. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33252
2012-03-19 05:36:41 +01:00
gnome_doc_utils = callPackage ../development/tools/documentation/gnome-doc-utils {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gnum4 = callPackage ../development/tools/misc/gnum4 { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
gnumake: clean up directory structure; no functional change
2013-12-09 16:09:33 +01:00
gnumake380 = callPackage ../development/tools/build-managers/gnumake/3.80 { };
gnumake381 = callPackage ../development/tools/build-managers/gnumake/3.81 { };
gnumake382 = callPackage ../development/tools/build-managers/gnumake/3.82 { };
gnumake: add version 4.0
2013-12-09 16:14:41 +01:00
gnumake40 = callPackage ../development/tools/build-managers/gnumake/4.0 { };
gnumake: clean up directory structure; no functional change
2013-12-09 16:09:33 +01:00
gnumake = gnumake382;
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Move gtkLibs to top-level namespace Earlier there was a strict correspondence between versions of gtkLibs.* but now upstream moves to gtk-3.x, and there is no simple rule anymore. Thus it is easier to override particular libs on a case-by-case basis than using gtkLibs2x. svn path=/nixpkgs/trunk/; revision=32040
2012-02-05 19:29:42 +01:00
gob2 = callPackage ../development/tools/misc/gob2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gradle = callPackage ../development/tools/build-managers/gradle { };
add Gradle 0.8 patch provided by Francois Perrad svn path=/nixpkgs/trunk/; revision=20863
2010-03-30 01:36:35 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gperf = callPackage ../development/tools/misc/gperf { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Move gnome-doc-utils and gtk-doc to top-level Add compatibility attrs. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33252
2012-03-19 05:36:41 +01:00
gtk_doc = callPackage ../development/tools/documentation/gtk-doc { };
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
gtkdialog = callPackage ../development/tools/misc/gtkdialog { };
* added haddock documentation tool for ghc/Haskell svn path=/nixpkgs/trunk/; revision=10229
2008-01-19 18:05:54 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
guileLint = callPackage ../development/tools/guile/guile-lint { };
Add Guile-Lint, a syntax and semantics checker for GNU Guile. svn path=/nixpkgs/trunk/; revision=10710
2008-02-15 17:30:33 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gwrap = callPackage ../development/tools/guile/g-wrap { };
Add G-Wrap, a binding generator for Guile. svn path=/nixpkgs/trunk/; revision=11506
2008-04-09 09:56:52 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
help2man = callPackage ../development/tools/misc/help2man {
* Drop the "perl" prefix from Perl attribute names. It's redundant now that Perl packages are in their own namespace (perlPackages.<pkg>). svn path=/nixpkgs/trunk/; revision=15176
2009-04-20 14:49:35 +02:00
inherit (perlPackages) LocaleGettext;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Adding hyenae - patch by MarcWeber svn path=/nixpkgs/trunk/; revision=29470
2011-09-24 11:14:21 +02:00
hyenae = callPackage ../tools/networking/hyenae { };
add ibus
2014-01-25 17:05:33 +01:00
ibus = callPackage ../development/libraries/ibus { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
iconnamingutils = callPackage ../development/tools/misc/icon-naming-utils {
* Drop the "perl" prefix from Perl attribute names. It's redundant now that Perl packages are in their own namespace (perlPackages.<pkg>). svn path=/nixpkgs/trunk/; revision=15176
2009-04-20 14:49:35 +02:00
inherit (perlPackages) XMLSimple;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
* More Gnome stuff. svn path=/nixpkgs/trunk/; revision=8190
2007-03-05 19:52:31 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
indent = callPackage ../development/tools/misc/indent { };
Added indent svn path=/nixpkgs/trunk/; revision=9790
2007-11-25 19:35:33 +01:00
arduino-core libraries +inotool
2012-11-28 02:55:24 +01:00
ino = callPackage ../development/arduino/ino { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
inotifyTools = callPackage ../development/tools/misc/inotify-tools { };
adding inotify-tools svn path=/nixpkgs/trunk/; revision=19469
2010-01-15 20:35:02 +01:00
intel-gpu-tools: Add derivation
2014-08-04 08:21:59 +02:00
intel-gpu-tools = callPackage ../development/tools/misc/intel-gpu-tools {
inherit (xorg) libpciaccess dri2proto libX11 libXext libXv libXrandr;
};
Adding libva, to get some possible video acceleration in intel video cards. svn path=/nixpkgs/trunk/; revision=26854
2011-04-16 13:00:31 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ired = callPackage ../development/tools/analysis/radare/ired.nix { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Add itstool svn path=/nixpkgs/trunk/; revision=31372
2012-01-06 21:09:39 +01:00
itstool = callPackage ../development/tools/misc/itstool { };
Adding the rally game Trigger. As a side effect, I add jam. svn path=/nixpkgs/trunk/; revision=26615
2011-03-30 20:45:11 +02:00
jam = callPackage ../development/tools/build-managers/jam { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jikespg = callPackage ../development/tools/parsing/jikespg { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Add jenkins continuous integration server and user. By default the jenkins server is executed under the user "jenkins". Which can be configured using users.jenkins.* options. If a different user is requested by changing services.jenkins.user then none of the users.jenkins options apply. This patch does not include jenkins slave configuration. Some config options will probably change when this is implemented. Aspects like the user and environment are typically identical between slave and master. The service configs are different. The design is for users.jenkins to cover the shared aspects while services.jenkins and services.jenkins-slave cover the master and slave specific aspects, respectively. Another option would be to place everything under services.jenkins and have a config that selects master vs slave.
2014-02-10 21:07:12 +01:00
jenkins = callPackage ../development/tools/continuous-integration/jenkins { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lcov = callPackage ../development/tools/analysis/lcov { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
leiningen: added package version 1.6.2 svn path=/nixpkgs/trunk/; revision=31716
2012-01-19 21:34:59 +01:00
leiningen = callPackage ../development/tools/build-managers/leiningen { };
* pam_console needs an old libtool. svn path=/nixpkgs/branches/stdenv-updates/; revision=14791
2009-03-30 17:31:47 +02:00
libtool = libtool_2;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libtool_1_5 = callPackage ../development/tools/misc/libtool { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libtool_2 = callPackage ../development/tools/misc/libtool/libtool2.nix { };
Add GNU Libtool 2.2.x. svn path=/nixpkgs/trunk/; revision=13176
2008-11-03 11:15:37 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lsof = callPackage ../development/tools/misc/lsof { };
Added lsof in package collection svn path=/nixpkgs/trunk/; revision=8886
2007-06-18 00:44:30 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ltrace = callPackage ../development/tools/misc/ltrace { };
Added ltrace - library call tracer. Note that it needed adding an extension point to doUnpack, but it doesn't force full rebuild of everything using builder composing. svn path=/nixpkgs/trunk/; revision=9574
2007-11-03 09:19:00 +01:00
lttng: align attribute name with package name lttngModules => lttng-modules lttngTools => lttng-tools lttngUst => lttng-ust But keep the old attributes around for backward compatibility.
2014-07-31 15:48:06 +02:00
lttng-tools = callPackage ../development/tools/misc/lttng-tools { };
lttng-tools: new package This is the Linux Trace Toolkit. Included in this package: Command-line client: lttng Tracing daemons: lttng-sessiond (automatically started by lttng) lttng-relayd (remote trace collection daemon) Userspace tracing can be done by using liblttng-ust. To do kernel tracing we also need the LTTng kernel modules. I've added a patch that changes "/sbin/modprobe" to just "modprobe".
2013-07-04 21:38:23 +02:00
lttng: align attribute name with package name lttngModules => lttng-modules lttngTools => lttng-tools lttngUst => lttng-ust But keep the old attributes around for backward compatibility.
2014-07-31 15:48:06 +02:00
lttng-ust = callPackage ../development/tools/misc/lttng-ust { };
lttng-ust: new package This is the user space library for LTTng. It is needed to do user space tracing, as opposed to kernel space tracing.
2013-07-04 21:32:12 +02:00
lttv: new package Linux Trace Toolkit Viewer is a GUI program to visualize LTTng trace files. (An alternative to this program is the LTTng plugin for the Eclipse IDE.)
2013-07-06 10:56:42 +02:00
lttv = callPackage ../development/tools/misc/lttv { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mk = callPackage ../development/tools/build-managers/mk { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
add package: neoload-4.0.4
2012-11-18 12:37:10 +01:00
neoload = callPackage ../development/tools/neoload {
licenseAccepted = (config.neoload.accept_license or false);
};
ninja: move out of pythonPackages ninja is a build system written in C++ that just happens to use python to build/install *itself*. It is not a "python package". After this commit, ninja will be at pkgs.ninja instead of pkgs.pythonPackages.ninja.
2013-05-11 11:39:52 +02:00
ninja = callPackage ../development/tools/build-managers/ninja { };
nixbang: add expession
2014-08-24 14:17:17 +02:00
nixbang = callPackage ../development/tools/misc/nixbang {
pythonPackages = python3Packages;
};
Add node-webkit, app runtime based on Chromium and node.js
2014-01-12 23:39:14 +01:00
node_webkit = callPackage ../development/tools/node-webkit {
gconf = pkgs.gnome.GConf;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
noweb = callPackage ../development/tools/literate-programming/noweb { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
omake = callPackage ../development/tools/ocaml/omake { };
Upgraded omake to 0.9.8.6_rc1. kept the previous version as default because this is a rc1. This is necessary to compile the latest camlimages
2013-06-04 20:33:31 +02:00
omake_rc1 = callPackage ../development/tools/ocaml/omake/0.9.8.6-rc1.nix { };
omake: version 0.9.8.5 svn path=/nixpkgs/trunk/; revision=22019
2010-05-27 21:44:03 +02:00
opengrok: new package Source code search and cross reference engine http://opengrok.github.io/OpenGrok/
2014-06-04 14:28:08 +02:00
opengrok = callPackage ../development/tools/misc/opengrok { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openocd = callPackage ../development/tools/misc/openocd { };
Adding OpenOCD. svn path=/nixpkgs/trunk/; revision=17302
2009-09-20 18:43:16 +02:00
Updating oprofile svn path=/nixpkgs/trunk/; revision=32751
2012-03-03 12:30:44 +01:00
oprofile = callPackage ../development/tools/profiling/oprofile { };
Add OProfile, a system-wide profiler for Linux. svn path=/nixpkgs/trunk/; revision=11984
2008-06-04 23:23:30 +02:00
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
patchelf = callPackage ../development/tools/misc/patchelf { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Add peg, http://piumarta.com/software/peg/ svn path=/nixpkgs/trunk/; revision=28456
2011-08-10 11:54:22 +02:00
peg = callPackage ../development/tools/parsing/peg { };
add phantomjs to darwin platform
2014-02-12 00:46:46 +01:00
phantomjs = callPackage ../development/tools/phantomjs {
stdenv = if stdenv.isDarwin
then overrideGCC stdenv gccApple
else stdenv;
};
new package: phantomjs
2012-12-13 17:09:41 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pmccabe = callPackage ../development/tools/misc/pmccabe { };
Add pmccabe, a tool that computes the cyclomatic complexity of C/C++ source. svn path=/nixpkgs/trunk/; revision=12000
2008-06-06 14:26:01 +02:00
Rename hostDrv -> crossDrv, buildDrv -> nativeDrv This is for consistency with terminology in stdenv (and the terms "hostDrv" and "buildDrv" are not very intuitive, even if they're consistent with GNU terminology).
2012-12-28 19:08:19 +01:00
/* Make pkgconfig always return a nativeDrv, never a proper crossDrv,
Made more libraries cross compile. fontconfig, libxcb, bzip2, libdrm, zlib... I was trying to cross compile SDL. Many dependencies work, but I ended seeing libX11 not ready for cross compilation. Other xorg libraries cross-compile well. libX11 may need a small patch. The problem is the usual "configure test cannot be run in cross compilation", so the configure script halts. I made the pkgconfig expression always return buildDrv, as I think it rarely will be needed as buildInput. So to avoid rewriting all its mentions to use it as buildNativeInput, I prefered this small change. svn path=/nixpkgs/branches/stdenv-updates/; revision=18500
2009-11-21 11:44:22 +01:00
because most usage of pkgconfig as buildInput (inheritance of
Rename buildNativeInputs -> nativeBuildInputs Likewise for propagatedBuildNativeInputs, etc. "buildNativeInputs" sounds like an imperative rather than a noun phrase.
2012-12-28 19:20:09 +01:00
pre-cross nixpkgs) means using it using as nativeBuildInput
Adding a note about a change to do in the big-renaming to allow clear buildInputs and buildNativeInputs, on pkgconfig, which now works always as buildDrv even asking for its hostDrv. Key string: cross_renaming svn path=/nixpkgs/branches/stdenv-updates/; revision=18506
2009-11-21 16:39:20 +01:00
cross_renaming: we should make all programs use pkgconfig as
Rename buildNativeInputs -> nativeBuildInputs Likewise for propagatedBuildNativeInputs, etc. "buildNativeInputs" sounds like an imperative rather than a noun phrase.
2012-12-28 19:20:09 +01:00
nativeBuildInput after the renaming.
Adding a note about a change to do in the big-renaming to allow clear buildInputs and buildNativeInputs, on pkgconfig, which now works always as buildDrv even asking for its hostDrv. Key string: cross_renaming svn path=/nixpkgs/branches/stdenv-updates/; revision=18506
2009-11-21 16:39:20 +01:00
*/
More renames
2012-12-28 19:42:10 +01:00
pkgconfig = forceNativeDrv (callPackage ../development/tools/misc/pkgconfig { });
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
pkgconfigUpstream = lowPrio (pkgconfig.override { vanilla = true; });
Made more libraries cross compile. fontconfig, libxcb, bzip2, libdrm, zlib... I was trying to cross compile SDL. Many dependencies work, but I ended seeing libX11 not ready for cross compilation. Other xorg libraries cross-compile well. libX11 may need a small patch. The problem is the usual "configure test cannot be run in cross compilation", so the configure script halts. I made the pkgconfig expression always return buildDrv, as I think it rarely will be needed as buildInput. So to avoid rewriting all its mentions to use it as buildNativeInput, I prefered this small change. svn path=/nixpkgs/branches/stdenv-updates/; revision=18500
2009-11-21 11:44:22 +01:00
Add prelink package
2014-07-19 02:12:50 +02:00
prelink = callPackage ../development/tools/misc/prelink { };
premake: bump to version 4.3 aacskeys depends on premake3, so keep that version around.
2013-04-08 21:06:54 +02:00
premake3 = callPackage ../development/tools/misc/premake/3.nix { };
premake4 = callPackage ../development/tools/misc/premake { };
premake = premake4;
new package: premake -- lua based build configuration tool this is version 3, while 4 already exists. But I only need this tool for 'aacskeys', which doesn't work with 4 svn path=/nixpkgs/trunk/; revision=32490
2012-02-22 21:29:42 +01:00
Forgot to commit all-packages.nix for pstack.
2012-08-23 14:15:56 +02:00
pstack = callPackage ../development/tools/misc/gdb/pstack.nix { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
radare = callPackage ../development/tools/analysis/radare {
Adding radare svn path=/nixpkgs/trunk/; revision=15226
2009-04-21 21:47:51 +02:00
inherit (gnome) vte;
lua = lua5;
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
useX11 = config.radare.useX11 or false;
pythonBindings = config.radare.pythonBindings or false;
rubyBindings = config.radare.rubyBindings or false;
luaBindings = config.radare.luaBindings or false;
Adding radare svn path=/nixpkgs/trunk/; revision=15226
2009-04-21 21:47:51 +02:00
};
Add radare2
2014-09-03 21:01:39 +02:00
radare2 = callPackage ../development/tools/analysis/radare2 {
inherit (gnome) vte;
lua = lua5;
useX11 = config.radare.useX11 or false;
pythonBindings = config.radare.pythonBindings or false;
rubyBindings = config.radare.rubyBindings or false;
luaBindings = config.radare.luaBindings or false;
};
Adding radare svn path=/nixpkgs/trunk/; revision=15226
2009-04-21 21:47:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ragel = callPackage ../development/tools/parsing/ragel { };
Add ragel: A state machine compiler. svn path=/nixpkgs/trunk/; revision=13881
2009-01-27 15:00:54 +01:00
Added re2c 0.13.5
2012-12-02 00:25:01 +01:00
re2c = callPackage ../development/tools/parsing/re2c { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
remake = callPackage ../development/tools/build-managers/remake { };
Adding 'remake': a patched and modernized version of GNU make utility that adds improved error reporting, the ability to trace execution in a comprehensible way, and a debugger. svn path=/nixpkgs/trunk/; revision=17744
2009-10-11 17:03:13 +02:00
saleae-logic: align attr name with pkg name (saleaeLogic -> saleae-logic)
2014-03-08 09:53:11 +01:00
saleae-logic = callPackage ../development/tools/misc/saleae-logic { };
saleae-logic: new package Add Saleae Logic - analyzer software for Saleae logic analyzators. Also, add a small LD_PRELOAD library that is needed to make it work from a read-only installation directory.
2013-02-28 22:15:04 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
# couldn't find the source yet
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
seleniumRCBin = callPackage ../development/tools/selenium/remote-control {
newline svn path=/nixpkgs/trunk/; revision=26049
2011-02-22 07:19:11 +01:00
jre = jdk;
};
xara update (now works on i686 and _64 again) selenium-rc binaries (automatic web application testing remote control server) svn path=/nixpkgs/trunk/; revision=9835
2007-12-03 15:33:54 +01:00
Add selenium-server-standalone (submitted by coreyoconnor)
2014-02-27 13:06:23 +01:00
selenium-server-standalone = callPackage ../development/tools/selenium/server { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
scons = callPackage ../development/tools/build-managers/scons { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
simpleBuildTool = callPackage ../development/tools/build-managers/simple-build-tool { };
patch provided by David Brown adding simple-build-tool which builds Scala packages svn path=/nixpkgs/trunk/; revision=21671
2010-05-08 23:51:47 +02:00
sigrok-cli: new package This is the command-line frontend for the sigrok signal analysis software suite. http://sigrok.org/
2014-05-18 22:30:34 +02:00
sigrok-cli = callPackage ../development/tools/sigrok-cli { };
Adding SlimerJS — script-driven Gecko browser
2013-10-20 22:30:11 +02:00
slimerjs = callPackage ../development/tools/slimerjs {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sloccount = callPackage ../development/tools/misc/sloccount { };
Add SLOCCount, a tool to count source lines of code (SLOCs). svn path=/nixpkgs/trunk/; revision=14091
2009-02-17 11:11:33 +01:00
Add a "smatch" package. Signed-off-by: Cyril Roelandt <tipecaml@gmail.com> Signed-off-by: Ludovic Courtès <ludo@gnu.org>
2012-10-05 03:24:09 +02:00
smatch = callPackage ../development/tools/analysis/smatch {
buildllvmsparse = false;
buildc2xml = false;
};
smc: new package SMC is a state machine compiler. It generates state machine code from text input files (state diagrams). Homepage: http://smc.sourceforge.net/
2013-11-23 00:11:23 +01:00
smc = callPackage ../tools/misc/smc { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sparse = callPackage ../development/tools/analysis/sparse { };
Add Sparse, a static analysis tool for C. svn path=/nixpkgs/trunk/; revision=12696
2008-08-22 20:33:52 +02:00
add development version of speedtest-cli
2013-07-20 12:45:33 +02:00
speedtest_cli = callPackage ../tools/networking/speedtest-cli { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
spin = callPackage ../development/tools/analysis/spin { };
Adding spin svn path=/nixpkgs/trunk/; revision=15433
2009-05-03 16:35:43 +02:00
splint: fix build by using older flex
2014-08-14 18:02:35 +02:00
splint = callPackage ../development/tools/analysis/splint {
flex = flex_2_5_35;
};
Add Splint, a static code analyzer for C. svn path=/nixpkgs/trunk/; revision=12343
2008-07-11 11:13:34 +02:00
Add stm32flash, flash program for stm32 bootloader. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-06-22 15:05:32 +02:00
stm32flash = callPackage ../development/tools/misc/stm32flash { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
strace = callPackage ../development/tools/misc/strace { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
swig = callPackage ../development/tools/misc/swig { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Add swig-2.x svn path=/nixpkgs/trunk/; revision=31320
2012-01-06 00:15:24 +01:00
swig2 = callPackage ../development/tools/misc/swig/2.x.nix { };
Add swig-3.x
2014-04-20 00:54:16 +02:00
swig3 = callPackage ../development/tools/misc/swig/3.x.nix { };
Keep only one SWIG, with support for all languages. svn path=/nixpkgs/trunk/; revision=17351
2009-09-22 13:59:41 +02:00
swigWithJava = swig;
add swfmill-0.3.2
2013-02-05 04:36:18 +01:00
swfmill = callPackage ../tools/video/swfmill { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
swftools = callPackage ../tools/video/swftools { };
added swftools svn path=/nixpkgs/trunk/; revision=13078
2008-10-16 13:01:10 +02:00
tcptrack: new package tcptrack is a small libpcap based program (with ncurses UI) for live TCP connection monitoring. It seems upstream homepage is down, so download the source code from a fedora server instead.
2013-05-12 14:03:24 +02:00
tcptrack = callPackage ../development/tools/misc/tcptrack { };
teensy-loader: New package Firmware uploader for the teensy microcontroller board family.
2014-02-18 01:02:47 +01:00
teensy-loader = callPackage ../development/tools/misc/teensy { };
texinfo: added version 5.0
2013-02-19 10:14:09 +01:00
texinfo413 = callPackage ../development/tools/misc/texinfo/4.13a.nix { };
texinfo: update to version 5.2
2013-09-28 10:36:34 +02:00
texinfo5 = callPackage ../development/tools/misc/texinfo/5.2.nix { };
gcc: use texinfo4, fix bad mpfr reference
2013-06-30 22:25:30 +02:00
texinfo4 = texinfo413;
texinfo: update to version 5.2
2013-09-28 10:36:34 +02:00
texinfo = texinfo5;
texinfo: move ncurses support into texinfoInteractive This, for example, drops the stdenv dependency on ncurses.
2014-02-27 08:22:41 +01:00
texinfoInteractive = appendToName "interactive" (
texinfo.override { interactive = true; }
);
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
texi2html = callPackage ../development/tools/misc/texi2html { };
adding texitohtml (dependency of lilypond) svn path=/nixpkgs/trunk/; revision=17023
2009-09-10 18:57:42 +02:00
uhd: new package UHD is USRP Hardware Driver (for Software Defined Radio).
2013-05-02 15:27:11 +02:00
uhd = callPackage ../development/tools/misc/uhd { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
uisp = callPackage ../development/tools/misc/uisp { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
uncrustify: new package Uncrustify is a source code beautifier for C, C++, C#, ObjectiveC, D, Java, Pawn and VALA. Homepage: http://uncrustify.sourceforge.net/
2013-08-31 09:42:20 +02:00
uncrustify = callPackage ../development/tools/misc/uncrustify { };
vagrant: upgrade to 1.6.3
2014-07-15 02:47:11 +02:00
vagrant = callPackage ../development/tools/vagrant {
ruby = ruby2;
};
vagrant: add expression
2013-11-21 23:21:39 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gdb = callPackage ../development/tools/misc/gdb {
GDB: Allow cross-compilation for GNU. svn path=/nixpkgs/trunk/; revision=30481
2011-11-19 19:28:10 +01:00
hurd = gnu.hurdCross;
Making more programs use readline63. Specially those I use.
2014-03-21 11:59:57 +01:00
readline = readline63;
GDB: Allow cross-compilation for GNU. svn path=/nixpkgs/trunk/; revision=30481
2011-11-19 19:28:10 +01:00
inherit (gnu) mig;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Mark some cross-compiled packages as low priority
2012-11-08 16:30:02 +01:00
gdbCross = lowPrio (callPackage ../development/tools/misc/gdb {
Adding gdbCross, to have a gdb for other targets than native. svn path=/nixpkgs/branches/stdenv-updates/; revision=18772
2009-12-02 21:54:40 +01:00
target = crossSystem;
Mark some cross-compiled packages as low priority
2012-11-08 16:30:02 +01:00
});
Adding gdbCross, to have a gdb for other targets than native. svn path=/nixpkgs/branches/stdenv-updates/; revision=18772
2009-12-02 21:54:40 +01:00
Darwin: Use GCC 4.6 in `stdenvNix'. svn path=/nixpkgs/trunk/; revision=33894
2012-04-23 17:47:37 +02:00
valgrind = callPackage ../development/tools/analysis/valgrind {
stdenv =
# On Darwin, Valgrind 3.7.0 expects Apple's GCC (for
# `__private_extern'.)
if stdenv.isDarwin
then overrideGCC stdenv gccApple
else stdenv;
};
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
Adding valkyrie, a frontend for some valgrind 3.6 tools. svn path=/nixpkgs/trunk/; revision=24815
2010-11-22 20:10:15 +01:00
valkyrie = callPackage ../development/tools/analysis/valkyrie { };
xc3sprog: new package xc3sprog is command-line tools for programming FPGAs, microcontrollers and PROMs via JTAG. Homepage: http://xc3sprog.sourceforge.net/ I'm using the latest from subversion as xc3sprog doesn't seem to make proper releases. There are only a few seemingly random snapshots at sourceforge. And these snapshots are built binary packages, not source archives. NOTE: I haven't tested this on any hardware yet.
2013-10-26 09:38:31 +02:00
xc3sprog = callPackage ../development/tools/misc/xc3sprog { };
xmlindent: New expression [Bjørn Forsman <bjorn.forsman@gmail.com>: - introduce "name-${version}" (to not duplicate version number) - use mirror://sourceforge instead of specific mirror URL - add vertical whitespace between attributes - add meta description and homepage attributes - place the top-level 'xmlindent' attribute in alphabetial order ]
2014-01-27 15:31:27 +01:00
xmlindent = callPackage ../development/web/xmlindent {};
Add new package "xpwn" from @dborca's fork. This really hase some nice utilities for coping with HFS+ and DMG format. We're going to use it for extracting the xcode DMG, but it could be used for more, even generating DMGs. The reason I'm using the fork instead of the repository from @planetbeing is thet the fork contains a few fixes, especially for dealing with symlinks in HFS+ images. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 02:57:48 +01:00
xpwn = callPackage ../development/mobile/xpwn {};
xxdiff, qt5: use bison2
2014-01-19 11:47:58 +01:00
xxdiff = callPackage ../development/tools/misc/xxdiff {
bison = bison2;
};
Added xxdiff svn path=/nixpkgs/trunk/; revision=11888
2008-05-25 22:43:56 +02:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
yacc = bison;
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
yodl = callPackage ../development/tools/misc/yodl { };
added yodl, dependency for zsh documentation svn path=/nixpkgs/trunk/; revision=13669
2008-12-22 19:36:02 +01:00
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### DEVELOPMENT / LIBRARIES
Updated gaim to latest beta Added gdb svn path=/nixpkgs/trunk/; revision=8019
2007-02-22 17:07:51 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
a52dec = callPackage ../development/libraries/a52dec { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
new package: aacskeys -- grab aacs keys from bluray disks svn path=/nixpkgs/trunk/; revision=32491
2012-02-22 21:29:46 +01:00
aacskeys = callPackage ../development/libraries/aacskeys { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
aalib = callPackage ../development/libraries/aalib { };
* A wrapper around the Visual C++ compiler and the Windows SDK. TODO: download and unpack into the Nix store Visual C++ (either from Visual C++ Express Edition or from the .NET 2.0 Framework SDK) and the Windows Platform SDK. The command line tools don't seem to need any registry settings... svn path=/nixpkgs/trunk/; revision=5369
2006-06-02 11:56:10 +02:00
accountsservice: be consistent in naming (always two 's') The package is (correctly) named 'accountsservice' (with two 's'), but the attribute and expression path lacked one 's'. Fix it.
2014-06-22 21:03:19 +02:00
accountsservice = callPackage ../development/libraries/accountsservice { };
Add accountservice, needed for gdm.
2014-01-11 23:38:21 +01:00
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
acl = callPackage ../development/libraries/acl { };
Added acl package and fixed attr package. svn path=/nixpkgs/trunk/; revision=9963
2007-12-23 16:09:12 +01:00
Add apache-activemq 5.8.0, a Java message broker.
2013-02-25 11:39:19 +01:00
activemq = callPackage ../development/libraries/apache-activemq { };
adns: dropped obsolete versions and static-only feature svn path=/nixpkgs/trunk/; revision=27890
2011-07-21 22:58:34 +02:00
adns = callPackage ../development/libraries/adns { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
Adding afflib svn path=/nixpkgs/trunk/; revision=28129
2011-08-02 21:46:28 +02:00
afflib = callPackage ../development/libraries/afflib {};
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
agg = callPackage ../development/libraries/agg { };
add xchat and tcl svn path=/nixpkgs/trunk/; revision=4302
2005-11-22 13:05:36 +01:00
Adding Allegro library svn path=/nixpkgs/trunk/; revision=24891
2010-11-27 19:31:05 +01:00
allegro = callPackage ../development/libraries/allegro {};
Adding Allegro 5 svn path=/nixpkgs/trunk/; revision=29482
2011-09-25 23:07:48 +02:00
allegro5 = callPackage ../development/libraries/allegro/5.nix {};
Add fresh (unstable) Allegro 5, too
2014-07-01 10:41:07 +02:00
allegro5unstable = callPackage
../development/libraries/allegro/5-unstable.nix {};
Adding Allegro library svn path=/nixpkgs/trunk/; revision=24891
2010-11-27 19:31:05 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
amrnb = callPackage ../development/libraries/amrnb { };
Adding amr support in mplayer. That should be enabled by the user, because those libraries are not redistributable. I don't know if the 'unfree' in the amr libraries will stop mplayer being built without its support. We would have to write the all-packages MPlayer expression different, in this case. svn path=/nixpkgs/trunk/; revision=17635
2009-10-04 23:31:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
amrwb = callPackage ../development/libraries/amrwb { };
Adding amr support in mplayer. That should be enabled by the user, because those libraries are not redistributable. I don't know if the 'unfree' in the amr libraries will stop mplayer being built without its support. We would have to write the all-packages MPlayer expression different, in this case. svn path=/nixpkgs/trunk/; revision=17635
2009-10-04 23:31:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
apr = callPackage ../development/libraries/apr { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
aprutil = callPackage ../development/libraries/apr-util {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
bdbSupport = true;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Adding the racing videogame VDrift. I added the asio library as a side effect. svn path=/nixpkgs/trunk/; revision=26575
2011-03-28 18:08:21 +02:00
asio = callPackage ../development/libraries/asio { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
aspell = callPackage ../development/libraries/aspell { };
Added acl package and fixed attr package. svn path=/nixpkgs/trunk/; revision=9963
2007-12-23 16:09:12 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
aspellDicts = recurseIntoAttrs (import ../development/libraries/aspell/dictionaries.nix {
inherit fetchurl stdenv aspell which;
});
Added acl package and fixed attr package. svn path=/nixpkgs/trunk/; revision=9963
2007-12-23 16:09:12 +01:00
* More cleanup. Updated to the latest Stratego/XT 0.17. svn path=/nixpkgs/trunk/; revision=14610
2009-03-19 15:34:16 +01:00
aterm = aterm25;
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
aterm25 = callPackage ../development/libraries/aterm/2.5.nix { };
* A wrapper around the Visual C++ compiler and the Windows SDK. TODO: download and unpack into the Nix store Visual C++ (either from Visual C++ Express Edition or from the .NET 2.0 Framework SDK) and the Windows Platform SDK. The command line tools don't seem to need any registry settings... svn path=/nixpkgs/trunk/; revision=5369
2006-06-02 11:56:10 +02:00
added seperate meta-environment packages, use callpackage for aterm28 svn path=/nixpkgs/trunk/; revision=23394
2010-08-24 15:20:55 +02:00
aterm28 = lowPrio (callPackage ../development/libraries/aterm/2.8.nix { });
Added aterm 2.5 svn path=/nixpkgs/trunk/; revision=10370
2008-01-29 10:32:56 +01:00
* Move Attica and polkit-qt-1 out of desktops/kde (since they're not part of a KDE release). svn path=/nixpkgs/branches/kde-4.7/; revision=27643
2011-07-07 22:47:38 +02:00
attica = callPackage ../development/libraries/attica { };
* Get rid of the ugly `useFromStdenv' hack in all-packages.nix. Instead, use the generic package override mechanism to use packages from earlier bootstrap phases. * Don't rely on the existence of attributes such as `stdenv.coreutils'. svn path=/nixpkgs/trunk/; revision=22991
2010-08-06 12:34:34 +02:00
attr = callPackage ../development/libraries/attr { };
Added jikes, IBM's open source java compiler. svn path=/nixpkgs/trunk/; revision=715
2004-01-24 23:50:47 +01:00
Move at_spi2_core and at_spi2_atk outside of the gnome3 attrset
2014-07-08 18:00:00 +02:00
at_spi2_core = callPackage ../development/libraries/at-spi2-core { };
at_spi2_atk = callPackage ../development/libraries/at-spi2-atk { };
Add bunch of kmymoney-4.6.1 dependencies svn path=/nixpkgs/trunk/; revision=31436
2012-01-08 20:29:07 +01:00
aqbanking = callPackage ../development/libraries/aqbanking { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
aubio = callPackage ../development/libraries/aubio { };
adding aubio svn path=/nixpkgs/trunk/; revision=17326
2009-09-21 11:58:38 +02:00
audiofile: Use default gcc
2014-07-23 11:28:26 +02:00
audiofile = callPackage ../development/libraries/audiofile { };
Add a module for the pommed tool for Apple laptop keyboards. svn path=/nixpkgs/trunk/; revision=33286
2012-03-20 05:41:13 +01:00
gimp: revert broken gimp-2.6 dependencies
2012-08-22 22:13:43 +02:00
babl_0_0_22 = callPackage ../development/libraries/babl/0_0_22.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
babl = callPackage ../development/libraries/babl { };
Ruby svn path=/nixpkgs/trunk/; revision=2990
2005-05-05 01:36:28 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
beecrypt = callPackage ../development/libraries/beecrypt { };
Added spidermonkey. svn path=/nixpkgs/trunk/; revision=5227
2006-04-26 16:47:16 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
boehmgc = callPackage ../development/libraries/boehm-gc { };
added version to uuagc added: noweb, lua-5.x, lua-4.x, mk, qc-- (as qcmm) svn path=/nixpkgs/trunk/; revision=4681
2006-02-02 18:07:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
boolstuff = callPackage ../development/libraries/boolstuff { };
adding boolstuff svn path=/nixpkgs/trunk/; revision=17026
2009-09-10 18:57:50 +02:00
boost: updated to version 1.47.0 Packages that don't build with the latest libraries can use 'boost144', which is the version we had before. svn path=/nixpkgs/trunk/; revision=27740
2011-07-12 16:24:01 +02:00
boost144 = callPackage ../development/libraries/boost/1.44.nix { };
boost: updated to version 1.49 svn path=/nixpkgs/trunk/; revision=32562
2012-02-25 20:22:06 +01:00
boost149 = callPackage ../development/libraries/boost/1.49.nix { };
boost: say hello to version 1.55.0
2013-11-11 22:08:30 +01:00
boost155 = callPackage ../development/libraries/boost/1.55.nix { };
boost = boost155;
* Provide a patched ATerm library that works on 64-bit systems and on systems with Glibc 2.5 or GCC 4.1.x. svn path=/nixpkgs/trunk/; revision=7032
2006-11-14 16:55:57 +01:00
boost: generalize the header-only expression The 'header-only-wrapper' expression can now wrap any version of boost that's passed to it as an argument.
2013-07-03 21:38:34 +02:00
boostHeaders = callPackage ../development/libraries/boost/header-only-wrapper.nix { };
Made mosh use boostHeaders, and not boost. A much lighter dependency, of great help on the Sheevaplug. I'm not sure of the name 'boostHeaders' and 'boostHeaders149'. Changes welcome. svn path=/nixpkgs/trunk/; revision=33806
2012-04-17 00:16:38 +02:00
Update Botan svn path=/nixpkgs/trunk/; revision=24639
2010-11-10 15:48:42 +01:00
botan = callPackage ../development/libraries/botan { };
Add Botan unstable branch - 1.11.9 release
2014-07-04 19:22:58 +02:00
botanUnstable = callPackage ../development/libraries/botan/unstable.nix { };
Updated Monotone to 0.43 svn path=/nixpkgs/trunk/; revision=14704
2009-03-25 17:06:00 +01:00
Adding Box2D library svn path=/nixpkgs/trunk/; revision=25172
2010-12-17 14:02:17 +01:00
box2d = callPackage ../development/libraries/box2d { };
Fix typo in box2d 2.0.1 name svn path=/nixpkgs/trunk/; revision=25175
2010-12-17 15:16:17 +01:00
box2d_2_0_1 = callPackage ../development/libraries/box2d/2.0.1.nix { };
Adding Box2D library svn path=/nixpkgs/trunk/; revision=25172
2010-12-17 14:02:17 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
buddy = callPackage ../development/libraries/buddy { };
maude, tecla, buddy: new packages Maude is a high-level specification language. Buddy and libtecla are required to build Maude. svn path=/nixpkgs/trunk/; revision=12358
2008-07-15 11:58:30 +02:00
Add tkabber dependency bwidget v1.9.5.
2012-06-04 20:05:11 +02:00
bwidget = callPackage ../development/libraries/bwidget { };
curl: Add support for c-ares, asynchronous dns resolver
2013-08-08 18:33:39 +02:00
c-ares = callPackage ../development/libraries/c-ares {
fetchurl = fetchurlBoot;
};
Add c-ares DNS library I love it when packages just need name and src Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-23 23:09:04 +02:00
Adding caelum (I want RoR) svn path=/nixpkgs/trunk/; revision=32548
2012-02-24 21:34:35 +01:00
caelum = callPackage ../development/libraries/caelum { };
capnproto: Add package
2014-04-25 17:18:18 +02:00
capnproto = callPackage ../development/libraries/capnproto { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
scmccid = callPackage ../development/libraries/scmccid { };
Adding propietary drivers for the SCM smart card readers. svn path=/nixpkgs/trunk/; revision=19378
2010-01-12 20:22:22 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ccrtp = callPackage ../development/libraries/ccrtp { };
Twinkle needs an older version of ccrtp svn path=/nixpkgs/trunk/; revision=27333
2011-05-31 11:09:35 +02:00
ccrtp_1_8 = callPackage ../development/libraries/ccrtp/1.8.nix { };
adding twinkle, a voice over IP phone software svn path=/nixpkgs/trunk/; revision=17303
2009-09-20 19:01:19 +02:00
Adding GSM and CELT codecs; dependencies of sflphone - failed to buuild itself svn path=/nixpkgs/trunk/; revision=27364
2011-06-07 16:42:24 +02:00
celt = callPackage ../development/libraries/celt {};
celt_0_7 = callPackage ../development/libraries/celt/0.7.nix {};
add celt-0.5.1
2012-08-28 00:35:29 +02:00
celt_0_5_1 = callPackage ../development/libraries/celt/0.5.1.nix {};
adding twinkle, a voice over IP phone software svn path=/nixpkgs/trunk/; revision=17303
2009-09-20 19:01:19 +02:00
Adding CGAL: Computational Geometry Algorithms Library svn path=/nixpkgs/trunk/; revision=31868
2012-01-26 19:28:53 +01:00
cgal = callPackage ../development/libraries/CGAL {};
Add CGUI library svn path=/nixpkgs/trunk/; revision=24894
2010-11-27 20:38:34 +01:00
cgui = callPackage ../development/libraries/cgui {};
Add Check, a unit testing framework for C. svn path=/nixpkgs/trunk/; revision=24127
2010-10-07 09:29:36 +02:00
check = callPackage ../development/libraries/check { };
Added chipmunk 2 physics library svn path=/nixpkgs/trunk/; revision=13519
2008-11-30 16:05:43 +01:00
chipmunk = builderDefsPackage (import ../development/libraries/chipmunk) {
inherit cmake freeglut mesa;
inherit (xlibs) libX11 xproto inputproto libXi libXmu;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
chmlib = callPackage ../development/libraries/chmlib { };
Added aspell Added gtkspell Added pidgin, builds but does not run yet: running pidgin fails to find libX11.so.6. ldd on pidgin reports: libX11.so.6 => not found .... libX11.so.6 => /nix/store/brsva6rh1p2ymjvk7054a90is5panrhf-libX11-1.1.1/lib/libX11.so.6 (0xb7358000) which looks a bit weird ... Maybe some problem with patchelf? Or just a build problem and should the library path be set using an environment variable? svn path=/nixpkgs/trunk/; revision=8660
2007-05-13 16:22:24 +02:00
chromaprint: Add new package in version 0.7. This is the core component of the AcoustID project and is the library for extracting/querying of audio fingerprints. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-08-14 18:34:46 +02:00
chromaprint = callPackage ../development/libraries/chromaprint { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cil = callPackage ../development/libraries/cil { };
* aspell: hacked up a little patch to allow additional dictionary directories to be specified through the environment variable ASPELL_EXTRA_DICT_DIRS. This way dictionaries don't have to be installed into aspell's prefix. Instead you can just set ASPELL_EXTRA_DICT_DIRS to $HOME/.nix-profile/lib/aspell and install dictionaries separately with nix-env (e.g. "nix-env -i aspell-dict-nl"). * Added a bunch of Aspell dictionaries. Additional dictionaries can be added easily in development/libraries/aspell/dictionaries.nix. svn path=/nixpkgs/trunk/; revision=9512
2007-10-23 18:33:11 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
cilaterm = callPackage ../development/libraries/cil-aterm {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
stdenv = overrideInStdenv stdenv [gnumake380];
};
added version to uuagc added: noweb, lua-5.x, lua-4.x, mk, qc-- (as qcmm) svn path=/nixpkgs/trunk/; revision=4681
2006-02-02 18:07:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
clanlib = callPackage ../development/libraries/clanlib { };
add xchat and tcl svn path=/nixpkgs/trunk/; revision=4302
2005-11-22 13:05:36 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
classads = callPackage ../development/libraries/classads { };
applying patches provided by griswold svn path=/nixpkgs/trunk/; revision=19707
2010-01-27 13:12:35 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
classpath = callPackage ../development/libraries/java/classpath {
Add GNU Classpath. svn path=/nixpkgs/trunk/; revision=16527
2009-07-31 11:59:45 +02:00
javac = gcj;
jvm = gcj;
gconf = gnome.GConf;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
clearsilver = callPackage ../development/libraries/clearsilver { };
Added gwydion-dylan to nixpkgs svn path=/nixpkgs/trunk/; revision=1786
2004-11-19 18:47:17 +01:00
Add cln svn path=/nixpkgs/trunk/; revision=23179
2010-08-15 15:54:27 +02:00
cln = callPackage ../development/libraries/cln { };
* PCRE updated to 8.21. Also enable Unicode support by default, since it only increases the size of the library a little bit. svn path=/nixpkgs/branches/stdenv-updates/; revision=30886
2011-12-14 14:36:38 +01:00
clppcre = builderDefsPackage (import ../development/libraries/cl-ppcre) { };
bison: use version 2.3 by default (the latest) svn path=/nixpkgs/trunk/; revision=12703
2008-08-25 15:25:07 +02:00
Add clucene-core.2.x
2012-08-29 22:31:26 +02:00
clucene_core_2 = callPackage ../development/libraries/clucene-core/2.x.nix { };
clucene_core: switch to versioning scheme to make overriding easier
2013-12-23 11:35:35 +01:00
clucene_core_1 = callPackage ../development/libraries/clucene-core { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
clucene_core: switch to versioning scheme to make overriding easier
2013-12-23 11:35:35 +01:00
clucene_core = clucene_core_1;
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
clutter = callPackage ../development/libraries/clutter { };
Add Clutter{,-GTK}, a library for fancy GUIs. svn path=/nixpkgs/trunk/; revision=22648
2010-07-19 00:45:03 +02:00
Add clutter 1.18
2014-05-19 18:20:02 +02:00
clutter_1_18 = callPackage ../development/libraries/clutter/1.18.nix {
cogl = cogl_1_18;
};
clutter-gst: new package
2014-02-19 23:21:19 +01:00
clutter-gst = callPackage ../development/libraries/clutter-gst { };
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
clutter_gtk = callPackage ../development/libraries/clutter-gtk { };
Restore clutter-gtk svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33290
2012-03-20 12:16:01 +01:00
clutter_gtk_0_10 = callPackage ../development/libraries/clutter-gtk/0.10.8.nix { };
Add Clutter{,-GTK}, a library for fancy GUIs. svn path=/nixpkgs/trunk/; revision=22648
2010-07-19 00:45:03 +02:00
Adding cminpack svn path=/nixpkgs/trunk/; revision=26204
2011-03-08 10:19:32 +01:00
cminpack = callPackage ../development/libraries/cminpack { };
Add cogl svn path=/nixpkgs/trunk/; revision=30291
2011-11-07 17:48:05 +01:00
cogl = callPackage ../development/libraries/cogl { };
Add cogl 1.18
2014-05-19 14:53:06 +02:00
cogl_1_18 = callPackage ../development/libraries/cogl/1.18.nix { };
Adding xercesc, the references to coin3d and soqt, and trying to add freecad (that still does not build). svn path=/nixpkgs/trunk/; revision=26135
2011-03-02 18:18:30 +01:00
coin3d = callPackage ../development/libraries/coin3d { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
commoncpp2 = callPackage ../development/libraries/commoncpp2 { };
adding twinkle, a voice over IP phone software svn path=/nixpkgs/trunk/; revision=17303
2009-09-20 19:01:19 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
confuse = callPackage ../development/libraries/confuse { };
Adding xburst-tools to manage the USB_BOOT mode of the Ben Nanonote (reflashing, ...) I add the 'confuse' library as a side effect. svn path=/nixpkgs/trunk/; revision=22817
2010-07-30 01:25:42 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
coredumper = callPackage ../development/libraries/coredumper { };
add boost svn path=/nixpkgs/trunk/; revision=8874
2007-06-12 17:35:57 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ctl = callPackage ../development/libraries/ctl { };
Lisp isn't a language, it's a building material (Alan Kay). svn path=/nixpkgs/trunk/; revision=1314
2004-08-23 12:44:21 +02:00
Add cpp-netlib library
2014-05-17 15:32:56 +02:00
cpp-netlib = callPackage ../development/libraries/cpp-netlib { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cppunit = callPackage ../development/libraries/cppunit { };
gimp+php in all-packages svn path=/nixpkgs/trunk/; revision=3808
2005-09-12 00:39:06 +02:00
Adding cppnetlib 0.9.2. The last I found in their github. svn path=/nixpkgs/trunk/; revision=31901
2012-01-27 21:40:44 +01:00
cppnetlib = callPackage ../development/libraries/cppnetlib {
cppnetlib: build with boostHeaders
2012-07-07 11:45:36 +02:00
boost = boostHeaders;
Adding cppnetlib 0.9.2. The last I found in their github. svn path=/nixpkgs/trunk/; revision=31901
2012-01-27 21:40:44 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cracklib = callPackage ../development/libraries/cracklib { };
* development/libraries/gnome/*: upgraded all gnome packages to 2.8.3. * development/libraries/gnome/*: copied gtk packages to gnome directory. gnome 2.8.3 did not work on gtk 2.4 nor gtk 2.6. Using the specific version of the gnome platform 2.8.3 directory 'solved' the issue. * development/libraries/gnome/gnome-icon-theme: new packag * development/libraries/gnome/libgtkhtml: new package * development/libraries/gnome/gtkhtml: new package * development/libraries/gnome/libgnomeprint: new package * development/libraries/gnome/libgnomeprintui: new package * development/libraries/gnome/gnome-keyring: new package * development/libraries/gnome/gail: new package * applications/editors/monodoc: new package svn path=/nixpkgs/trunk/; revision=2312
2005-02-27 00:45:19 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cryptopp = callPackage ../development/libraries/crypto++ { };
Add Crypto++, a C++ cryptography library. svn path=/nixpkgs/trunk/; revision=12444
2008-07-29 16:26:03 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cyrus_sasl = callPackage ../development/libraries/cyrus-sasl { };
* Added the j2sdk of Sun for Linux. Downloading this thing is a big problem, so I decided to require to user to get the file and put it in some location in the file system. wget doesn't seem to accept the file scheme however, so I had to move the copying into the builder itself. The builder checks the md5 hash of the downloaded file. Maybe having a separate 'fetchfile' would be useful to make a file in the outside world pure. I tried to add this to build-support, but this obviously did not work. I still committed it. Just remove it if you think that it sucks. svn path=/nixpkgs/trunk/; revision=716
2004-01-25 00:46:00 +01:00
db: Reorganize Berkeley Database Packaging Currently, the berkeley databases resuses a lot of the same code for the expressions of each version. This consolidates all of the build routines similar to that of the linux kernel. This patch also adds version 6 of BDB.
2014-01-31 10:25:49 +01:00
# Make bdb5 the default as it is the last release under the custom
# bsd-like license
db = db5;
db4: change default 4.5 -> 4.8
2013-12-10 15:43:47 +01:00
db4 = db48;
db: Reorganize Berkeley Database Packaging Currently, the berkeley databases resuses a lot of the same code for the expressions of each version. This consolidates all of the build routines similar to that of the linux kernel. This patch also adds version 6 of BDB.
2014-01-31 10:25:49 +01:00
db44 = callPackage ../development/libraries/db/db-4.4.nix { };
db45 = callPackage ../development/libraries/db/db-4.5.nix { };
db47 = callPackage ../development/libraries/db/db-4.7.nix { };
db48 = callPackage ../development/libraries/db/db-4.8.nix { };
db5: Add package
2014-01-31 04:51:26 +01:00
db5 = db53;
db53 = callPackage ../development/libraries/db/db-5.3.nix { };
db: Reorganize Berkeley Database Packaging Currently, the berkeley databases resuses a lot of the same code for the expressions of each version. This consolidates all of the build routines similar to that of the linux kernel. This patch also adds version 6 of BDB.
2014-01-31 10:25:49 +01:00
db6 = db60;
db60 = callPackage ../development/libraries/db/db-6.0.nix { };
db5: Add package
2014-01-31 04:51:26 +01:00
Fix .deepOverride on poppler, glib By moving the default derivation into callPackage call, close #1115.
2013-10-24 18:08:48 +02:00
dbus = callPackage ../development/libraries/dbus { };
dbus_* naming reorganization
2013-03-23 20:31:37 +01:00
dbus_cplusplus = callPackage ../development/libraries/dbus-cplusplus { };
dbus_glib = callPackage ../development/libraries/dbus-glib { };
dbus_java = callPackage ../development/libraries/java/dbus-java { };
dbus_python = callPackage ../development/python-modules/dbus { };
Make dbus overridable
2014-04-16 16:44:27 +02:00
dbus: minor update, reorganize and polish the expression
2013-04-11 22:12:00 +02:00
# Should we deprecate these? Currently there are many references.
Make dbus overridable
2014-04-16 16:44:27 +02:00
dbus_tools = pkgs.dbus.tools;
dbus_libs = pkgs.dbus.libs;
dbus_daemon = pkgs.dbus.daemon;
Added dbus-java and libmatthew-java (dependency for dbus-java) packages svn path=/nixpkgs/trunk/; revision=19170
2010-01-02 14:28:51 +01:00
added dhex, a nice ncurses based hex editor for the shell
2013-07-31 17:20:23 +02:00
dhex = callPackage ../applications/editors/dhex { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dclib = callPackage ../development/libraries/dclib { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Dillo: new package Dillo is a lightweight, fast web browser.
2014-04-17 14:59:31 +02:00
dillo = callPackage ../applications/networking/browsers/dillo {
all-packages.nix: strip trailing whitespace
2014-05-04 14:39:40 +02:00
fltk = fltk13;
Dillo: new package Dillo is a lightweight, fast web browser.
2014-04-17 14:59:31 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
directfb = callPackage ../development/libraries/directfb { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Trying to add mumble. It still does not build. svn path=/nixpkgs/trunk/; revision=25890
2011-02-10 20:23:27 +01:00
dotconf = callPackage ../development/libraries/dotconf { };
Adding GTK-VNC svn path=/nixpkgs/trunk/; revision=25547
2011-01-13 23:21:09 +01:00
dssi = callPackage ../development/libraries/dssi {};
llvm: Split llvmFull into separate derivations Now most packages in the llvm suite are built as separate derivations. The exceptions are: * compiler-rt must currently be built with llvm. This increases llvm's size by 6 MB * clang-tools-extra must be built with clang In addition, the top-level llvm attribute is defaulted to llvm 3.4, and llvm 3.3 must be accessed by the llvm_33 attribute. This is to make the out-of-date packages obvious in the hope that eventually all will be updated to work with 3.4 and 3.3 can be removed. I think we should keep this policy in the future (latest llvm gets top-level name, the rest are versioned until they can be removed). The llvm packages (except libc++, which exception I will try to remove on the next update) can all be accessed via the llvmPackages attribute, and there are also aliases for the packages that already existed (llvm, clang, and dragonegg). Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 02:19:53 +01:00
dragonegg = llvmPackages.dragonegg;
llvm update attempt + dragonegg svn path=/nixpkgs/trunk/; revision=22234
2010-06-12 19:42:33 +02:00
Fix typo
2012-08-27 13:49:33 +02:00
dxflib = callPackage ../development/libraries/dxflib {};
Adding Sphere of Influence svn path=/nixpkgs/trunk/; revision=25711
2011-01-28 09:13:52 +01:00
eigen = callPackage ../development/libraries/eigen {};
eigen: adding back eigen 2.0, for kde. Kdeedu wants eigen 2.0.
2012-12-14 12:44:24 +01:00
eigen2 = callPackage ../development/libraries/eigen/2.0.nix {};
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
enchant = callPackage ../development/libraries/enchant { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Adding a more-or-less working 'egoboo'. I'll update to a better expression after some egoboo upstream work. svn path=/nixpkgs/trunk/; revision=23408
2010-08-24 21:36:42 +02:00
enet = callPackage ../development/libraries/enet { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
enginepkcs11 = callPackage ../development/libraries/enginepkcs11 { };
Adding engine_pkcs11, a openssl engine for pkcs11 implementations for smartcards. svn path=/nixpkgs/trunk/; revision=19324
2010-01-09 23:22:41 +01:00
Add epoxy: A library for handling OpenGL function pointer management
2014-07-27 12:14:38 +02:00
epoxy = callPackage ../development/libraries/epoxy {
inherit (xorg) utilmacros libX11;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
esdl = callPackage ../development/libraries/esdl { };
Adding Wings 3D (as a side effect, update erlang, and add esdl). svn path=/nixpkgs/trunk/; revision=22436
2010-07-01 11:08:37 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
exiv2 = callPackage ../development/libraries/exiv2 { };
Added some parts of kde-4. It doesn't work yet, but I need version control svn path=/nixpkgs/trunk/; revision=9049
2007-08-05 15:54:42 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
expat = callPackage ../development/libraries/expat { };
Fixed strategoxt and added the Java packages to all-package-generic svn path=/nixpkgs/trunk/; revision=1256
2004-08-10 13:07:50 +02:00
extreme-tux-racer: update to 0.6.0
2014-08-29 13:09:05 +02:00
extremetuxracer = callPackage ../games/extremetuxracer {
Extreme Tux Racer still requires libpng 1.2 svn path=/nixpkgs/trunk/; revision=33769
2012-04-13 07:32:12 +02:00
libpng = libpng12;
All-packages.nix updates.. svn path=/nixpkgs/trunk/; revision=14153
2009-02-21 19:59:15 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
eventlog = callPackage ../development/libraries/eventlog { };
Added syslog-ng (and the eventlog library that it depends on). svn path=/nixpkgs/trunk/; revision=13988
2009-02-05 17:50:45 +01:00
Use default ocaml in libfacile svn path=/nixpkgs/trunk/; revision=27388
2011-06-07 23:51:00 +02:00
facile = callPackage ../development/libraries/facile { };
exrviewer added (needs ctl openexr openexr_ctl) fltk update ilmbase updated ndiswrapper does compile but has to be integrated into the kernel somehow svn path=/nixpkgs/trunk/; revision=9863
2007-12-05 22:25:47 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
faac = callPackage ../development/libraries/faac { };
added faad2 and faac (deps of cinelerra) svn path=/nixpkgs/trunk/; revision=13067
2008-10-14 16:01:38 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
faad2 = callPackage ../development/libraries/faad2 { };
added faad2 and faac (deps of cinelerra) svn path=/nixpkgs/trunk/; revision=13067
2008-10-14 16:01:38 +02:00
Make nixpkgs ready for gst_all attrset removal svn path=/nixpkgs/trunk/; revision=33092
2012-03-14 23:44:52 +01:00
farsight2 = callPackage ../development/libraries/farsight2 { };
add farsight2 svn path=/nixpkgs/trunk/; revision=19135
2009-12-27 16:27:45 +01:00
Fix file name used for libcdio 0.82
2014-02-02 22:35:33 +01:00
farstream = callPackage ../development/libraries/farstream {
Update/fix farstream: Gajim now at least builds
2014-02-02 16:07:03 +01:00
inherit (gst_all_1)
gstreamer gst-plugins-base gst-python gst-plugins-good gst-plugins-bad
gst-libav;
};
Add farstream svn path=/nixpkgs/trunk/; revision=33127
2012-03-15 22:49:54 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fcgi = callPackage ../development/libraries/fcgi { };
fcgi library added svn path=/nixpkgs/trunk/; revision=10552
2008-02-08 11:54:56 +01:00
ffmpeg: order and cleanup versions
2013-12-11 01:04:26 +01:00
ffmpeg_0_6 = callPackage ../development/libraries/ffmpeg/0.6.nix {
logic cleanup
2012-10-03 23:43:19 +02:00
vpxSupport = !stdenv.isMips;
Make mplayer build on the loongson2f svn path=/nixpkgs/branches/stdenv-updates/; revision=23578
2010-09-01 10:36:09 +02:00
};
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
ffmpeg: order and cleanup versions
2013-12-11 01:04:26 +01:00
ffmpeg_0_6_90 = callPackage ../development/libraries/ffmpeg/0.6.90.nix {
Fixing the Ultrastardx build. Not tested if it works and how.
2013-12-07 00:07:04 +01:00
vpxSupport = !stdenv.isMips;
};
ffmpeg: order and cleanup versions
2013-12-11 01:04:26 +01:00
ffmpeg_0_10 = callPackage ../development/libraries/ffmpeg/0.10.nix {
logic cleanup
2012-10-03 23:43:19 +02:00
vpxSupport = !stdenv.isMips;
ffmpeg: order and cleanup versions
2013-12-11 01:04:26 +01:00
stdenv = if stdenv.isDarwin
then overrideGCC stdenv gccApple
else stdenv;
Make mplayer build on the loongson2f svn path=/nixpkgs/branches/stdenv-updates/; revision=23578
2010-09-01 10:36:09 +02:00
};
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
ffmpeg: update to 1.2 (and patching mplayer2) Simple patch required by mplayer2 to build with ffmpeg 1.2.
2013-04-04 22:57:08 +02:00
ffmpeg_1 = callPackage ../development/libraries/ffmpeg/1.x.nix {
Adding ffmpeg 1.1 Moving packages using 1.0 to using 1.1. Vlc built fine here.
2013-01-14 00:40:23 +01:00
vpxSupport = !stdenv.isMips;
};
all-packages.nix: remove redundant texinfo5 overrides Texinfo 5.x is the default version now.
2014-01-21 20:29:34 +01:00
ffmpeg_2 = callPackage ../development/libraries/ffmpeg/2.x.nix { };
Adding ffmpeg 2.x
2013-12-04 21:04:30 +01:00
ffmpeg: change default 0.10 -> 2.0 This commit, and the "pinnings" that follow should not cause major issues. I personally checked (build-only) each and every package that depends on ffmpeg to find the maximum supported version. I performed this on stdenv-updates+glibc2.18+x-updates but I don't expect that to matter.
2013-12-11 01:05:03 +01:00
ffmpeg = ffmpeg_2;
ffmpeg: switch to default versioning-scheme
2013-12-11 00:58:53 +01:00
Adding avxsynth. To add it, I also add ffms and log4cpp.
2013-04-10 15:12:02 +02:00
ffms = callPackage ../development/libraries/ffms { };
fftw: minor update and major refactoring - Unify the "single" and "float" variants, which are the same thing. - Enable threads and openmp wrapper by default (they are very small). - Don't use sse on i686, as I'm quite sure we have no warrant for that. Cf. http://en.wikipedia.org/wiki/Pentium_Pro - Disable static libs (big, no indication we need them). - I tested most builds using fftw (they build OK).
2014-01-01 11:51:56 +01:00
fftw = callPackage ../development/libraries/fftw { };
fftwSinglePrec = fftw.override { precision = "single"; };
fftwFloat = fftwSinglePrec; # the configure option is just an alias
Added cyrus-sasl-2.1.22 with openssl svn path=/nixpkgs/trunk/; revision=9388
2007-10-01 17:11:38 +02:00
Adding flann svn path=/nixpkgs/trunk/; revision=26205
2011-03-08 10:19:37 +01:00
flann = callPackage ../development/libraries/flann { };
Bump flite to 1.4, move to libraries svn path=/nixpkgs/trunk/; revision=26759
2011-04-08 18:15:44 +02:00
flite = callPackage ../development/libraries/flite { };
fltk-1.3.0 svn path=/nixpkgs/trunk/; revision=31223
2012-01-03 11:02:33 +01:00
fltk13 = callPackage ../development/libraries/fltk/fltk13.nix { };
Adding cinepaint 0.22.1 and as a dependency, also fltk 1.1.9 svn path=/nixpkgs/trunk/; revision=14841
2009-04-02 17:20:19 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fltk20 = callPackage ../development/libraries/fltk { };
* Berkeley DB 4.5.20. svn path=/nixpkgs/trunk/; revision=6729
2006-10-13 14:58:13 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fmod = callPackage ../development/libraries/fmod { };
Adding fmod. svn path=/nixpkgs/trunk/; revision=14193
2009-02-22 23:06:20 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
freeimage = callPackage ../development/libraries/freeimage { };
Committing Lluís Batlle's submissions from mailing list posting <45219fb00901110456i6f21db35tbd1894eaea2146ff@mail.gmail.com>: * nixpkgs-ccrypt-1.7-new.patch * nixpkgs-cmake-add-ccmake.patch * nixpkgs-cpufrequtils-005-new.patch * nixpkgs-dwm-5.1-fix.patch * nixpkgs-freeimage-3.11.0-new.patch * nixpkgs-proxychains-3.1-new.patch * nixpkgs-psi-to-0.12.patch * nixpkgs-skype-to-2.0.0.72.patch * nixpkgs-truecrypt-6.1a-fix.patch * nixpkgs-vxl-1.11.0-new.patch * nixpkgs-xkb-popular-esperanto-symbols.patch * nixpkgs-xorg-via-video-fix.patch svn path=/nixpkgs/trunk/; revision=13751
2009-01-12 22:12:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
freetts = callPackage ../development/libraries/freetts { };
Added FreeTTS package svn path=/nixpkgs/trunk/; revision=17577
2009-10-01 16:48:57 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cfitsio = callPackage ../development/libraries/cfitsio { };
cfitsio added svn path=/nixpkgs/trunk/; revision=10350
2008-01-28 20:46:59 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fontconfig = callPackage ../development/libraries/fontconfig { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Graphviz updated to 2.20.2. Now built with fontconfig, gd and pango support. * New function makeFontsConf to generate a fontconfig configuration file. Moved from NixOS. * dot2pdf: use makeFontsConf to generate a fonts.conf containing just the Ghostscript fonts (see NIXPKGS-29). * dot2pdf: generate PDF directly, don't go through PS. Note that this and using fontconfig changes the interpretation of "fontname" attributes in dot graphs. svn path=/nixpkgs/trunk/; revision=12251
2008-07-03 16:27:19 +02:00
makeFontsConf = let fontconfig_ = fontconfig; in {fontconfig ? fontconfig_, fontDirectories}:
import ../development/libraries/fontconfig/make-fonts-conf.nix {
inherit runCommand libxslt fontconfig fontDirectories;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
freealut = callPackage ../development/libraries/freealut { };
Added dbus variant with X support Default is the old variant (without X). svn path=/nixpkgs/trunk/; revision=9350
2007-09-20 21:40:22 +02:00
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
freeglut = callPackage ../development/libraries/freeglut { };
* gconf-editor and various dependencies. svn path=/nixpkgs/trunk/; revision=8171
2007-03-04 22:28:24 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
freetype = callPackage ../development/libraries/freetype { };
* gconf-editor and various dependencies. svn path=/nixpkgs/trunk/; revision=8171
2007-03-04 22:28:24 +01:00
Add frei0r: Minimalist, cross-platform, shared video plugins
2014-07-27 12:28:02 +02:00
frei0r = callPackage ../development/libraries/frei0r { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fribidi = callPackage ../development/libraries/fribidi { };
Improved Ants in Nix. The names of the various Ants now reflects the j2sdk configuration: ant-j2sdk-1.4.2, ant-j2sdk-1.5.0, ant-blackdown svn path=/nixpkgs/trunk/; revision=1325
2004-08-24 13:26:26 +02:00
Add funambol svn path=/nixpkgs/trunk/; revision=26336
2011-03-16 00:09:27 +01:00
funambol = callPackage ../development/libraries/funambol { };
Some renaming for future variants svn path=/nixpkgs/trunk/; revision=10343
2008-01-28 20:44:39 +01:00
fam = gamin;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gamin = callPackage ../development/libraries/gamin { };
gamin added svn path=/nixpkgs/trunk/; revision=10337
2008-01-28 20:41:55 +01:00
add ganv: An interactive Gtk canvas widget for graph-based interfaces
2014-03-09 18:20:45 +01:00
ganv = callPackage ../development/libraries/ganv { };
A little patch to gav, and it does not require gcc 4.1 anymore. svn path=/nixpkgs/trunk/; revision=32863
2012-03-07 23:04:53 +01:00
gav = callPackage ../games/gav { };
Adding GPL Arcade Volleyball. I had this patch _almost_ ready for a long long time. Now ready. svn path=/nixpkgs/trunk/; revision=14017
2009-02-09 23:44:36 +01:00
Gratuitous Space Battles. Needs libcurl.so.3, so put an old version of that in, too
2013-09-16 06:07:11 +02:00
gsb = callPackage ../games/gsb { };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
gdome2 = callPackage ../development/libraries/gdome2 {
inherit (gnome) gtkdoc;
* Getting rid of gtk-libs by moving the packages in gtk-libs to development/libraries/{glib,gtk+,pango,atk,...}. Done for glib/gtk+ 1.2. Also deleted some obsolete, unused versions (gtkLibs 2.10, 2.12, and 2.14). svn path=/nixpkgs/trunk/; revision=17992
2009-10-28 16:06:18 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gdbm = callPackage ../development/libraries/gdbm { };
Add GDBM, a key/value database library. svn path=/nixpkgs/trunk/; revision=11480
2008-04-07 01:18:25 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gegl = callPackage ../development/libraries/gegl {
gegl added (needs recent glibc) svn path=/nixpkgs/trunk/; revision=11465
2008-04-04 22:57:09 +02:00
# avocodec avformat librsvg
};
gimp: revert broken gimp-2.6 dependencies
2012-08-22 22:13:43 +02:00
gegl_0_0_22 = callPackage ../development/libraries/gegl/0_0_22.nix {
# avocodec avformat librsvg
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
libpng = libpng12;
gimp: revert broken gimp-2.6 dependencies
2012-08-22 22:13:43 +02:00
};
glibc: Update to 2.16
2012-09-18 18:38:43 +02:00
Adding geoclue - as framework only, feel free to build it with proper data providers if you have a reason for that svn path=/nixpkgs/trunk/; revision=25335
2011-01-02 14:23:59 +01:00
geoclue = callPackage ../development/libraries/geoclue {};
Remove libsoup_2_44
2014-01-30 18:48:16 +01:00
geoclue2 = callPackage ../development/libraries/geoclue/2.0.nix {};
changes in: redshift, geoclue, libsoup - added support for geoclue for redshift - package geoclue 2.0.0 (as geoclue2) - package libsoup 2.44.1 (as libsoup_2_40)
2013-10-29 16:23:24 +01:00
geoip: Convert to mkDerivation Also, drop unused zlib dependency and add some meta attributes.
2014-03-14 17:54:40 +01:00
geoip = callPackage ../development/libraries/geoip { };
Adding WebDruid log analyzer. In the same time, reworking source autoupdate system a bit svn path=/nixpkgs/trunk/; revision=16859
2009-08-26 13:13:36 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
geoipjava = callPackage ../development/libraries/java/geoipjava { };
Added GeoIP Java API library svn path=/nixpkgs/trunk/; revision=21626
2010-05-06 15:58:27 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
geos = callPackage ../development/libraries/geos { };
* DirectFB. svn path=/nixpkgs/trunk/; revision=7040
2006-11-14 23:23:33 +01:00
gettext, now properly svn path=/nixpkgs/branches/stdenv-updates/; revision=24868
2010-11-26 13:38:09 +01:00
gettext = gettext_0_18;
GNU gettext 0.18 (not in stdenv). svn path=/nixpkgs/trunk/; revision=21704
2010-05-10 14:57:10 +02:00
add gettext_0_17, gettext_0_18 aliases to gettext, preparation for stdenv merge, concerning gnu hydra build configuration svn path=/nixpkgs/branches/stdenv-updates/; revision=24867
2010-11-26 13:34:46 +01:00
gettext_0_17 = callPackage ../development/libraries/gettext/0.17.nix { };
gettext, now properly svn path=/nixpkgs/branches/stdenv-updates/; revision=24868
2010-11-26 13:38:09 +01:00
gettext_0_18 = callPackage ../development/libraries/gettext { };
re-add gettext 0.17 svn path=/nixpkgs/branches/stdenv-updates/; revision=24663
2010-11-11 15:42:35 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gd = callPackage ../development/libraries/gd { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gdal = callPackage ../development/libraries/gdal { };
enchant library added svn path=/nixpkgs/trunk/; revision=9455
2007-10-12 22:27:15 +02:00
Add Widelands RTS svn path=/nixpkgs/trunk/; revision=26869
2011-04-17 19:55:29 +02:00
ggz_base_libs = callPackage ../development/libraries/ggz_base_libs {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
giblib = callPackage ../development/libraries/giblib { };
* Added scrot, a command-line screen capture utility. svn path=/nixpkgs/trunk/; revision=16946
2009-09-03 00:56:33 +02:00
Add libgit2, pygit2 and powerline beta
2013-05-10 22:12:37 +02:00
libgit2 = callPackage ../development/libraries/git2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
glew = callPackage ../development/libraries/glew { };
glew added svn path=/nixpkgs/trunk/; revision=10164
2008-01-16 03:20:46 +01:00
glfw: Update packaging and add v3 This patch cleans up the previous glfw2 package. Additionally, it adds glfw3 and makes that the new default glfw version.
2014-02-04 20:13:30 +01:00
glfw = glfw3;
glfw2 = callPackage ../development/libraries/glfw/2.x.nix { };
glfw3 = callPackage ../development/libraries/glfw/3.x.nix { };
adding glefw svn path=/nixpkgs/trunk/; revision=18707
2009-11-30 02:05:02 +01:00
glibc: Rename 2.18 -> 2.19
2014-02-14 15:49:50 +01:00
glibc = callPackage ../development/libraries/glibc/2.19 {
glibc: making 2.17 the glibc to use cross-building.
2012-12-29 15:08:18 +01:00
kernelHeaders = linuxHeaders;
installLocales = config.glibc.locales or false;
machHeaders = null;
hurdHeaders = null;
gccCross = null;
};
glibc: Rename 2.18 -> 2.19
2014-02-14 15:49:50 +01:00
glibc_memusage = callPackage ../development/libraries/glibc/2.19 {
Adding a glibc variant with the memusage program
2013-08-20 10:15:40 +02:00
kernelHeaders = linuxHeaders;
installLocales = false;
withGd = true;
};
glibc: Rename 2.18 -> 2.19
2014-02-14 15:49:50 +01:00
glibcCross = forceNativeDrv (makeOverridable (import ../development/libraries/glibc/2.19)
* Move all glibc versions to development/libraries/glibc. svn path=/nixpkgs/branches/stdenv-updates/; revision=32373
2012-02-17 23:02:37 +01:00
(let crossGNU = crossSystem != null && crossSystem.config == "i586-pc-gnu";
in {
Revert stdenv glibc back to version 2.13. Note that I didn't touch the glibcCross attribute! That still points to glibc 2.14. svn path=/nixpkgs/branches/stdenv-updates/; revision=30031
2011-10-26 12:48:55 +02:00
inherit stdenv fetchurl;
glibc 2.11: Cross-build for GNU/Hurd. svn path=/nixpkgs/trunk/; revision=21752
2010-05-12 17:46:51 +02:00
gccCross = gccCrossStageStatic;
GNU libc 2.14: Fix cross-GNU builds. svn path=/nixpkgs/branches/stdenv-updates/; revision=32367
2012-02-17 21:37:31 +01:00
kernelHeaders = if crossGNU then gnu.hurdHeaders else linuxHeadersCross;
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
installLocales = config.glibc.locales or false;
glibc 2.11: Cross-build for GNU/Hurd. svn path=/nixpkgs/trunk/; revision=21752
2010-05-12 17:46:51 +02:00
}
* Move all glibc versions to development/libraries/glibc. svn path=/nixpkgs/branches/stdenv-updates/; revision=32373
2012-02-17 23:02:37 +01:00
// lib.optionalAttrs crossGNU {
GNU libc 2.14: Fix cross-GNU builds. svn path=/nixpkgs/branches/stdenv-updates/; revision=32367
2012-02-17 21:37:31 +01:00
inherit (gnu) machHeaders hurdHeaders libpthreadHeaders mig;
inherit fetchgit;
* Move all glibc versions to development/libraries/glibc. svn path=/nixpkgs/branches/stdenv-updates/; revision=32373
2012-02-17 23:02:37 +01:00
}));
Fixing a trivial error in the glibc-2.11 longDescription, and fixing the arguments for the ncurses expression. We should find a way to express a dependency in cross compilation of the style "cross-ncurses depends on having the native-ncurses". svn path=/nixpkgs/branches/stdenv-updates/; revision=18479
2009-11-20 09:27:59 +01:00
glibc: Update to 2.16
2012-09-18 18:38:43 +02:00
Making the cross-builds work with uclibc. There is no easy way of switching between uclibc/glibc still. I started the renaming from glibc to libc regarding the cross-toolchain, but I still have to finish. svn path=/nixpkgs/branches/stdenv-updates/; revision=18801
2009-12-04 14:35:58 +01:00
# We can choose:
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
libcCrossChooser = name : if name == "glibc" then glibcCross
else if name == "uclibc" then uclibcCross
Use mingw-w64 for 32bit Windows builds as well. Mingw(32) is rather poorly maintaned and has quite a lot of bugs. And because our Windows cross builds were also poorly maintained and most of the cross-tests were broken as well, I'm just taking this step and try to switch to mingw-w64 for everything "cross Windows". Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-03 22:31:18 +01:00
else if name == "msvcrt" then windows.mingw_w64
gcc-4.8: Hook in cross-darwin libc and binutils. Let's finally hook everything into the existing cross-building infrastructure. We're using --with-sysroot instead of --with-headers here, because the XCode SDK contains references to /usr/lib. I've tried to patch those references, but unfortunately (at least with install_name_tool) it isn't possible to change those refernces in stub dylibs. So after bugging @tpoechtrager with annoying questions (thanks again), I think my initial approach (patching the SDK itself and/or regenerating the dylib stubs) was way to complicated so I ended up with this implementation. Also, I've added a condition to binutilsCross to use cctools if the libc is set to libSystem. This might need some cleanups someday, mainly to figure out how to properly bridge cctools and binutils. So, as an example on how to cross-compile GNU Hello to Darwin, you can use something like this: (import <nixpkgs> { crossSystem = { config = "x86_64-apple-darwin13"; arch = "x86_64"; libc = "libSystem"; platform = {}; }; }).hello.crossDrv Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 04:10:34 +01:00
else if name == "libSystem" then darwin.xcode
Enabling cross-builds with uclibc again (I had that too much abandoned). Hydra now should even test it. svn path=/nixpkgs/trunk/; revision=20500
2010-03-09 16:48:25 +01:00
else throw "Unknown libc";
Updating from trunk, to get the main evaluation fix about libcCross. svn path=/nixpkgs/branches/stdenv-updates/; revision=20512
2010-03-09 19:17:30 +01:00
libcCross = assert crossSystem != null; libcCrossChooser crossSystem.libc;
My first attempt at getting cross compilers in nixpkgs. My idea is to provide special stdenv expressions that will contain in the path additional cross compilers. As most expressions for programs accept a stdenv parameter, we could substitute this parameter with the special stdenv, which will have a generic builder that attempts the usual "--target=..." and can additionally have an env variable like "cross" with the target architecture set. So, finally we could have additional expressions like this: bashRealArm = makeOverridable (import ../shells/bash) { inherit fetchurl bison; stdenv = stdenvCross "armv5tel-unknown-linux-gnueabi"; }; Meanwhile it does not work - I still cannot get the cross-gcc to build. I think it does not fill the previous expressions with a lot of noise, so I think it may be a good path to follow. I only touched some files of the current stdenv: gcc-4.3, kernel headers 2.6.28, glibc 2.9, ... I tried to use the gcc-cross-wrapper, that may be very outdated. Maybe I will update it, or update the gcc-wrapper expression to make it fit the cross tools, but meanwhile I even cannot build gcc, so I have not tested the wrapper. This new idea on cross compiling is not similar to that of the nixpkgs/branches/cross-compilation, which mostly added bare new expressions for anything to be cross compiled, if I understood it correctly. I cared not to break anything of the usual stdenv in all this work. svn path=/nixpkgs/branches/stdenv-updates/; revision=18343
2009-11-14 09:11:30 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
eglibc = callPackage ../development/libraries/eglibc {
Replace `kernelHeaders' by `linuxHeaders'. svn path=/nixpkgs/branches/stdenv-updates/; revision=19067
2009-12-21 15:04:45 +01:00
kernelHeaders = linuxHeaders;
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
installLocales = config.glibc.locales or false;
Porting changes from stdenv-updates into this branch. This comes from: svn diff ^/nixpkgs/trunk/@18255 ^/nixpkgs/branches/stdenv-updates/ > diff patch -p0 < diff and then adding into svn all files new from the patch. trunk@18255 comes from the last time I updated stdenv-updates from trunk. svn path=/nixpkgs/stdenv-updates2/; revision=18272
2009-11-08 01:32:12 +01:00
};
glibc: Rename 2.18 -> 2.19
2014-02-14 15:49:50 +01:00
glibcLocales = callPackage ../development/libraries/glibc/2.19/locales.nix { };
* A function to build Glibc's locale-archive separately from Glibc. svn path=/nixpkgs/branches/stdenv-updates/; revision=15155
2009-04-19 17:28:37 +02:00
glibc: Rename 2.18 -> 2.19
2014-02-14 15:49:50 +01:00
glibcInfo = callPackage ../development/libraries/glibc/2.19/info.nix { };
First attempt at adding an attribute for the libc.info glibc manual. svn path=/nixpkgs/trunk/; revision=17868
2009-10-18 17:15:39 +02:00
glibc_multi: move glibc_multi script out of all-packages.nix
2014-07-10 09:55:50 +02:00
glibc_multi = callPackage ../development/libraries/glibc/2.19/multi.nix {
inherit glibc;
glibc32 = (import ./all-packages.nix {system = "i686-linux";}).glibc;
};
Improved support for building 32-bit binaries on x86_64-linux. * glibc_multi: a wrapper that combines the 32-bit and 64-bit Glibcs. This is necessary so that 64-bit GCC can find gnu/stubs-32.h and the 32-bit Glibc libraries. To build glibc_multi on x86_64-linux, you still need either the i686-linux Glibc derivation from a channel, or to have configured Nix with support for forwarding the build to a i686-linux machine. In the future this may become unnecessary by providing a prebuilt binary of 32-bit Glibc somewhere (like the binaries used in the stdenvLinux bootstrap). * With glibc_multi, it becomes possible to build gcc with multilib support (i.e. it builds 32-bit and 64-bit versions of libgcc, libstdc++, etc.). svn path=/nixpkgs/trunk/; revision=12203
2008-06-27 20:26:19 +02:00
glm: new package OpenGL Mathematics (GLM) is a header only C++ mathematics library for graphics software based on the OpenGL Shading Language (GLSL) specification and released under the MIT license. http://glm.g-truc.net/
2014-01-18 18:38:59 +01:00
glm = callPackage ../development/libraries/glm { };
add glog 0.3.3
2014-01-24 15:51:04 +01:00
glog = callPackage ../development/libraries/glog { };
Add Gloox.
2014-06-18 23:18:31 +02:00
gloox = callPackage ../development/libraries/gloox { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
glpk = callPackage ../development/libraries/glpk { };
Add the GNU Linear Programming Kit (GLPK). Contributed by Brian Gough <bjg@gnu.org>. svn path=/nixpkgs/trunk/; revision=21284
2010-04-23 23:15:48 +02:00
whitespace cleaning
2013-06-25 09:17:34 +02:00
glsurf = callPackage ../applications/science/math/glsurf {
added glsurf package
2013-06-16 22:27:14 +02:00
inherit (ocamlPackages) lablgl findlib camlimages ocaml_mysql mlgmp;
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
libpng = libpng12;
Use old giflib for packages which lack new versions/compatibility patches for giflib5
2013-12-08 11:36:46 +01:00
giflib = giflib_4_1;
added glsurf package
2013-06-16 22:27:14 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gmime = callPackage ../development/libraries/gmime { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gmm = callPackage ../development/libraries/gmm { };
kde shipped with a copy of this lib. They have removed it. I guess we need id nevertheless? svn path=/nixpkgs/trunk/; revision=11669
2008-04-21 17:20:49 +02:00
Remove support for the obsolete powerpc-darwin and i686-darwin platforms
2012-11-29 14:10:49 +01:00
gmp = gmp5;
mpfr: only use 3.1.2 and drop 3.1.1 I tried some packages, all seem to compile fine.
2013-06-29 16:56:20 +02:00
gmp5 = gmp51;
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages.nix: append "with-cxx" to the name of gmpxx to ensure that "nix-env -i gmp" prefers this expression svn path=/nixpkgs/trunk/; revision=30995
2011-12-21 10:28:17 +01:00
gmpxx = appendToName "with-cxx" (gmp.override { cxx = true; });
all-packages.nix: added 'gmpxx', a reference to libgmp with C++ API enabled svn path=/nixpkgs/trunk/; revision=16158
2009-07-03 13:31:28 +02:00
* Fix GHC. The bootstrap binaries depend on libgmp.so.3, which is provided by GMP 4 but not GMP 5. svn path=/nixpkgs/branches/stdenv-updates/; revision=31639
2012-01-18 19:43:34 +01:00
# The GHC bootstrap binaries link against libgmp.so.3, which is in GMP 4.x.
Remove support for the obsolete powerpc-darwin and i686-darwin platforms
2012-11-29 14:10:49 +01:00
gmp4 = callPackage ../development/libraries/gmp/4.3.2.nix { };
gfortran: updated default version to 4.6.3. svn path=/nixpkgs/trunk/; revision=32838
2012-03-06 23:27:14 +01:00
gmp5: minor update 5.1.1 -> 5.1.2 and file rename
2013-06-29 16:19:56 +02:00
gmp51 = callPackage ../development/libraries/gmp/5.1.x.nix { };
gfortran: updated default version to 4.6.3. svn path=/nixpkgs/trunk/; revision=32838
2012-03-06 23:27:14 +01:00
mpfr: only use 3.1.2 and drop 3.1.1 I tried some packages, all seem to compile fine.
2013-06-29 16:56:20 +02:00
#GMP ex-satellite, so better keep it near gmp
mpfr = callPackage ../development/libraries/mpfr/default.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gobjectIntrospection = callPackage ../development/libraries/gobject-introspection { };
Add gobject-introspection svn path=/nixpkgs/trunk/; revision=21763
2010-05-13 17:56:04 +02:00
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
goocanvas = callPackage ../development/libraries/goocanvas { };
added goocanvas svn path=/nixpkgs/trunk/; revision=13552
2008-12-02 13:28:13 +01:00
google-gflags: add 2.0
2014-02-10 16:27:44 +01:00
google-gflags = callPackage ../development/libraries/google-gflags { };
gperftools: Update to 2.0 and fix build http://hydra.nixos.org/build/3875478
2013-01-28 13:48:35 +01:00
gperftools = callPackage ../development/libraries/gperftools { };
add google perftools 1.8.3 svn path=/nixpkgs/trunk/; revision=29517
2011-09-27 19:24:01 +02:00
all-packages.nix: cosmetic changes
2014-06-11 11:01:10 +02:00
gst_all_1 = recurseIntoAttrs(callPackage ../development/libraries/gstreamer {
gst-libav: update to 1.4.0
2014-07-22 12:17:13 +02:00
callPackage = pkgs.newScope (pkgs // { libav = pkgs.libav_10; });
Use the libav version compatible with our gstreamer version
2014-06-08 10:20:47 +02:00
});
add gstreamer 1.2.1
2013-12-23 16:36:37 +01:00
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
gst_all = {
inherit (pkgs) gstreamer gnonlin gst_python qt_gstreamer;
gstPluginsBase = pkgs.gst_plugins_base;
gstPluginsBad = pkgs.gst_plugins_bad;
gstPluginsGood = pkgs.gst_plugins_good;
gstPluginsUgly = pkgs.gst_plugins_ugly;
gstFfmpeg = pkgs.gst_ffmpeg;
};
Merge master into stdenv-updates Conflicts: pkgs/development/lisp-modules/stumpwm/default.nix (auto-solved) pkgs/top-level/all-packages.nix (trivial)
2014-01-12 12:27:06 +01:00
gstreamer = callPackage ../development/libraries/gstreamer/legacy/gstreamer {
gstreamer: builds only with bison 2.x
2013-09-16 10:59:26 +02:00
bison = bison2;
};
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
gstreamer-0.10: move to gstreamer/legacy
2013-12-23 16:21:43 +01:00
gst_plugins_base = callPackage ../development/libraries/gstreamer/legacy/gst-plugins-base {};
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
gstreamer-0.10: move to gstreamer/legacy
2013-12-23 16:21:43 +01:00
gst_plugins_good = callPackage ../development/libraries/gstreamer/legacy/gst-plugins-good {};
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
gstreamer-0.10: move to gstreamer/legacy
2013-12-23 16:21:43 +01:00
gst_plugins_bad = callPackage ../development/libraries/gstreamer/legacy/gst-plugins-bad {};
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
gstreamer-0.10: move to gstreamer/legacy
2013-12-23 16:21:43 +01:00
gst_plugins_ugly = callPackage ../development/libraries/gstreamer/legacy/gst-plugins-ugly {};
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
gstreamer-0.10: move to gstreamer/legacy
2013-12-23 16:21:43 +01:00
gst_ffmpeg = callPackage ../development/libraries/gstreamer/legacy/gst-ffmpeg {
gst-ffmpeg: stick to ffmpeg 0.10
2013-12-11 01:05:25 +01:00
ffmpeg = ffmpeg_0_10;
};
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
gstreamer-0.10: move to gstreamer/legacy
2013-12-23 16:21:43 +01:00
gst_python = callPackage ../development/libraries/gstreamer/legacy/gst-python {};
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
subtitleeditor, gstreamermm: new packages
2014-05-21 20:45:58 +02:00
gstreamermm = callPackage ../development/libraries/gstreamer/legacy/gstreamermm { };
gstreamer-0.10: move to gstreamer/legacy
2013-12-23 16:21:43 +01:00
gnonlin = callPackage ../development/libraries/gstreamer/legacy/gnonlin {};
Move gstreamer packages to top-level This will make callPackage work with gst. * Rename gstCamelCase to gst_with_underscores. * Add compatibility attributes. svn path=/nixpkgs/trunk/; revision=33078
2012-03-14 20:35:35 +01:00
colord, gusb: package. Part of #517.
2013-05-10 19:17:36 +02:00
gusb = callPackage ../development/libraries/gusb {
inherit (gnome) gtkdoc;
};
gstreamer-0.10: move to gstreamer/legacy
2013-12-23 16:21:43 +01:00
qt_gstreamer = callPackage ../development/libraries/gstreamer/legacy/qt-gstreamer {};
- svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10823
2008-02-22 04:06:12 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gnet = callPackage ../development/libraries/gnet { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages: remove gcc47 dependencies now gcc48 is default I checked these and they built fine
2013-12-07 20:10:55 +01:00
gnu-efi = callPackage ../development/libraries/gnu-efi { };
GNU EFI development libraries svn path=/nixpkgs/trunk/; revision=33057
2012-03-14 02:23:31 +01:00
gnutls32: update 3.2.4 -> .10, including CVE fixes Also make gnutls32 the default gnutls. CVE-2013-{4466,4487}
2014-02-06 20:45:14 +01:00
gnutls = gnutls32;
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Rename misleadingly named gnutls/default.nix (it's not the default)
2014-03-04 22:33:20 +01:00
gnutls31 = callPackage ../development/libraries/gnutls/3.1.nix {
gnutls: Update to 3.2.12, 3.1.22 CVE-2014-0092 Unfortunately, 3.2.12 doesn't pass the tests with Guile bindings enabled, so I've turned them off in the default build.
2014-03-04 22:31:02 +01:00
guileBindings = config.gnutls.guile or false;
Re-add GNU TLS 2.12 - it does fix glib-networking svn path=/nixpkgs/trunk/; revision=28853
2011-08-27 19:04:25 +02:00
};
Add gnutls 3.2.4 (as pkgs.gnutls32) & make weechat use it. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-10-07 13:44:19 +02:00
gnutls32 = callPackage ../development/libraries/gnutls/3.2.nix {
gnutls: Update to 3.2.12, 3.1.22 CVE-2014-0092 Unfortunately, 3.2.12 doesn't pass the tests with Guile bindings enabled, so I've turned them off in the default build.
2014-03-04 22:31:02 +01:00
guileBindings = config.gnutls.guile or false;
Add gnutls 3.2.4 (as pkgs.gnutls32) & make weechat use it. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-10-07 13:44:19 +02:00
};
gnutls: Update to 3.2.12, 3.1.22 CVE-2014-0092 Unfortunately, 3.2.12 doesn't pass the tests with Guile bindings enabled, so I've turned them off in the default build.
2014-03-04 22:31:02 +01:00
gnutls_with_guile = lowPrio (gnutls.override { guileBindings = true; });
GnuTLS: Get Hydra to build the Guile-less variants. svn path=/nixpkgs/trunk/; revision=32034
2012-02-05 00:21:33 +01:00
new package: GPAC
2012-11-30 11:39:40 +01:00
gpac = callPackage ../applications/video/gpac { };
gpg/pth: fixing the pth building on arm I could built pth with the fix commented in: http://forums.gentoo.org/viewtopic-t-904280-start-0.html And I remove the 'pth.supported' structure I had built.
2012-11-15 11:18:38 +01:00
gpgme = callPackage ../development/libraries/gpgme {
gnupg1 = gnupg1orig;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Add grantlee svn path=/nixpkgs/trunk/; revision=23625
2010-09-03 19:40:55 +02:00
grantlee = callPackage ../development/libraries/grantlee { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gsasl = callPackage ../development/libraries/gsasl { };
Add GNU SASL, GNU GSS-API, and GNU Rush. Contributed by Brian Gough <bjg@gnu.org>. svn path=/nixpkgs/trunk/; revision=21315
2010-04-26 10:59:25 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gsl = callPackage ../development/libraries/gsl { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Adding GSM and CELT codecs; dependencies of sflphone - failed to buuild itself svn path=/nixpkgs/trunk/; revision=27364
2011-06-07 16:42:24 +02:00
gsm = callPackage ../development/libraries/gsm {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gsoap = callPackage ../development/libraries/gsoap { };
applying patches provided by griswold svn path=/nixpkgs/trunk/; revision=19707
2010-01-27 13:12:35 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gss = callPackage ../development/libraries/gss { };
Add GNU SASL, GNU GSS-API, and GNU Rush. Contributed by Brian Gough <bjg@gnu.org>. svn path=/nixpkgs/trunk/; revision=21315
2010-04-26 10:59:25 +02:00
Make nixpkgs ready to gtkLibs attrset removal svn path=/nixpkgs/trunk/; revision=33091
2012-03-14 23:44:41 +01:00
gtkimageview = callPackage ../development/libraries/gtkimageview { };
Add GtkImageView. svn path=/nixpkgs/trunk/; revision=17880
2009-10-19 14:50:41 +02:00
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
gtkmathview = callPackage ../development/libraries/gtkmathview { };
Move gtkLibs to top-level namespace Earlier there was a strict correspondence between versions of gtkLibs.* but now upstream moves to gtk-3.x, and there is no simple rule anymore. Thus it is easier to override particular libs on a case-by-case basis than using gtkLibs2x. svn path=/nixpkgs/trunk/; revision=32040
2012-02-05 19:29:42 +01:00
gtkLibs = {
inherit (pkgs) glib glibmm atk atkmm cairo pango pangomm gdk_pixbuf gtk
gtkmm;
};
pkgs/tools/typesetting/asciidoc: updated to version 8.5.1 New asciidoc versions do have a proper configure script. Using that simplifies the build instructions a bit. svn path=/nixpkgs/trunk/; revision=18076
2009-11-03 16:57:22 +01:00
glib: Fix compilation on Darwin and use default gcc http://hydra.nixos.org/build/12458779
2014-07-15 11:09:30 +02:00
glib = callPackage ../development/libraries/glib { };
glib: add -tested variant, also to the unstable job Replaces #1753.
2014-02-18 20:03:03 +01:00
glib-tested = glib.override { doCheck = true; }; # checked version separate to break cycles
update gtk c++ bindings
2013-02-22 00:02:24 +01:00
glibmm = callPackage ../development/libraries/glibmm { };
* Finished getting rid of gtk-libs. svn path=/nixpkgs/trunk/; revision=18010
2009-10-29 11:53:54 +01:00
Move glib-networking to top namespace svn path=/nixpkgs/trunk/; revision=32905
2012-03-08 17:49:08 +01:00
glib_networking = callPackage ../development/libraries/glib-networking {};
rename the expressions of some gtk-related libraries now the default (and usually only) version is called default
2013-01-29 16:11:34 +01:00
atk = callPackage ../development/libraries/atk { };
update gtk c++ bindings
2013-02-22 00:02:24 +01:00
atkmm = callPackage ../development/libraries/atkmm { };
* Finished getting rid of gtk-libs. svn path=/nixpkgs/trunk/; revision=18010
2009-10-29 11:53:54 +01:00
non-Linux: more adjustments Also reordered stuff in all-packages.nix.
2013-06-18 23:42:25 +02:00
pixman = callPackage ../development/libraries/pixman { };
cairo: minor bugfix update, depend on new pixman now
2013-01-31 21:50:30 +01:00
cairo = callPackage ../development/libraries/cairo {
Buidling cairo without gl on arm and mips Mesa didn't build for arm, and I don't think anyone with arm wants mesa now. And I needed cairo for rrdtool.
2013-07-20 23:15:37 +02:00
glSupport = config.cairo.gl or (stdenv.isLinux &&
!stdenv.isArm && !stdenv.isMips);
cairo: minor bugfix update, depend on new pixman now
2013-01-31 21:50:30 +01:00
};
non-Linux: more adjustments Also reordered stuff in all-packages.nix.
2013-06-18 23:42:25 +02:00
cairomm = callPackage ../development/libraries/cairomm { };
* Finished getting rid of gtk-libs. svn path=/nixpkgs/trunk/; revision=18010
2009-10-29 11:53:54 +01:00
pango on darwin: amend the wrong fix I didn't realize pango doesn't depend on flex directly, only through introspection which caused build problems by itself, too.
2014-04-11 09:55:46 +02:00
pango = callPackage ../development/libraries/pango { };
pangomm: update, so we can drop older cairo
2013-12-10 17:12:32 +01:00
pangomm = callPackage ../development/libraries/pangomm { };
Mentioning GTK-2.18 in all-packages svn path=/nixpkgs/trunk/; revision=17502
2009-09-29 15:49:41 +02:00
add pangox-compat It's needed for some packages to work with pango>1.30.*
2013-02-02 14:38:17 +01:00
pangox_compat = callPackage ../development/libraries/pangox-compat { };
* GTK+ 2.20, Glib 2.24 etc. svn path=/nixpkgs/branches/x-updates/; revision=22652
2010-07-19 01:22:59 +02:00
gdk_pixbuf: tests crash on Darwin with gcc 4.8.3
2014-06-22 08:53:13 +02:00
gdk_pixbuf = callPackage ../development/libraries/gdk-pixbuf {
# workaround signal 10 in gdk_pixbuf tests
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
};
* GTK+ 2.20, Glib 2.24 etc. svn path=/nixpkgs/branches/x-updates/; revision=22652
2010-07-19 01:22:59 +02:00
libXrender, libXvMC: Update
2013-06-14 14:53:36 +02:00
gtk2 = callPackage ../development/libraries/gtk+/2.x.nix {
non-Linux: more adjustments Also reordered stuff in all-packages.nix.
2013-06-18 23:42:25 +02:00
cupsSupport = config.gtk2.cups or stdenv.isLinux;
gtk2: fix compilation on darwin * add libintlOrEmpty to build inputs * allow cups to be disabled by setting config.gtk2.cups to false
2013-06-13 10:10:53 +02:00
};
libXrender, libXvMC: Update
2013-06-14 14:53:36 +02:00
Move at_spi2_core and at_spi2_atk outside of the gnome3 attrset
2014-07-08 18:00:00 +02:00
gtk3 = callPackage ../development/libraries/gtk+/3.x.nix { };
libXrender, libXvMC: Update
2013-06-14 14:53:36 +02:00
Move gtkLibs3x to top-level namespace, gtk+-3.2.3 Cherry-pick /nixpkgs/branches/glib-2.30@32044 svn path=/nixpkgs/trunk/; revision=32129
2012-02-07 22:03:16 +01:00
gtk = pkgs.gtk2;
* GTK+ 2.20, Glib 2.24 etc. svn path=/nixpkgs/branches/x-updates/; revision=22652
2010-07-19 01:22:59 +02:00
update gtk c++ bindings
2013-02-22 00:02:24 +01:00
gtkmm = callPackage ../development/libraries/gtkmm/2.x.nix { };
gtkmm3 = callPackage ../development/libraries/gtkmm/3.x.nix { };
Mentioning GTK-2.18 in all-packages svn path=/nixpkgs/trunk/; revision=17502
2009-09-29 15:49:41 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gtkmozembedsharp = callPackage ../development/libraries/gtkmozembed-sharp {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
gtksharp = gtksharp2;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gtksharp1 = callPackage ../development/libraries/gtk-sharp-1 {
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
inherit (gnome) libglade libgtkhtml gtkhtml
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
libgnomecanvas libgnomeui libgnomeprint
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
libgnomeprintui GConf;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gtksharp2 = callPackage ../development/libraries/gtk-sharp-2 {
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
inherit (gnome) libglade libgtkhtml gtkhtml
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
libgnomecanvas libgnomeui libgnomeprint
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
libgnomeprintui GConf gnomepanel;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gtksourceviewsharp = callPackage ../development/libraries/gtksourceview-sharp {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
inherit (gnome) gtksourceview;
gtksharp = gtksharp2;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
gtkspell = callPackage ../development/libraries/gtkspell { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Add gtkspell3
2014-01-09 14:21:36 +01:00
gtkspell3 = callPackage ../development/libraries/gtkspell/3.nix { };
Adding GNU Triangulated Surface library svn path=/nixpkgs/trunk/; revision=26132
2011-03-02 18:18:15 +01:00
gts = callPackage ../development/libraries/gts { };
gvfs: Fix build with lightWeight=false (close #2068) Needed for SMB backend.
2014-03-29 20:54:17 +01:00
gvfs = callPackage ../development/libraries/gvfs { gconf = gnome.GConf; };
gvfs: add globally, lightWeight by default HeavyWeight will be fixed after gnome3 from x-updates.
2013-04-01 18:09:51 +02:00
Add bunch of kmymoney-4.6.1 dependencies svn path=/nixpkgs/trunk/; revision=31436
2012-01-08 20:29:07 +01:00
gwenhywfar = callPackage ../development/libraries/gwenhywfar { };
Package hamlib library Signed-off-by: Ricky Elrod <ricky@elrod.me>
2014-05-11 22:37:43 +02:00
hamlib = callPackage ../development/libraries/hamlib { };
Some renaming for future variants svn path=/nixpkgs/trunk/; revision=10343
2008-01-28 20:44:39 +01:00
# TODO : Add MIT Kerberos and let admin choose.
kerberos = heimdal;
heimdal: remove obsolete 1.3.x version
2013-06-06 10:43:26 +02:00
heimdal = callPackage ../development/libraries/kerberos/heimdal.nix { };
Rename hupnp to herqq Don't pass it to kdelibs as it breaks kdelibs build svn path=/nixpkgs/trunk/; revision=25289
2010-12-26 18:18:13 +01:00
harfbuzz by default: don't use icu and do use graphite2 Also fix detection, so texLive builds now.
2013-11-24 13:51:12 +01:00
harfbuzz = callPackage ../development/libraries/harfbuzz { };
Add Harfbuzz, an OpenType text shaping engine
2012-09-27 23:23:36 +02:00
Adding two NES emulators. Because of them, I made allegro build the allegrogl library. I also added the HawkNL library. svn path=/nixpkgs/trunk/; revision=26517
2011-03-25 23:15:48 +01:00
hawknl = callPackage ../development/libraries/hawknl { };
Rename hupnp to herqq Don't pass it to kdelibs as it breaks kdelibs build svn path=/nixpkgs/trunk/; revision=25289
2010-12-26 18:18:13 +01:00
* Update a bunch of dependencies of kdelibs. svn path=/nixpkgs/branches/kde-4.7/; revision=27702
2011-07-11 12:49:21 +02:00
herqq = callPackage ../development/libraries/herqq { };
Rename hupnp to herqq Don't pass it to kdelibs as it breaks kdelibs build svn path=/nixpkgs/trunk/; revision=25289
2010-12-26 18:18:13 +01:00
hspell (another KDE dependency) svn path=/nixpkgs/trunk/; revision=24331
2010-10-17 20:44:00 +02:00
hspell = callPackage ../development/libraries/hspell { };
hspellDicts = callPackage ../development/libraries/hspell/dicts.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hsqldb = callPackage ../development/libraries/java/hsqldb { };
Added exiv2-0.15 library svn path=/nixpkgs/trunk/; revision=9389
2007-10-01 17:12:41 +02:00
http-parser: Bump Signed-off-by: Shea Levy <shea@shealevy.com>
2014-02-04 00:37:20 +01:00
http-parser = callPackage ../development/libraries/http-parser { inherit (pythonPackages) gyp; };
Add http_parser library Signed-off-by: Shea Levy <shea@shealevy.com>
2013-05-23 22:58:23 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hunspell = callPackage ../development/libraries/hunspell { };
Add hunspell TODO: make it work (export DICTDIR) svn path=/nixpkgs/trunk/; revision=22432
2010-06-30 17:53:28 +02:00
hwloc 1.3. svn path=/nixpkgs/trunk/; revision=30771
2011-12-06 15:04:01 +01:00
hwloc = callPackage ../development/libraries/hwloc {
inherit (xlibs) libX11;
};
Add hwloc 0.9.2, renamed from libtopology. svn path=/nixpkgs/trunk/; revision=18152
2009-11-05 19:46:46 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hydraAntLogger = callPackage ../development/libraries/java/hydra-ant-logger { };
hydra-ant-logger svn path=/nixpkgs/trunk/; revision=20332
2010-03-02 16:37:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
icu = callPackage ../development/libraries/icu { };
Added Apache Ant, including configuration of JAVA_HOME and ANT_HOME. Currently only the shell script is patched, but this one is used most in practice. svn path=/nixpkgs/trunk/; revision=718
2004-01-25 01:50:00 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
id3lib = callPackage ../development/libraries/id3lib { };
Added facile library svn path=/nixpkgs/trunk/; revision=9674
2007-11-15 00:05:11 +01:00
iksemel: Add new package with version 1.4. This library is used by Zabbix in order to send XMPP alerts/notifications. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-06-21 11:33:08 +02:00
iksemel = callPackage ../development/libraries/iksemel { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ilbc = callPackage ../development/libraries/ilbc { };
ilbc and msilbc libraries added svn path=/nixpkgs/branches/stdenv-updates/; revision=10570
2008-02-10 18:35:03 +01:00
ilixi: new package ilixi is a lightweight C++ GUI toolkit for embedded Linux systems. http://ilixi.org/
2014-02-01 16:00:40 +01:00
ilixi = callPackage ../development/libraries/ilixi { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ilmbase = callPackage ../development/libraries/ilmbase { };
enable beecrypt here svn path=/nixpkgs/trunk/; revision=4402
2005-12-19 19:56:31 +01:00
Pass libpng12 to imlib svn path=/nixpkgs/branches/libpng15/; revision=31892
2012-01-27 21:06:42 +01:00
imlib = callPackage ../development/libraries/imlib {
libpng = libpng12;
};
sox, ffmpeg_svn expressions added ghcPkgUtil defines a function to create setup-hook - creating a packagedatabase (nix-support/package.conf) - adding it to GHC_PACKAGE_PATH see comments for details svn path=/nixpkgs/trunk/; revision=9500
2007-10-22 02:51:40 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
imlib2 = callPackage ../development/libraries/imlib2 { };
Added a new setup proposal, builder is no more derived from shell script (where edit=glibc rebuild), but is composed from a nix attribute set with strings and dependencies - so if you add a function, old expressions ignore it; collateral damage are packages in this style: Fastest Fourier Transform in the West, Audacity sound editor, Falling Sand game. Also added string equality that ignores dependencies to lib. Note that hasSuffixHack is now the more predictable version, but hasSuffix is left to remind us to fix the bug. svn path=/nixpkgs/trunk/; revision=9549
2007-10-29 11:52:04 +01:00
incrTcl: packaged svn path=/nixpkgs/trunk/; revision=24279
2010-10-14 13:54:13 +02:00
incrtcl = callPackage ../development/libraries/incrtcl { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
indilib = callPackage ../development/libraries/indilib { };
indilib added svn path=/nixpkgs/trunk/; revision=10352
2008-01-28 20:47:23 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iniparser = callPackage ../development/libraries/iniparser { };
iniparser library added svn path=/nixpkgs/trunk/; revision=10344
2008-01-28 20:45:19 +01:00
unify intltool IMHO: - It's no longer GNOME package. - It seems best for everyone to use the newest version.
2013-01-31 16:43:52 +01:00
intltool = callPackage ../development/tools/misc/intltool { };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
Updating super tux kart to 0.7.3. I also add the library irrlicht, the specific version needed for super tux kart. svn path=/nixpkgs/trunk/; revision=32399
2012-02-19 14:15:50 +01:00
irrlicht3843 = callPackage ../development/libraries/irrlicht { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
isocodes = callPackage ../development/libraries/iso-codes { };
all-packages.nix: commented out package 'vice' error: getting status of `/usr/local/src/nix-pkgs-current/pkgs/misc/emulators/vice': No such file or directory svn path=/nixpkgs/trunk/; revision=15646
2009-05-18 15:53:01 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
itk = callPackage ../development/libraries/itk { };
Adding the itk libraries. Adding a skeleton of the seg3d package. It builds, but libraries and rpaths are wrong. I hope to fix it soon. svn path=/nixpkgs/trunk/; revision=20320
2010-03-02 00:31:35 +01:00
Adding JAMP game.. svn path=/nixpkgs/trunk/; revision=18454
2009-11-19 13:10:23 +01:00
jamp = builderDefsPackage ../games/jamp {
inherit mesa SDL SDL_image SDL_mixer;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jasper = callPackage ../development/libraries/jasper { };
pkgs/tools/typesetting/asciidoc: updated to version 8.5.1 New asciidoc versions do have a proper configure script. Using that simplifies the build instructions a bit. svn path=/nixpkgs/trunk/; revision=18076
2009-11-03 16:57:22 +01:00
JaMa library: packaged svn path=/nixpkgs/trunk/; revision=24277
2010-10-14 13:53:59 +02:00
jama = callPackage ../development/libraries/jama { };
Add Jansson C JSON lib
2013-05-11 23:34:07 +02:00
jansson = callPackage ../development/libraries/jansson { };
Adding 'mupdf', a lightweight PDF 1.7 viewer As a side effect, I add openjpeg and jbig2dec. svn path=/nixpkgs/trunk/; revision=23069
2010-08-09 22:59:38 +02:00
jbig2dec = callPackage ../development/libraries/jbig2dec { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jetty_gwt = callPackage ../development/libraries/java/jetty-gwt { };
pkgs/tools/typesetting/asciidoc: updated to version 8.5.1 New asciidoc versions do have a proper configure script. Using that simplifies the build instructions a bit. svn path=/nixpkgs/trunk/; revision=18076
2009-11-03 16:57:22 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jetty_util = callPackage ../development/libraries/java/jetty-util { };
Added JasPer JPEG 2000 library svn path=/nixpkgs/trunk/; revision=10335
2008-01-28 20:41:03 +01:00
Add json-glib svn path=/nixpkgs/trunk/; revision=23961
2010-09-27 13:18:28 +02:00
json_glib = callPackage ../development/libraries/json-glib { };
json-c: update to 0.12, fixing CVE-2013-{6370,6371}
2014-05-03 17:17:34 +02:00
json-c-0-11 = callPackage ../development/libraries/json-c/0.11.nix { }; # vulnerable
json_c = callPackage ../development/libraries/json-c { };
update pulseaudio 0.9.23 -> 1.1 svn path=/nixpkgs/trunk/; revision=30279
2011-11-06 21:03:07 +01:00
Add JsonCpp v0.6.0 Close #1112.
2013-10-22 17:42:06 +02:00
jsoncpp = callPackage ../development/libraries/jsoncpp { };
add libjson library svn path=/nixpkgs/trunk/; revision=30168
2011-11-01 18:07:14 +01:00
libjson = callPackage ../development/libraries/libjson { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
judy = callPackage ../development/libraries/judy { };
Making gtkwave more featured, adding more buildInputs. svn path=/nixpkgs/trunk/; revision=22133
2010-06-03 17:37:02 +02:00
keybinder: new package keybinder is a library for registering global keyboard shortcuts. keybinder works with GTK-based applications using the X Window System. https://github.com/engla/keybinder/
2014-02-17 20:37:55 +01:00
keybinder = callPackage ../development/libraries/keybinder {
automake = automake111x;
lua = lua5_1;
};
keybinder-3.0: Add package keybinder-3.0 is for GTK+ 3, whereas keybinder (already in nixpkgs) is for GTK+ 2. This adds version 0.3.0 of keybinder-3.0, which we named "keybinder3" in nixpkgs to (hopefully) lessen the confusion about what is package name and what is version number. [Bjørn: extend commit message beyond summary line]
2014-04-26 00:09:13 +02:00
keybinder3 = callPackage ../development/libraries/keybinder3 {
automake = automake111x;
lua = lua5_1;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
krb5 = callPackage ../development/libraries/kerberos/krb5.nix { };
Add MIT Kerberos implementation krb5. svn path=/nixpkgs/trunk/; revision=18202
2009-11-06 13:57:29 +01:00
Add lcms2 svn path=/nixpkgs/trunk/; revision=23012
2010-08-06 22:23:56 +02:00
lcms = lcms1;
lcms1 = callPackage ../development/libraries/lcms { };
lcms2 = callPackage ../development/libraries/lcms2 { };
* Added GemRB, a reimplementation of the Infinity Engine. svn path=/nixpkgs/trunk/; revision=8695
2007-05-14 23:47:11 +02:00
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
lensfun = callPackage ../development/libraries/lensfun { };
Add lensfun library svn path=/nixpkgs/trunk/; revision=21560
2010-05-03 05:45:52 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lesstif = callPackage ../development/libraries/lesstif { };
* Added FreeGLUT. svn path=/nixpkgs/trunk/; revision=8592
2007-04-18 15:47:35 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lesstif93 = callPackage ../development/libraries/lesstif-0.93 { };
Added older version of lesstif for arb svn path=/nixpkgs/trunk/; revision=12974
2008-10-06 17:11:36 +02:00
add leveldb
2013-05-11 08:52:32 +02:00
leveldb = callPackage ../development/libraries/leveldb { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
levmar = callPackage ../development/libraries/levmar { };
Updating meshlab. Their build system has changed, and the source tree they distribute too, so the dependencies changed a bit. To get meshlab working, I update lib3ds and add levmar. svn path=/nixpkgs/trunk/; revision=19595
2010-01-21 15:39:53 +01:00
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
leptonica = callPackage ../development/libraries/leptonica {
libpng = libpng12;
};
Adding the leptonica library of image processing and analysis. svn path=/nixpkgs/trunk/; revision=26954
2011-04-24 20:16:51 +02:00
awesome-3-5: add expression and nixos module
2013-11-13 03:34:49 +01:00
lgi = callPackage ../development/libraries/lgi {
lua = lua5_1;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lib3ds = callPackage ../development/libraries/lib3ds { };
added freestyle (non photorealistic renderer) and dependencies libQGLViewer, lib3ds svn path=/nixpkgs/trunk/; revision=12009
2008-06-08 05:56:32 +02:00
new library: libaacs for decoding bluray disks Does not contain any drm or copyright infringements. svn path=/nixpkgs/trunk/; revision=32485
2012-02-22 21:29:25 +01:00
libaacs = callPackage ../development/libraries/libaacs { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libaal = callPackage ../development/libraries/libaal { };
* Reiser4 stuff. svn path=/nixpkgs/trunk/; revision=10498
2008-02-04 15:37:15 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
libao = callPackage ../development/libraries/libao {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
usePulseAudio = config.pulseaudio or true;
Add mpg321, libao and libid3tag; upgrade libmad. svn path=/nixpkgs/trunk/; revision=10626
2008-02-11 22:02:38 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libarchive = callPackage ../development/libraries/libarchive { };
libarchive added svn path=/nixpkgs/trunk/; revision=10349
2008-01-28 20:46:38 +01:00
Add libass svn path=/nixpkgs/trunk/; revision=25868
2011-02-09 22:10:42 +01:00
libass = callPackage ../development/libraries/libass { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libassuan1 = callPackage ../development/libraries/libassuan1 { };
libassuan added svn path=/nixpkgs/trunk/; revision=10341
2008-01-28 20:43:37 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libassuan = callPackage ../development/libraries/libassuan { };
libassuan added svn path=/nixpkgs/trunk/; revision=10341
2008-01-28 20:43:37 +01:00
libassuan: added extra package with current git version needed for upcoming gnupg 2.1 svn path=/nixpkgs/trunk/; revision=33681
2012-04-09 12:17:36 +02:00
libassuan2_1 = callPackage ../development/libraries/libassuan/git.nix { };
Adding libatomic_ops
2014-06-27 14:02:29 +02:00
libatomic_ops = callPackage ../development/libraries/libatomic_ops {};
libav: update 0.8.11 -> .12, 9.12 -> .13, introduce 10.1
2014-06-03 14:25:21 +02:00
libav = libav_10;
libav: major update and refactoring (close #839) Also leaving 0_8 branch, as it's compatible with older ffmpeg versions. I'm planning that all expressions will be able to switch easily between ffmpeg and libav (whatever default we choose, but I prefer libav). Edited (twice) according to notes on the reverted b003138.
2013-08-17 07:17:44 +02:00
libav_all = callPackage ../development/libraries/libav { };
libav: update 0.8.11 -> .12, 9.12 -> .13, introduce 10.1
2014-06-03 14:25:21 +02:00
inherit (libav_all) libav_0_8 libav_9 libav_10;
* Added libav, a fork of ffmpeg. svn path=/nixpkgs/trunk/; revision=27797
2011-07-15 14:20:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libavc1394 = callPackage ../development/libraries/libavc1394 { };
kino (compiling but neither finding libX11 nor libghtread) and libiec61883 (dependency) added svn path=/nixpkgs/trunk/; revision=10133
2008-01-13 16:21:21 +01:00
Add bluedevil svn path=/nixpkgs/trunk/; revision=26333
2011-03-16 00:09:07 +01:00
libbluedevil = callPackage ../development/libraries/libbluedevil { };
new library: libbluray for playing bluray disks optionally use libaacs to decrypt commercial disks svn path=/nixpkgs/trunk/; revision=32486
2012-02-22 21:29:29 +01:00
libbluray = callPackage ../development/libraries/libbluray { };
mplayer(2): Add support and library for bs2b. This also adds a new package "libbs2b", which is needed in order to support Bauer stereophonic-to-binaural DSP as an audio filter. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-05-17 01:18:48 +02:00
libbs2b = callPackage ../development/libraries/audio/libbs2b { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libcaca = callPackage ../development/libraries/libcaca { };
added cil-aterm to nixpkgs svn path=/nixpkgs/trunk/; revision=4482
2006-01-02 15:24:36 +01:00
Make nixpkgs ready for gst_all attrset removal svn path=/nixpkgs/trunk/; revision=33092
2012-03-14 23:44:52 +01:00
libcanberra = callPackage ../development/libraries/libcanberra { };
pavucontrol 2.0
2013-07-27 17:43:17 +02:00
libcanberra_gtk3 = libcanberra.override { gtk = gtk3; };
kde4: unify used libcanberra I wondered why I'm getting two versions in the closure of KDE apps.
2013-07-05 14:22:01 +02:00
libcanberra_kde = if (config.kde_runtime.libcanberraWithoutGTK or true)
then libcanberra.override { gtk = null; }
else libcanberra;
Add `libcanberra'. svn path=/nixpkgs/trunk/; revision=13814
2009-01-20 10:50:15 +01:00
added libcello
2013-05-09 04:09:16 +02:00
libcello = callPackage ../development/libraries/libcello {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libcdaudio = callPackage ../development/libraries/libcdaudio { };
* Converting packages. This is the minimal Nix stdenv for building the ATerm library. svn path=/nixpkgs/trunk/; revision=459
2003-11-02 18:42:19 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libcddb = callPackage ../development/libraries/libcddb { };
Add libcddb and GNU libcdio. svn path=/nixpkgs/trunk/; revision=10960
2008-03-05 10:10:23 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libcdio = callPackage ../development/libraries/libcdio { };
fix libcdio filename
2014-02-02 21:39:17 +01:00
libcdio082 = callPackage ../development/libraries/libcdio/0.82.nix { };
Add libcddb and GNU libcdio. svn path=/nixpkgs/trunk/; revision=10960
2008-03-05 10:10:23 +01:00
keep lcms versioning in all-packages.nix
2013-06-29 16:07:15 +02:00
libcdr = callPackage ../development/libraries/libcdr { lcms = lcms2; };
Add libcdr (libreoffice dependency)
2012-08-29 22:30:15 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
libchamplain = callPackage ../development/libraries/libchamplain {
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
inherit (gnome) libsoup;
Add libchamplain, a library to display maps. svn path=/nixpkgs/trunk/; revision=22649
2010-07-19 00:46:19 +02:00
};
Restore libchamplain svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33291
2012-03-20 12:16:06 +01:00
libchamplain_0_6 = callPackage ../development/libraries/libchamplain/0.6.nix {};
libchop: builds with gnutls32 now
2014-03-21 07:23:43 +01:00
libchop = callPackage ../development/libraries/libchop { };
Adding libchop. I want to try it. Why didn't ludo add this, I don't know. :) svn path=/nixpkgs/trunk/; revision=30411
2011-11-13 15:33:31 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libcm = callPackage ../development/libraries/libcm { };
geos library added svn path=/nixpkgs/trunk/; revision=9837
2007-12-03 17:01:51 +01:00
libcroco: move to gnome-3, minor update
2013-02-04 23:26:28 +01:00
inherit (gnome3) libcroco;
Move libcroco and librsvg to top-level svn path=/nixpkgs/trunk/; revision=32933
2012-03-08 23:57:05 +01:00
Add libcangjie
2014-01-30 15:38:34 +01:00
libcangjie = callPackage ../development/libraries/libcangjie { };
libcredis: new package libcredis is a client library for Redis (key-value database). (libcredis is an optional dependency of collectd.) Homepage: https://code.google.com/p/credis/
2014-07-14 21:21:02 +02:00
libcredis = callPackage ../development/libraries/libcredis { };
libctemplate: packaged. Patch by Karn Kallio. svn path=/nixpkgs/trunk/; revision=23981
2010-09-28 11:33:42 +02:00
libctemplate = callPackage ../development/libraries/libctemplate { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libcue = callPackage ../development/libraries/libcue { };
libcue: New nixpkg. svn path=/nixpkgs/trunk/; revision=21147
2010-04-18 21:12:07 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libdaemon = callPackage ../development/libraries/libdaemon { };
Added support for overridable variants of package. For details read comments near getVersion function, gettext is the current example. svn path=/nixpkgs/trunk/; revision=9235
2007-09-01 20:26:13 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libdbi = callPackage ../development/libraries/libdbi { };
add Google's coredumper helper library (snapshots/coredumps for running programs) svn path=/nixpkgs/trunk/; revision=5485
2006-06-21 23:05:39 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
libdbiDriversBase = callPackage ../development/libraries/libdbi-drivers {
* ltrace: updated to 0.5.3. * libdbi / libdbi-drivers: updated to 0.8.3, and make it compile with SQLite. * qemu-image: fix the URL. * gdmap: make it build again (requires an older GTK+). * rlwrap: updated to 0.37. * smbfs-fuse -> fusesmb to match the upstream name. * x11vnc: updated to 0.9.10. * clearlyU: fix the URL. * Various packages: follow the coding conventions. svn path=/nixpkgs/trunk/; revision=22814
2010-07-29 20:55:16 +02:00
mysql = null;
sqlite = null;
* Removed selectVersion. There's no good reason to write `selectVersion ./foo "bar"' instead of `import ./foo/bar.nix'. * Replaced `with args' with formal function arguments in several packages. * Renamed several files to `default.nix'. As a general rule, version numbers should only be included in the filename when there is a reason to keep multiple versions of a package in Nixpkgs. Otherwise, it just makes it harder to update the package. svn path=/nixpkgs/trunk/; revision=18403
2009-11-18 10:39:59 +01:00
};
gdal library added svn path=/nixpkgs/trunk/; revision=9246
2007-09-04 11:38:52 +02:00
* composedArgsAndFun -> makeOverridable for consistency. * Rename a few single-version packages to "default.nix". svn path=/nixpkgs/trunk/; revision=22803
2010-07-29 10:21:21 +02:00
libdbiDrivers = libdbiDriversBase.override {
MySQL5 should be default already. svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10846
2008-02-25 04:16:07 +01:00
inherit sqlite mysql;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
* Stdenv for Linux, i.e., with a Nix-built glibc. svn path=/nixpkgs/trunk/; revision=461
2003-11-02 23:25:26 +01:00
Add libdmtx, restore alphabetical order svn path=/nixpkgs/trunk/; revision=27382
2011-06-07 23:50:23 +02:00
libdbusmenu_qt = callPackage ../development/libraries/libdbusmenu-qt { };
Adding libdc1394 svn path=/nixpkgs/trunk/; revision=33975
2012-05-03 09:38:58 +02:00
libdc1394 = callPackage ../development/libraries/libdc1394 { };
Adding the Allied Technologies libdc1394 variant and the cc1394 viewer. svn path=/nixpkgs/trunk/; revision=34013
2012-05-08 11:50:58 +02:00
libdc1394avt = callPackage ../development/libraries/libdc1394avt { };
Spring RTS: packaged along with its deps and utils: libDevIL, libtorrent-rasterbar, spring-lobby. svn path=/nixpkgs/trunk/; revision=24681
2010-11-13 08:47:04 +01:00
libdevil = callPackage ../development/libraries/libdevil { };
Add libdiscid svn path=/nixpkgs/trunk/; revision=23792
2010-09-14 16:29:13 +02:00
libdiscid = callPackage ../development/libraries/libdiscid { };
Adding libdivsufsort. Required for zpaq; I want to package it.
2012-07-05 11:07:26 +02:00
libdivsufsort = callPackage ../development/libraries/libdivsufsort { };
Add libdmtx, restore alphabetical order svn path=/nixpkgs/trunk/; revision=27382
2011-06-07 23:50:23 +02:00
libdmtx = callPackage ../development/libraries/libdmtx { };
Added glibc-ntpl to all-packages.nix . I also do not know if it works. svn path=/nixpkgs/trunk/; revision=9158
2007-08-18 18:20:14 +02:00
Adding hyenae - patch by MarcWeber svn path=/nixpkgs/trunk/; revision=29470
2011-09-24 11:14:21 +02:00
libdnet = callPackage ../development/libraries/libdnet { };
Get libdrm to compile on darwin The added patch uses mach_absolute_time() to get a nanosecond-resolution monotonic clock on darwin systems (See http://developer.apple.com/library/mac/#qa/qa1398/_index.html for an understanding of the added code). In addition, the patch changes one use of clock_gettime to gettimeofday since only resolution of a second is needed at that point. This code compiles on darwin, but the resulting library is not yet tested. svn path=/nixpkgs/trunk/; revision=28879
2011-08-29 20:55:37 +02:00
libdrm = callPackage ../development/libraries/libdrm {
* X.org 7.5. svn path=/nixpkgs/branches/xorg-7.5/; revision=18034
2009-10-29 18:56:10 +01:00
inherit fetchurl stdenv pkgconfig;
inherit (xorg) libpthreadstubs;
Get libdrm to compile on darwin The added patch uses mach_absolute_time() to get a nanosecond-resolution monotonic clock on darwin systems (See http://developer.apple.com/library/mac/#qa/qa1398/_index.html for an understanding of the added code). In addition, the patch changes one use of clock_gettime to gettimeofday since only resolution of a second is needed at that point. This code compiles on darwin, but the resulting library is not yet tested. svn path=/nixpkgs/trunk/; revision=28879
2011-08-29 20:55:37 +02:00
};
* Stdenv for Linux, i.e., with a Nix-built glibc. svn path=/nixpkgs/trunk/; revision=461
2003-11-02 23:25:26 +01:00
Add libdmtx, restore alphabetical order svn path=/nixpkgs/trunk/; revision=27382
2011-06-07 23:50:23 +02:00
libdv = callPackage ../development/libraries/libdv { };
added libdvbpsi and added it to the dependency list of vlc so that vlc can play DVB svn path=/nixpkgs/trunk/; revision=30789
2011-12-07 00:09:19 +01:00
libdvbpsi = callPackage ../development/libraries/libdvbpsi { };
Add libdmtx, restore alphabetical order svn path=/nixpkgs/trunk/; revision=27382
2011-06-07 23:50:23 +02:00
libdwg = callPackage ../development/libraries/libdwg { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libdvdcss = callPackage ../development/libraries/libdvdcss { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libdvdnav = callPackage ../development/libraries/libdvdnav { };
* Added wxHaskell. * Added GNU MP, use it in pycrypto. svn path=/nixpkgs/trunk/; revision=7343
2006-12-13 23:29:40 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libdvdread = callPackage ../development/libraries/libdvdread { };
Added Falling Sand Game and wxGTK without unicode for it. svn path=/nixpkgs/trunk/; revision=9543
2007-10-27 19:55:13 +02:00
Added libdwarf, libevent 1.4, libmcrypt, libmemcached, oniguruma. These are dependencies for HipHop Virtual Machine.
2012-12-01 21:28:32 +01:00
libdwarf = callPackage ../development/libraries/libdwarf { };
Adding libeatmydata. It doesn't run very well with our symlinks in PATH, but I don't know what patch can make it work still. This is better than nothing; calling it with its full path makes it work.
2013-02-10 00:08:29 +01:00
libeatmydata = callPackage ../development/libraries/libeatmydata { };
libebml: 1.0.0 svn path=/nixpkgs/trunk/; revision=25923
2011-02-12 21:18:41 +01:00
libebml = callPackage ../development/libraries/libebml { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libedit = callPackage ../development/libraries/libedit { };
* editline: renamed to libedit (which seems to be the proper name for the package). * Removed the old ghc-wrapper, which hasn't been used for a long time. * Renamed the "boot" GHC to "binary", which is more descriptive. (They *can* be used for other things than bootstrapping a GHC source build.) * Updated the GHC 6.10.1 binary to 6.10.2. svn path=/nixpkgs/trunk/; revision=15095
2009-04-16 21:25:22 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libelf = callPackage ../development/libraries/libelf { };
Add libelf. svn path=/nixpkgs/trunk/; revision=21400
2010-04-28 14:36:58 +02:00
Add pcmanfm-1.2.0
2014-03-01 19:37:39 +01:00
libfm = callPackage ../development/libraries/libfm { };
Add libdmtx, restore alphabetical order svn path=/nixpkgs/trunk/; revision=27382
2011-06-07 23:50:23 +02:00
libgadu = callPackage ../development/libraries/libgadu { };
add gnome3.libgdata and liboauth
2014-01-20 16:38:39 +01:00
libgdata = gnome3.libgdata;
Add libdmtx, restore alphabetical order svn path=/nixpkgs/trunk/; revision=27382
2011-06-07 23:50:23 +02:00
Adding LinuxSampler and dependencies, using SVN version for SFZ support svn path=/nixpkgs/trunk/; revision=33865
2012-04-20 22:39:42 +02:00
libgig = callPackage ../development/libraries/libgig { };
Move libgnome-keyring to development/libraries svn path=/nixpkgs/trunk/; revision=32887
2012-03-08 14:06:44 +01:00
libgnome_keyring = callPackage ../development/libraries/libgnome-keyring { };
gnome3: port and update (lib)gnome-keyring
2013-02-21 20:36:20 +01:00
libgnome_keyring3 = gnome3.libgnome_keyring;
Move libgnome-keyring to development/libraries svn path=/nixpkgs/trunk/; revision=32887
2012-03-08 14:06:44 +01:00
libgnurl, a fork of libcurl used by GNUnet
2014-04-28 07:20:37 +02:00
libgnurl = callPackage ../development/libraries/libgnurl { };
libseccomp: version 2.1.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-09 02:37:47 +02:00
libseccomp = callPackage ../development/libraries/libseccomp { };
networkmanagerapplet: 0.9.8.0 -> 0.9.8.2 Upgraded because some icons weren't displaying. Also adds new dependency libsecret.
2013-06-21 19:59:20 +02:00
libsecret = callPackage ../development/libraries/libsecret { };
libserialport: new package libserialport is a cross-platform shared library for serial port access, written in C. It comes from the sigrok project, but has no dependency on sigrok code. Homepage: http://sigrok.org/
2014-05-31 14:38:56 +02:00
libserialport = callPackage ../development/libraries/libserialport { };
Add libgtop svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33343
2012-03-22 08:32:08 +01:00
libgtop = callPackage ../development/libraries/libgtop {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
liblo = callPackage ../development/libraries/liblo { };
adding liblo svn path=/nixpkgs/trunk/; revision=17322
2009-09-21 11:58:27 +02:00
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
liblrdf = librdf;
Adding GTK-VNC svn path=/nixpkgs/trunk/; revision=25547
2011-01-13 23:21:09 +01:00
Adding qsampler, the frontend for LinuxSampler svn path=/nixpkgs/trunk/; revision=33867
2012-04-21 00:44:50 +02:00
liblscp = callPackage ../development/libraries/liblscp { };
Adding libe-book: a library for importing reflowable e-book formats
2014-06-27 14:06:41 +02:00
libe-book = callPackage ../development/libraries/libe-book {};
Minor cleanup
2012-11-29 14:40:25 +01:00
libev = builderDefsPackage ../development/libraries/libev { };
Adding libev - an even loop library remotely similar to libevent svn path=/nixpkgs/trunk/; revision=16877
2009-08-27 09:17:57 +02:00
Added libdwarf, libevent 1.4, libmcrypt, libmemcached, oniguruma. These are dependencies for HipHop Virtual Machine.
2012-12-01 21:28:32 +01:00
libevent14 = callPackage ../development/libraries/libevent/1.4.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libevent = callPackage ../development/libraries/libevent { };
Added sglr svn path=/nixpkgs/trunk/; revision=707
2004-01-22 20:09:49 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libewf = callPackage ../development/libraries/libewf { };
Adding libewf. svn path=/nixpkgs/trunk/; revision=15225
2009-04-21 21:47:41 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libexif = callPackage ../development/libraries/libexif { };
* Build ssmtp with TLS support. * Added gnutls (but it turns out that ssmtp also builds with openssl, so I don't actually use it). svn path=/nixpkgs/trunk/; revision=9604
2007-11-08 18:48:52 +01:00
Adding linphone svn path=/nixpkgs/trunk/; revision=25545
2011-01-13 21:49:58 +01:00
libexosip = callPackage ../development/libraries/exosip {};
Linphone 3.6.1 Lots of updates and new/old libs to get the latest linphone It segfaults on running.
2013-06-29 16:50:56 +02:00
libexosip_3 = callPackage ../development/libraries/exosip/3.x.nix {
libosip = libosip_3;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
libextractor = callPackage ../development/libraries/libextractor {
GNU libextractor 0.5.23. svn path=/nixpkgs/trunk/; revision=19216
2010-01-05 12:16:30 +01:00
libmpeg2 = mpeg2dec;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
Added jikespg, an oldskool parser generator svn path=/nixpkgs/trunk/; revision=5038
2006-03-14 19:20:21 +01:00
Add libexttextcat (part of LibreOffice)
2012-08-31 10:01:57 +02:00
libexttextcat = callPackage ../development/libraries/libexttextcat {};
Adding libf2c svn path=/nixpkgs/trunk/; revision=26144
2011-03-03 14:41:06 +01:00
libf2c = callPackage ../development/libraries/libf2c {};
Add libfixposix svn path=/nixpkgs/trunk/; revision=24462
2010-10-25 07:52:13 +02:00
libfixposix = callPackage ../development/libraries/libfixposix {};
Updating CLisp and adding SBCL. SBCL currently has to be symlinked to a writable directory (I am investigating a fix). CLisp 2.47 is somewhat incompatible with lots of software, so I added 2.44.1 as preserved version svn path=/nixpkgs/trunk/; revision=15806
2009-05-31 08:07:25 +02:00
libffcall = builderDefsPackage (import ../development/libraries/libffcall) {
inherit fetchcvs;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libffi = callPackage ../development/libraries/libffi { };
Add libffi, a foreign function interface library. svn path=/nixpkgs/trunk/; revision=11505
2008-04-09 09:40:48 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libftdi = callPackage ../development/libraries/libftdi { };
Made openocd work with ft2232 jtag chipset, that of the Sheevaplug. svn path=/nixpkgs/trunk/; revision=17407
2009-09-24 23:28:27 +02:00
libftdi1: new package This is the 1.x version of libftdi, as opposed to our existing libftdi 0.20 package. (AVRDUDE is an (optional) dependee of libftdi1.)
2014-05-31 13:10:41 +02:00
libftdi1 = callPackage ../development/libraries/libftdi/1.x.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libgcrypt = callPackage ../development/libraries/libgcrypt { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
add libgcrypt-1.6
2013-12-20 23:56:26 +01:00
libgcrypt_1_6 = lowPrio (callPackage ../development/libraries/libgcrypt/1.6.nix { });
* Fix building libgdiplus with libpng15. svn path=/nixpkgs/trunk/; revision=32826
2012-03-06 14:49:37 +01:00
libgdiplus = callPackage ../development/libraries/libgdiplus { };
Adding libgdiplus for mono, and making mono reference it. svn path=/nixpkgs/trunk/; revision=31276
2012-01-04 14:55:54 +01:00
New packages: libgksu, gksu
2014-08-05 23:28:12 +02:00
libgksu = callPackage ../development/libraries/libgksu { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libgpgerror = callPackage ../development/libraries/libgpg-error { };
* Converted some more packages. * Subversion no longer needs libxml2 (just expat). svn path=/nixpkgs/trunk/; revision=478
2003-11-05 13:17:48 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libgphoto2 = callPackage ../development/libraries/libgphoto2 { };
libcdaudio 0.99.12 svn path=/nixpkgs/trunk/; revision=2062
2005-01-19 22:12:46 +01:00
libgphoto2: adding a 2.4 version, for kde 4.7 and 4.8.
2013-05-29 19:29:18 +02:00
libgphoto2_4 = callPackage ../development/libraries/libgphoto2/2.4.nix { };
Add mutagen, upgrade libgpod svn path=/nixpkgs/trunk/; revision=23955
2010-09-26 21:40:22 +02:00
libgpod = callPackage ../development/libraries/libgpod {
inherit (pkgs.pythonPackages) mutagen;
};
Adding libgpod, for a future gtkpod. svn path=/nixpkgs/trunk/; revision=15015
2009-04-13 17:41:00 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libharu = callPackage ../development/libraries/libharu { };
adding haru pdf lib svn path=/nixpkgs/trunk/; revision=17076
2009-09-13 10:54:44 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libical = callPackage ../development/libraries/libical { };
Use $NIXPKGS_CONFIG to determine whether ghostscript has cups support. svn path=/nixpkgs/trunk/; revision=14275
2009-02-27 14:44:31 +01:00
Add libicns svn path=/nixpkgs/trunk/; revision=33481
2012-03-30 03:36:38 +02:00
libicns = callPackage ../development/libraries/libicns { };
Add libimobiledevice svn path=/nixpkgs/trunk/; revision=23953
2010-09-26 21:40:07 +02:00
libimobiledevice = callPackage ../development/libraries/libimobiledevice { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
libiodbc = callPackage ../development/libraries/libiodbc {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
useGTK = config.libiodbc.gtk or false;
* libiodbc: don't pass all of Nixpkgs to the package. There is no reason why this shouldn't work, but it breaks NixOS evaluation on x86_64-linux with weird segfaults and assertion failures, probably due to a bug in the evaluator or the ATerm library. svn path=/nixpkgs/trunk/; revision=20953
2010-04-06 12:50:52 +02:00
};
Add libiodbc Use experimental style. Will revert to "standard" one if needed. svn path=/nixpkgs/trunk/; revision=20929
2010-04-03 11:53:38 +02:00
New pkg: syslog-ng-incubator A collection of tools and modules for syslog-ng
2014-07-07 18:07:06 +02:00
libivykis = callPackage ../development/libraries/libivykis { };
Add two lastfm libraries svn path=/nixpkgs/trunk/; revision=23954
2010-09-26 21:40:15 +02:00
liblastfmSF = callPackage ../development/libraries/liblastfmSF { };
liblastfm = callPackage ../development/libraries/liblastfm { };
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
liblqr1 = callPackage ../development/libraries/liblqr-1 { };
Add liblqr-1 svn path=/nixpkgs/trunk/; revision=21559
2010-05-03 05:45:47 +02:00
add liblockfile-1.09
2012-08-25 11:13:20 +02:00
liblockfile = callPackage ../development/libraries/liblockfile { };
Upgrade rsyslog to latest (v7) stable release. Added liblogging (new dependency of rsyslog).
2014-07-07 16:23:54 +02:00
liblogging = callPackage ../development/libraries/liblogging { };
Added libdwarf, libevent 1.4, libmcrypt, libmemcached, oniguruma. These are dependencies for HipHop Virtual Machine.
2012-12-01 21:28:32 +01:00
libmcrypt = callPackage ../development/libraries/libmcrypt {};
Add libmhash, a cryptographic hash library. Add Nix expression to package libmhash, a library providing a collection of cryptographic hash algorithms. svn path=/nixpkgs/trunk/; revision=23379
2010-08-24 10:24:33 +02:00
libmhash = callPackage ../development/libraries/libmhash {};
libmodbus: new package libmodbus is a library to send/receive data according to the Modbus protocol. http://libmodbus.org/
2014-06-14 21:45:43 +02:00
libmodbus = callPackage ../development/libraries/libmodbus {};
Add libmtp svn path=/nixpkgs/trunk/; revision=23947
2010-09-26 21:39:28 +02:00
libmtp = callPackage ../development/libraries/libmtp { };
add libmsgpack C/C++ library (close #2059)
2014-03-29 13:28:25 +01:00
libmsgpack = callPackage ../development/libraries/libmsgpack { };
Add libnatspec svn path=/nixpkgs/trunk/; revision=31960
2012-02-01 23:32:12 +01:00
libnatspec = callPackage ../development/libraries/libnatspec { };
Add libnfc 1.7.1
2014-08-26 01:21:27 +02:00
libnfc = callPackage ../development/libraries/libnfc { };
Enabling nfsv4 and nfsv41 in nfsUtils (or at least I think so). svn path=/nixpkgs/trunk/; revision=33315
2012-03-21 00:17:45 +01:00
libnfsidmap = callPackage ../development/libraries/libnfsidmap { };
Make nixpkgs ready for gst_all attrset removal svn path=/nixpkgs/trunk/; revision=33092
2012-03-14 23:44:52 +01:00
libnice = callPackage ../development/libraries/libnice { };
add libnice svn path=/nixpkgs/trunk/; revision=19134
2009-12-27 15:22:00 +01:00
liboping: new package liboping is a C library to generate ICMP echo requests, better known as "ping packets". It is intended for use in network monitoring applications or applications that would otherwise need to fork ping(1) frequently. http://verplant.org/liboping/
2014-06-15 00:42:40 +02:00
liboping = callPackage ../development/libraries/liboping { };
Updating from trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=24038
2010-10-03 11:25:34 +02:00
libplist = callPackage ../development/libraries/libplist { };
Add libplist svn path=/nixpkgs/trunk/; revision=23946
2010-09-26 21:39:21 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libQGLViewer = callPackage ../development/libraries/libqglviewer { };
added freestyle (non photorealistic renderer) and dependencies libQGLViewer, lib3ds svn path=/nixpkgs/trunk/; revision=12009
2008-06-08 05:56:32 +02:00
Added BareSIP
2012-09-24 19:02:19 +02:00
libre = callPackage ../development/libraries/libre {};
librem = callPackage ../development/libraries/librem {};
libresample: Add package
2014-04-05 20:54:47 +02:00
libresample = callPackage ../development/libraries/libresample {};
Adding librevenge: a library for creating file importers
2014-06-27 14:04:47 +02:00
librevenge = callPackage ../development/libraries/librevenge {};
librevisa: new package It's an implementation of the VISA standard (for instrument control). http://www.librevisa.org/
2014-05-18 22:55:32 +02:00
librevisa = callPackage ../development/libraries/librevisa { };
libsamplerate: Use default gcc
2014-07-23 11:45:44 +02:00
libsamplerate = callPackage ../development/libraries/libsamplerate { };
added libvorbis libogg and flac svn path=/nixpkgs/trunk/; revision=2063
2005-01-19 22:48:45 +01:00
* libspectre seems to work with the default ghostscript. svn path=/nixpkgs/branches/kde-4.7/; revision=27724
2011-07-11 16:47:15 +02:00
libspectre = callPackage ../development/libraries/libspectre { };
Libspectre 0.2.0, a PostScript rendering library. svn path=/nixpkgs/trunk/; revision=12375
2008-07-17 21:43:11 +02:00
libgsf: update, streamline dependencies, drop obsolete patch Tried to build some affected packages, seems OK. Conflicts (buildNativeInputs): pkgs/development/libraries/libgsf/default.nix
2013-02-04 23:31:10 +01:00
libgsf = callPackage ../development/libraries/libgsf { };
added libvorbis libogg and flac svn path=/nixpkgs/trunk/; revision=2063
2005-01-19 22:48:45 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libiconv = callPackage ../development/libraries/libiconv { };
Add GNU libiconv as a stand-alone package. svn path=/nixpkgs/trunk/; revision=17282
2009-09-20 00:03:24 +02:00
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
libiconvOrEmpty = if libiconvOrNull == null then [] else [libiconv];
avahi: use libiconv if needed svn path=/nixpkgs/trunk/; revision=33624
2012-04-05 17:11:19 +02:00
libiconvOrNull: Fix libc check.
2012-08-21 16:58:55 +02:00
libiconvOrNull =
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
if gcc.libc or null != null || stdenv.isGlibc
libiconvOrNull: Fix libc check.
2012-08-21 16:58:55 +02:00
then null
else libiconv;
Introduce libiconvOrNull and libiconvOrGlibc One can use these attrs instead of custom 'if ... then libiconv else null'. This way we can maintain the correct 'if ... then' check in one place. NB: I don't know what is the correct condition, so I use stdenv.isLinux. Feel free to fix this. svn path=/nixpkgs/trunk/; revision=31906
2012-01-28 13:44:42 +01:00
The logic behind 'libiconvOrLibc' is flawed and that attribute should be removed. See https://github.com/NixOS/nixpkgs/pull/2532 for further details.
2014-05-07 22:13:26 +02:00
# The logic behind this attribute is broken: libiconvOrNull==null does
# NOT imply libiconv=glibc! On Darwin, for example, we have a native
# libiconv library which is not glibc.
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
libiconvOrLibc = if libiconvOrNull == null then gcc.libc else libiconv;
Introduce libiconvOrNull and libiconvOrGlibc One can use these attrs instead of custom 'if ... then libiconv else null'. This way we can maintain the correct 'if ... then' check in one place. NB: I don't know what is the correct condition, so I use stdenv.isLinux. Feel free to fix this. svn path=/nixpkgs/trunk/; revision=31906
2012-01-28 13:44:42 +01:00
some libintl and libiconv cleanups + non-linux fixes
2013-04-14 13:27:58 +02:00
# On non-GNU systems we need GNU Gettext for libintl.
libintlOrEmpty = stdenv.lib.optional (!stdenv.isLinux) gettext;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libid3tag = callPackage ../development/libraries/libid3tag { };
Add mpg321, libao and libid3tag; upgrade libmad. svn path=/nixpkgs/trunk/; revision=10626
2008-02-11 22:02:38 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libidn = callPackage ../development/libraries/libidn { };
enable usbutils and libusb svn path=/nixpkgs/trunk/; revision=4507
2006-01-07 18:25:39 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libiec61883 = callPackage ../development/libraries/libiec61883 { };
kino (compiling but neither finding libX11 nor libghtread) and libiec61883 (dependency) added svn path=/nixpkgs/trunk/; revision=10133
2008-01-13 16:21:21 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
libinfinity = callPackage ../development/libraries/libinfinity {
Packaged libinfinity svn path=/nixpkgs/trunk/; revision=22359
2010-06-21 18:06:18 +02:00
inherit (gnome) gtkdoc;
};
pkgs/top-level/all-packages.nix: stripped trailing whitespace svn path=/nixpkgs/trunk/; revision=22734
2010-07-26 15:41:09 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libiptcdata = callPackage ../development/libraries/libiptcdata { };
Adding libiptcdata. I'm attempting to build rawtherapee, but it wants the propietary library 'rawzor'. Maybe upstream someone will allow building without it some day. Until then, no rawtherapee. svn path=/nixpkgs/trunk/; revision=19497
2010-01-17 01:46:57 +01:00
Use libjpeg-turbo as the system-wide default. ToDo: open an issue for discussion (testing, easy to revert).
2013-02-05 10:32:34 +01:00
libjpeg_original = callPackage ../development/libraries/libjpeg { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libjpeg_turbo = callPackage ../development/libraries/libjpeg-turbo { };
vala, libusb1, deps of libjpeg: attempt to fix on non-Linux
2013-06-18 15:35:26 +02:00
libjpeg = if (stdenv.isLinux) then libjpeg_turbo else libjpeg_original; # some problems, both on FreeBSD and Darwin
Adding virtualgl (and therefore, libjpeg-turbo, a SIMD API-compatible libjpeg) svn path=/nixpkgs/trunk/; revision=22553
2010-07-10 10:45:44 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
libjpeg62 = callPackage ../development/libraries/libjpeg/62.nix {
re-added libjpeg62 for chrome, updated chrome svn path=/nixpkgs/trunk/; revision=19199
2010-01-04 08:47:32 +01:00
libtool = libtool_1_5;
};
Add libjson-rpc-cpp-0.2.1
2013-10-14 16:11:46 +02:00
libjson_rpc_cpp = callPackage ../development/libraries/libjson-rpc-cpp { };
Add libkate svn path=/nixpkgs/trunk/; revision=25869
2011-02-09 22:10:55 +01:00
libkate = callPackage ../development/libraries/libkate { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libksba = callPackage ../development/libraries/libksba { };
Added libksba svn path=/nixpkgs/trunk/; revision=10342
2008-01-28 20:44:20 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmad = callPackage ../development/libraries/libmad { };
- add a whole bunch of packages which were added today already (but also list them here) - enable OOo2 build svn path=/nixpkgs/trunk/; revision=4149
2005-10-26 23:10:31 +02:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
libmatchbox = callPackage ../development/libraries/libmatchbox { };
Adding the matchbox window manager svn path=/nixpkgs/trunk/; revision=23076
2010-08-10 00:40:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmatthew_java = callPackage ../development/libraries/java/libmatthew-java { };
Added dbus-java and libmatthew-java (dependency for dbus-java) packages svn path=/nixpkgs/trunk/; revision=19170
2010-01-02 14:28:51 +01:00
libmatroska: 1.0.0 svn path=/nixpkgs/trunk/; revision=25924
2011-02-12 21:18:46 +01:00
libmatroska = callPackage ../development/libraries/libmatroska { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmcs = callPackage ../development/libraries/libmcs { };
* Added Audacious, a fork of beep-media-player (which doesn't seem to work very well after the Glibc update), plus its dependencies. TODO: make an audacious-wrapper that lets Audacious find its plugins automatically. Currently you have to install audacious-plugins and symlink ~/.nix-profile/lib/audacious/* in ~/.local/share/audacious/Plugins. svn path=/nixpkgs/trunk/; revision=10927
2008-03-03 11:55:20 +01:00
Added libdwarf, libevent 1.4, libmcrypt, libmemcached, oniguruma. These are dependencies for HipHop Virtual Machine.
2012-12-01 21:28:32 +01:00
libmemcached = callPackage ../development/libraries/libmemcached { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmicrohttpd = callPackage ../development/libraries/libmicrohttpd { };
add libmicrohttpd svn path=/nixpkgs/trunk/; revision=11813
2008-05-11 13:46:48 +02:00
libmikmod: fix build on darwin * build with gccApple
2013-07-04 06:58:32 +02:00
libmikmod = callPackage ../development/libraries/libmikmod {
# resolve the "stray '@' in program" errors
stdenv = if stdenv.isDarwin
then overrideGCC stdenv gccApple
else stdenv;
};
libmikmod: New nixpkg. svn path=/nixpkgs/trunk/; revision=21146
2010-04-18 20:57:35 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmilter = callPackage ../development/libraries/libmilter { };
added libmilter, opendkim svn path=/nixpkgs/trunk/; revision=19875
2010-02-09 11:32:55 +01:00
libmkv: from Handbrake project Libmkv was started from Handbrake but is now unmaintained upstream. Patches: - A01: add constant to header file - A02: Breaks API: Allow changing output sampling frequency - P00: Fix accessing large files on Mingw32
2014-05-04 01:52:45 +02:00
libmkv = callPackage ../development/libraries/libmkv { };
Add libmms svn path=/nixpkgs/trunk/; revision=28590
2011-08-15 20:04:57 +02:00
libmms = callPackage ../development/libraries/libmms { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmowgli = callPackage ../development/libraries/libmowgli { };
* Added Audacious, a fork of beep-media-player (which doesn't seem to work very well after the Glibc update), plus its dependencies. TODO: make an audacious-wrapper that lets Audacious find its plugins automatically. Currently you have to install audacious-plugins and symlink ~/.nix-profile/lib/audacious/* in ~/.local/share/audacious/Plugins. svn path=/nixpkgs/trunk/; revision=10927
2008-03-03 11:55:20 +01:00
libmng: update 1.0.10 -> 2.0.2, drop autotools phase
2013-12-23 18:08:09 +01:00
libmng = callPackage ../development/libraries/libmng { };
adding libmng svn path=/nixpkgs/trunk/; revision=17075
2009-09-13 10:54:41 +02:00
add libmnl-1.0.3
2012-10-13 19:27:18 +02:00
libmnl = callPackage ../development/libraries/libmnl { };
Adding libmodplug svn path=/nixpkgs/trunk/; revision=29186
2011-09-11 18:45:42 +02:00
libmodplug = callPackage ../development/libraries/libmodplug {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmpcdec = callPackage ../development/libraries/libmpcdec { };
- add a whole bunch of packages which were added today already (but also list them here) - enable OOo2 build svn path=/nixpkgs/trunk/; revision=4149
2005-10-26 23:10:31 +02:00
Add mp3splt
2014-07-07 20:38:14 +02:00
libmp3splt = callPackage ../development/libraries/libmp3splt { };
Adding libmrss and libnxml (dependency of the former) svn path=/nixpkgs/trunk/; revision=25325
2010-12-30 22:23:19 +01:00
libmrss = callPackage ../development/libraries/libmrss { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmsn = callPackage ../development/libraries/libmsn { };
Use $NIXPKGS_CONFIG to determine whether ghostscript has cups support. svn path=/nixpkgs/trunk/; revision=14275
2009-02-27 14:44:31 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmspack = callPackage ../development/libraries/libmspack { };
* Converted more packages. svn path=/nixpkgs/trunk/; revision=488
2003-11-06 16:24:19 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libmusclecard = callPackage ../development/libraries/libmusclecard { };
Adding more muscle programs and libraries. svn path=/nixpkgs/trunk/; revision=19320
2010-01-09 19:06:37 +01:00
Add libmusicbrainz 2.x and 3.x svn path=/nixpkgs/trunk/; revision=23793
2010-09-14 16:29:19 +02:00
libmusicbrainz2 = callPackage ../development/libraries/libmusicbrainz/2.x.nix { };
libmusicbrainz3 = callPackage ../development/libraries/libmusicbrainz { };
libmusicbrainz5: new major version
2014-04-07 23:52:40 +02:00
libmusicbrainz5 = callPackage ../development/libraries/libmusicbrainz/5.x.nix { };
Add libmusicbrainz 2.x and 3.x svn path=/nixpkgs/trunk/; revision=23793
2010-09-14 16:29:19 +02:00
libmusicbrainz = libmusicbrainz3;
Adding libmwaw: a library to import some old Macintosh text document formats
2014-06-27 14:08:18 +02:00
libmwaw = callPackage ../development/libraries/libmwaw { };
libmx: Add package
2014-04-26 00:09:13 +02:00
libmx = callPackage ../development/libraries/libmx { };
Add ettercap, a comprehensive suite for man in the middle attacks
2013-10-03 15:35:34 +02:00
libnet = callPackage ../development/libraries/libnet { };
add libnetfilter_conntrack-1.0.2
2012-10-13 19:18:16 +02:00
libnetfilter_conntrack = callPackage ../development/libraries/libnetfilter_conntrack { };
libnetfilter_queue: add version 1.0.2
2013-09-09 12:52:31 +02:00
libnetfilter_queue = callPackage ../development/libraries/libnetfilter_queue { };
add libnfnetlink-1.0.1
2012-10-13 18:53:17 +02:00
libnfnetlink = callPackage ../development/libraries/libnfnetlink { };
libnftnl: Add derivation
2014-08-24 00:11:37 +02:00
libnftnl = callPackage ../development/libraries/libnftnl { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libnih = callPackage ../development/libraries/libnih { };
* Upstart updated to 0.6.5. * Added libnih (a dependency of Upstart). * Removed the old Upstart 0.3.x. svn path=/nixpkgs/trunk/; revision=20015
2010-02-15 16:55:39 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libnova = callPackage ../development/libraries/libnova { };
libnova added svn path=/nixpkgs/trunk/; revision=10351
2008-01-28 20:47:12 +01:00
Adding libmrss and libnxml (dependency of the former) svn path=/nixpkgs/trunk/; revision=25325
2010-12-30 22:23:19 +01:00
libnxml = callPackage ../development/libraries/libnxml { };
Adding libodfgen: a library for writing ODF
2014-06-27 14:09:13 +02:00
libodfgen = callPackage ../development/libraries/libodfgen { };
Add libofa svn path=/nixpkgs/trunk/; revision=23794
2010-09-14 16:29:25 +02:00
libofa = callPackage ../development/libraries/libofa { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libofx = callPackage ../development/libraries/libofx { };
Adding libofx and updating opensp (to get libofx built). (I may have broken openjade... I will check later). svn path=/nixpkgs/trunk/; revision=19697
2010-01-26 23:04:54 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libogg = callPackage ../development/libraries/libogg { };
* Use all those new packages. svn path=/nixpkgs/trunk/; revision=545
2003-11-25 19:02:05 +01:00
Add liboggz svn path=/nixpkgs/trunk/; revision=25867
2011-02-09 22:10:28 +01:00
liboggz = callPackage ../development/libraries/liboggz { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
liboil = callPackage ../development/libraries/liboil { };
- svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10823
2008-02-22 04:06:12 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
liboop = callPackage ../development/libraries/liboop { };
Add GNU lsh, a GPL'd implementation of SSH, and `liboop', and event loop library. svn path=/nixpkgs/trunk/; revision=10637
2008-02-12 11:51:44 +01:00
Adding libopus I still don't know any program that can use it.
2012-09-25 20:01:29 +02:00
libopus = callPackage ../development/libraries/libopus { };
libosinfo: new package libosinfo contains "info about OSs, hypervisors and (virtual) hardware devices". It is a dependency of gnome-boxes (a virtual and remote machine application).
2014-07-11 19:53:17 +02:00
libosinfo = callPackage ../development/libraries/libosinfo {};
Adding libosip - GNU SIP library svn path=/nixpkgs/trunk/; revision=23555
2010-08-31 11:58:09 +02:00
libosip = callPackage ../development/libraries/osip {};
Linphone 3.6.1 Lots of updates and new/old libs to get the latest linphone It segfaults on running.
2013-06-29 16:50:56 +02:00
libosip_3 = callPackage ../development/libraries/osip/3.nix {};
Updating irssi_otr and libotr to the latest master versions. According to their few additional commit logs, it's worth it. I also set libotr to use the latest libgcrypt, related to a comment in libotr commit. They talk about a libgcrypt fix that will have more chances to be in the latest libgcrypt.
2014-02-11 11:55:59 +01:00
libotr = callPackage ../development/libraries/libotr {
libgcrypt = libgcrypt_1_6;
};
Added aspell Added gtkspell Added pidgin, builds but does not run yet: running pidgin fails to find libX11.so.6. ldd on pidgin reports: libX11.so.6 => not found .... libX11.so.6 => /nix/store/brsva6rh1p2ymjvk7054a90is5panrhf-libX11-1.1.1/lib/libX11.so.6 (0xb7358000) which looks a bit weird ... Maybe some problem with patchelf? Or just a build problem and should the library path be set using an environment variable? svn path=/nixpkgs/trunk/; revision=8660
2007-05-13 16:22:24 +02:00
libotr: adding back libotr 3.2; bitlbee failed without it
2013-04-15 20:13:49 +02:00
libotr_3_2 = callPackage ../development/libraries/libotr/3.2.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libp11 = callPackage ../development/libraries/libp11 { };
Adding engine_pkcs11, a openssl engine for pkcs11 implementations for smartcards. svn path=/nixpkgs/trunk/; revision=19324
2010-01-09 23:22:41 +01:00
* Doh, forgot to commit. svn path=/nixpkgs/trunk/; revision=27059
2011-04-30 11:21:38 +02:00
libpar2 = callPackage ../development/libraries/libpar2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libpcap = callPackage ../development/libraries/libpcap { };
Added hsqldb to all-packages svn path=/nixpkgs/trunk/; revision=9265
2007-09-06 17:56:39 +02:00
libpipeline: Add package [Bjørn Forsman: modify meta.description so that it doesn't include the package name and doesn't end in a period.]
2014-02-04 23:33:54 +01:00
libpipeline = callPackage ../development/libraries/libpipeline { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libpng = callPackage ../development/libraries/libpng { };
libpng: merge apng expression (keep patch disabled by default) I made sure no rebuild will happen because of this. Unfortunately this meant merging attrsets instead of just using an optionalString for postPatch
2013-06-26 10:54:06 +02:00
libpng_apng = libpng.override { apngSupport = true; };
Restore libpng-1.2.x svn path=/nixpkgs/branches/libpng15/; revision=31440
2012-01-08 20:50:06 +01:00
libpng12 = callPackage ../development/libraries/libpng/12.nix { };
libpng: reintroduce 1.5, some pkgs need older
2013-02-16 18:00:28 +01:00
libpng15 = callPackage ../development/libraries/libpng/15.nix { };
Some upgrades needed for kde4: * alsa-lib: 1.0.12 -> 1.0.14 * alsa-utils: 1.0.13 -> 1.0.14 * strigi: 0.5.1 -> 0.5.3dev * libgpg-error: 1.0 -> 1.4 * gpgme: 1.0.3 -> 1.1.4 * cmake: 2.4.6 -> 2.4.7 * Some kde4 components added (not compilable yet). * icu4c-3.6 added * boost: added unicode support to RegEx, switched to "system" layout svn path=/nixpkgs/trunk/; revision=9068
2007-08-08 15:20:18 +02:00
add libpaper
2013-01-28 21:43:50 +01:00
libpaper = callPackage ../development/libraries/libpaper { };
Some upgrades needed for kde4: * alsa-lib: 1.0.12 -> 1.0.14 * alsa-utils: 1.0.13 -> 1.0.14 * strigi: 0.5.1 -> 0.5.3dev * libgpg-error: 1.0 -> 1.4 * gpgme: 1.0.3 -> 1.1.4 * cmake: 2.4.6 -> 2.4.7 * Some kde4 components added (not compilable yet). * icu4c-3.6 added * boost: added unicode support to RegEx, switched to "system" layout svn path=/nixpkgs/trunk/; revision=9068
2007-08-08 15:20:18 +02:00
libproxy: attempt to fix build on Darwin It seems it won't compile with too old compilers.
2014-03-12 07:10:38 +01:00
libproxy = callPackage ../development/libraries/libproxy {
stdenv = if stdenv.isDarwin
then overrideGCC stdenv gcc
else stdenv;
};
Temporarily disable gimpPlugins to remedy the following failure when calling nix-env: error: undefined variable `gtkLibs', in `nix-pkgs-current/pkgs/applications/graphics/gimp/plugins/default.nix' svn path=/nixpkgs/trunk/; revision=16041
2009-06-25 15:37:59 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libpseudo = callPackage ../development/libraries/libpseudo { };
Adding vwm, the console window manager. svn path=/nixpkgs/trunk/; revision=15255
2009-04-22 23:33:24 +02:00
libpwquality: factor out from gnome-control-center
2014-04-04 16:14:38 +02:00
libpwquality = callPackage ../development/libraries/libpwquality { };
all-packages.nix: drop trailing whitespace
2014-04-11 10:06:06 +02:00
Add libqalculate svn path=/nixpkgs/trunk/; revision=23180
2010-08-15 15:55:02 +02:00
libqalculate = callPackage ../development/libraries/libqalculate { };
librsvg: drop gtk2 dep. by default, add optional gtk3 dep. Tried to build some affected packages, seems OK.
2013-02-04 23:35:20 +01:00
librsvg = callPackage ../development/libraries/librsvg {
gtk2 = null; gtk3 = null; # neither gtk version by default
};
Move libcroco and librsvg to top-level svn path=/nixpkgs/trunk/; revision=32933
2012-03-08 23:57:05 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
librsync = callPackage ../development/libraries/librsync { };
Adding 'duplicity', and its dependency 'librsync' svn path=/nixpkgs/trunk/; revision=19813
2010-02-04 14:42:41 +01:00
Add packages for libzdb, libsearpc, ccnet, seafile-shared, and seafile-client
2014-02-04 20:02:46 +01:00
libsearpc = callPackage ../development/libraries/libsearpc { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libsigcxx = callPackage ../development/libraries/libsigcxx { };
* Converted some more packages. * Subversion no longer needs libxml2 (just expat). svn path=/nixpkgs/trunk/; revision=478
2003-11-05 13:17:48 +01:00
Adding the game Advanced Strategic Command. I had to add an old version of libsigc++ for it. svn path=/nixpkgs/trunk/; revision=23490
2010-08-29 11:43:46 +02:00
libsigcxx12 = callPackage ../development/libraries/libsigcxx/1.2.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libsigsegv = callPackage ../development/libraries/libsigsegv { };
* Added feh to set the root image. * Compiz extra plugins. svn path=/nixpkgs/trunk/; revision=8178
2007-03-05 14:44:27 +01:00
Restore libsigsegv-2.5 and fix clisp-2.44.1 build for bootstrapping needs svn path=/nixpkgs/trunk/; revision=16632
2009-08-10 07:20:14 +02:00
# To bootstrap SBCL, I need CLisp 2.44.1; it needs libsigsegv 2.5
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libsigsegv_25 = callPackage ../development/libraries/libsigsegv/2.5.nix { };
Restore libsigsegv-2.5 and fix clisp-2.44.1 build for bootstrapping needs svn path=/nixpkgs/trunk/; revision=16632
2009-08-10 07:20:14 +02:00
libsndfile: Fix build on Darwin Fixes #3347.
2014-07-23 11:00:41 +02:00
libsndfile = callPackage ../development/libraries/libsndfile { };
Adding 'awesome' (and two packages it was depending on) svn path=/nixpkgs/trunk/; revision=20385
2010-03-04 15:44:56 +01:00
Adding libsodium 0.4.3.
2013-10-11 20:37:47 +02:00
libsodium = callPackage ../development/libraries/libsodium { };
Move libsoup to development/libraries It is used in many packages outside of gnome2 set. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33197
2012-03-17 17:45:37 +01:00
libsoup = callPackage ../development/libraries/libsoup { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libssh = callPackage ../development/libraries/libssh { };
pkgs/applications/editors/emacs-modes/magit: updated to version magit-0.7-94-gbf42bf8 Magit has seen plenty of development since version 0.7, but for some reason there haven't been any new releases. This version bump updates the expression to build a current version of Magit directly from the Git repository. This change adds buildInputs 'autoconf' and 'automake'. These tools are required only because we aren't building from a proper release tarball. Once version 0.8 comes out, these dependencies can be dropped again. svn path=/nixpkgs/trunk/; revision=20650
2010-03-16 13:13:40 +01:00
Add libssh2 svn path=/nixpkgs/trunk/; revision=22975
2010-08-05 22:24:32 +02:00
libssh2 = callPackage ../development/libraries/libssh2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libstartup_notification = callPackage ../development/libraries/startup-notification { };
* Gnome 2.22.1. * Moved some of the Gnome package Nix expressions into pkgs/desktops/gnome/default.nix - no need to have them in separate files. This way the code is much shorter. Still to be done for all the other Gnome packages. * Glib 2.16.3. svn path=/nixpkgs/branches/stdenv-updates/; revision=11855
2008-05-20 16:25:09 +02:00
Updating qgis (1.8.0 & geos (3.3.8). I also add libspatialindex and libspatialite, to get the latest qgis building.
2013-07-18 11:40:23 +02:00
libspatialindex = callPackage ../development/libraries/libspatialindex { };
libspatialite = callPackage ../development/libraries/libspatialite { };
libtar: new package libtar is a C library for manipulating POSIX tar files. http://www.feep.net/libtar/
2014-08-17 22:56:52 +02:00
libtar = callPackage ../development/libraries/libtar { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libtasn1 = callPackage ../development/libraries/libtasn1 { };
Added Compiz Fusion (main plugins). Also some dependencies, and made wmii build under setup-new-2.sh also. svn path=/nixpkgs/trunk/; revision=9577
2007-11-05 09:32:20 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libtheora = callPackage ../development/libraries/libtheora { };
* add unison - unison uses a wrapper script to add font-schumacher-misc to the local X font path if the font isn't already present; this is necessary for it to work, but not terribly nice ... * lablgtk is a dependency of unison - handling of library dirs with ocaml is a hack so far; in principle, ocaml needs a general setup for library dirs like ghc svn path=/nixpkgs/trunk/; revision=9094
2007-08-10 10:21:31 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libtiff = callPackage ../development/libraries/libtiff { };
* Added convertlit, a tool for converting Microsoft Reader ebooks, plus its dependency libtommath. svn path=/nixpkgs/trunk/; revision=12606
2008-08-12 21:57:35 +02:00
Add libtiger svn path=/nixpkgs/trunk/; revision=25871
2011-02-09 22:11:16 +01:00
libtiger = callPackage ../development/libraries/libtiger { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libtommath = callPackage ../development/libraries/libtommath { };
t/gis/libgeotiff adding libgeotiff Signed-off-by: Marc Weber <marco-oweber@gmx.de> svn path=/nixpkgs/trunk/; revision=22113
2010-06-03 02:51:13 +02:00
deluge: fix build on darwin (close #930)
2013-09-07 00:09:34 +02:00
libtorrentRasterbar = callPackage ../development/libraries/libtorrent-rasterbar {
# fix "unrecognized option -arch" error
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
};
Spring RTS: packaged along with its deps and utils: libDevIL, libtorrent-rasterbar, spring-lobby. svn path=/nixpkgs/trunk/; revision=24681
2010-11-13 08:47:04 +01:00
Moving the attribute tox_core to libtoxcore. It seems more appropiate.
2013-10-11 21:44:15 +02:00
libtoxcore = callPackage ../development/libraries/libtoxcore { };
Add kmscon, a kms-based replacement for kernel VTs Note that currently this depends on the default nixpkgs mesa and pango. It may be possible to build more limited versions that don't e.g. depend on the full X stack without limiting kmscon (which of course doesn't use X). Depends on libtsm, added in the same commit. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-15 06:58:46 +01:00
libtsm = callPackage ../development/libraries/libtsm { };
Add libtunepimp svn path=/nixpkgs/trunk/; revision=23796
2010-09-14 16:29:37 +02:00
libtunepimp = callPackage ../development/libraries/libtunepimp { };
Add libtxc_dxtn-1.0.1. I thought this was needed by Steam, but it only applies when not using propietary drivers, and even then it doesn't look like well supported.
2012-12-13 10:57:52 +01:00
libtxc_dxtn = callPackage ../development/libraries/libtxc_dxtn { };
libtxc_dxtn_s2tc: add v1.0 (close #2194) S2TC is a patent-free S3TC compatible implementation and provides texture compression to mesa.
2014-04-09 22:32:11 +02:00
libtxc_dxtn_s2tc = callPackage ../development/libraries/libtxc_dxtn_s2tc { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libgeotiff = callPackage ../development/libraries/libgeotiff { };
Add GNU Libunistring, a Unicode string handling library. svn path=/nixpkgs/trunk/; revision=16071
2009-06-27 23:44:47 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libunistring = callPackage ../development/libraries/libunistring { };
Add libupnp, a UPnP implementation. svn path=/nixpkgs/trunk/; revision=12995
2008-10-07 23:18:01 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libupnp = callPackage ../development/libraries/pupnp { };
move libungif svn path=/nixpkgs/trunk/; revision=10026
2007-12-31 22:52:43 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
giflib = callPackage ../development/libraries/giflib { };
Passing giflib 4.1.x to OpenSceneGraph for now
2013-12-08 10:13:19 +01:00
giflib_4_1 = callPackage ../development/libraries/giflib/4.1.nix { };
* Converted more packages. svn path=/nixpkgs/trunk/; revision=488
2003-11-06 16:24:19 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libungif = callPackage ../development/libraries/giflib/libungif.nix { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
libunibreak: meta.platforms attribute
2013-11-09 17:46:54 +01:00
libunibreak = callPackage ../development/libraries/libunibreak { };
libunibreak: Add libunibreak-1.0 a unicode line breaking library
2013-09-28 09:00:17 +02:00
vlada/xfce Major Xfce refactoring, also adding versions 4.10.* Signed-off-by: Vladimír Čunát <vcunat@gmail.com>
2013-02-21 12:16:51 +01:00
libunique = callPackage ../development/libraries/libunique/default.nix { };
liburcu: new package liburcu is a userspace RCU (read-copy-update) library that is used by LTTng - Linux Trace Toolkit (next generation).
2013-07-04 21:19:25 +02:00
liburcu = callPackage ../development/libraries/liburcu { };
libusb1: build using clangStdenv
2014-08-11 06:25:06 +02:00
libusb = callPackage ../development/libraries/libusb {};
libunwind added svn path=/nixpkgs/trunk/; revision=10345
2008-01-28 20:45:30 +01:00
vala, libusb1, deps of libjpeg: attempt to fix on non-Linux
2013-06-18 15:35:26 +02:00
libusb1 = callPackage ../development/libraries/libusb1 {
libusb1: build using clangStdenv ... on darwin
2014-08-11 06:25:33 +02:00
stdenv = if stdenv.isDarwin
then clangStdenv
vala, libusb1, deps of libjpeg: attempt to fix on non-Linux
2013-06-18 15:35:26 +02:00
else stdenv;
};
Add libusb-1.x svn path=/nixpkgs/trunk/; revision=23945
2010-09-26 21:39:02 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libunwind = callPackage ../development/libraries/libunwind { };
Added libv4l which is now a required dependency for kdenetwork-4.4.1 svn path=/nixpkgs/trunk/; revision=20349
2010-03-03 11:37:38 +01:00
add libuv package This adds multiple versions of libuv: "a multi-platform support library with a focus on asynchronous I/O." The latest 0.10.* versions are considered stable (and thus I've only included 0.10.27), while the 0.11.* versions are unstable and often break API compatibility (and thus I've included multiple version thereof). Versions >= 0.11.1 && <= 0.11.5 do not create shared libraries, so I've excluded them. This should help clean up some of our other packages that depend on libuv (e.g. rust, nodejs) where we currently use whatever version is included in the package's archive.
2014-07-09 02:08:45 +02:00
libuvVersions = callPackage ../development/libraries/libuv { };
Added libv4l which is now a required dependency for kdenetwork-4.4.1 svn path=/nixpkgs/trunk/; revision=20349
2010-03-03 11:37:38 +01:00
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
libv4l = lowPrio (v4l_utils.override {
Updating libv4l (part of v4l-utils). I moved v4l-utils to stdenv.mkDerivation style, and it's used to build either libv4l or the utils (with qt4). svn path=/nixpkgs/trunk/; revision=34208
2012-05-22 16:30:12 +02:00
withQt4 = false;
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
});
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
Adding libva, to get some possible video acceleration in intel video cards. svn path=/nixpkgs/trunk/; revision=26854
2011-04-16 13:00:31 +02:00
libva = callPackage ../development/libraries/libva { };
libvdpau: update
2013-02-02 16:18:48 +01:00
libvdpau = callPackage ../development/libraries/libvdpau { };
* Added libvdpau and vdpauinfo. svn path=/nixpkgs/branches/stdenv-updates/; revision=25296
2010-12-27 19:30:52 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libvirt = callPackage ../development/libraries/libvirt { };
applying patches provided by griswold svn path=/nixpkgs/trunk/; revision=19707
2010-01-27 13:12:35 +01:00
virt-manager: update to 1.0.1, fix & update dependencies, gtk3 support - Vte, add gtk3 support, enable introspection, update to 0.35.90 - Spice-gtk, add gtk3 support - gtk-vnc, add gtk3 support - Add libvirt-glib (thanks @bjornfor) - Add usbredir - qemu, enable usbredir - spice-gtk, enable usbredir - virt-manager, update to 1.0.1 [Bjørn: * Set namePrefix = "" to preserve package name "virt-manager" (instead of "python2.7-virt-manager") * Add dconf to GIO_EXTRA_MODULES to get persistent settings in virt-manager. Without it: GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. * Add ${gtk3}/share to XDG_DATA_DIRS to unbreak "Take Screenshot" feature (fixes "Settings schema 'org.gtk.Settings.FileChooser' is not installed") * gtk-vnc: don't pull "pkgs" attrset for optionalString, use stdenv.lib.optionalString instead. ]
2014-03-23 18:12:07 +01:00
libvirt-glib = callPackage ../development/libraries/libvirt-glib { };
Add libvisio (libreoffice dependency)
2012-08-29 22:21:13 +02:00
libvisio = callPackage ../development/libraries/libvisio { };
add libvisual 0.4.0
2013-08-11 05:15:07 +02:00
libvisual = callPackage ../development/libraries/libvisual { };
Fix Linux detection in libvncserver to build linuxvnc
2013-10-20 15:34:42 +02:00
libvncserver = callPackage ../development/libraries/libvncserver {};
Some of preparation work for adding Xen. Troubles: 1. Xen Dom0 support not complete in mainline. 2. Xen's love to check for headers in /usr/include. To do afterwards: We need to change bootloading setup a bit. svn path=/nixpkgs/trunk/; revision=12941
2008-10-04 17:24:08 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libviper = callPackage ../development/libraries/libviper { };
Adding vwm, the console window manager. svn path=/nixpkgs/trunk/; revision=15255
2009-04-22 23:33:24 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libvpx = callPackage ../development/libraries/libvpx { };
Adding libvpx (the codec VP8). Still no package uses it. svn path=/nixpkgs/trunk/; revision=21958
2010-05-24 23:57:45 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libvterm = callPackage ../development/libraries/libvterm { };
Updating vwm and its libraries. svn path=/nixpkgs/trunk/; revision=18123
2009-11-04 23:38:26 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libvorbis = callPackage ../development/libraries/libvorbis { };
add fribidi and abiword commit 5666 + 1! svn path=/nixpkgs/trunk/; revision=5667
2006-07-08 14:44:39 +02:00
Adding libwebp svn path=/nixpkgs/trunk/; revision=32146
2012-02-08 22:37:20 +01:00
libwebp = callPackage ../development/libraries/libwebp { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libwmf = callPackage ../development/libraries/libwmf { };
* Converted more packages. svn path=/nixpkgs/trunk/; revision=488
2003-11-06 16:24:19 +01:00
libwnck3: fix build via disabling introspection It isn't used anywhere, but fixing it won't hurt (I found by accident).
2013-11-18 20:06:30 +01:00
libwnck = libwnck2;
libwnck2 = callPackage ../development/libraries/libwnck { };
Add libwnck3 svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33254
2012-03-19 05:36:51 +01:00
libwnck3 = callPackage ../development/libraries/libwnck/3.x.nix { };
Move libwnck to top-level svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33253
2012-03-19 05:36:47 +01:00
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
libwpd = callPackage ../development/libraries/libwpd { };
* Build metacity with compositing support. svn path=/nixpkgs/trunk/; revision=8114
2007-02-28 18:52:41 +01:00
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
libwpd_08 = callPackage ../development/libraries/libwpd/0.8.nix { };
Openoffice.org does not build with libwpd 0.9. svn path=/nixpkgs/trunk/; revision=31396
2012-01-07 14:19:06 +01:00
Add libwpg svn path=/nixpkgs/trunk/; revision=23898
2010-09-22 20:04:41 +02:00
libwpg = callPackage ../development/libraries/libwpg { };
Adding vbetool svn path=/nixpkgs/trunk/; revision=17952
2009-10-24 21:58:07 +02:00
libx86 = builderDefsPackage ../development/libraries/libx86 {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libxdg_basedir = callPackage ../development/libraries/libxdg-basedir { };
Adding 'awesome' (and two packages it was depending on) svn path=/nixpkgs/trunk/; revision=20385
2010-03-04 15:44:56 +01:00
Add libxkbcommon 0.2.0. This is needed as a dependency for the Weston compositor.
2012-12-02 12:21:02 +01:00
libxkbcommon = callPackage ../development/libraries/libxkbcommon { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libxklavier = callPackage ../development/libraries/libxklavier { };
libxklavier added svn path=/nixpkgs/branches/stdenv-updates/; revision=10749
2008-02-18 21:53:36 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libxmi = callPackage ../development/libraries/libxmi { };
Adding enblend-fuse, libxmi and hugin. Maybe hugin doesn't run well enough still. svn path=/nixpkgs/trunk/; revision=14894
2009-04-05 23:41:38 +02:00
Revert "separate libxml2 python bindings, added libconvOrLibC dependency" This reverts commit 614b18668433329cc5686c34b51a63e51c86c9f4. svn path=/nixpkgs/branches/stdenv-updates/; revision=32650
2012-02-28 01:07:12 +01:00
libxml2 = callPackage ../development/libraries/libxml2 {
pythonSupport = false;
};
Added gdmap, changed builder-defs to use derivation attribute on propagatedBuildInputs, manually fixed Xorg expression problem for Compiz, various fixes. svn path=/nixpkgs/trunk/; revision=9812
2007-12-01 17:20:23 +01:00
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
libxml2Python = lowPrio (libxml2.override {
Revert "separate libxml2 python bindings, added libconvOrLibC dependency" This reverts commit 614b18668433329cc5686c34b51a63e51c86c9f4. svn path=/nixpkgs/branches/stdenv-updates/; revision=32650
2012-02-28 01:07:12 +01:00
pythonSupport = true;
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
});
Added gdmap, changed builder-defs to use derivation attribute on propagatedBuildInputs, manually fixed Xorg expression problem for Compiz, various fixes. svn path=/nixpkgs/trunk/; revision=9812
2007-12-01 17:20:23 +01:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
libxmlxx = callPackage ../development/libraries/libxmlxx { };
Packaged libxml++ svn path=/nixpkgs/trunk/; revision=22417
2010-06-26 03:40:42 +02:00
add libxmp 4.2.7
2014-06-10 05:59:55 +02:00
libxmp = callPackage ../development/libraries/libxmp { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libxslt = callPackage ../development/libraries/libxslt { };
Added gdmap, changed builder-defs to use derivation attribute on propagatedBuildInputs, manually fixed Xorg expression problem for Compiz, various fixes. svn path=/nixpkgs/trunk/; revision=9812
2007-12-01 17:20:23 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
libixp_for_wmii = lowPrio (import ../development/libraries/libixp_for_wmii {
inherit fetchurl stdenv;
});
Added gdmap, changed builder-defs to use derivation attribute on propagatedBuildInputs, manually fixed Xorg expression problem for Compiz, various fixes. svn path=/nixpkgs/trunk/; revision=9812
2007-12-01 17:20:23 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libyaml = callPackage ../development/libraries/libyaml { };
Add libyaml and PyYAML. svn path=/nixpkgs/trunk/; revision=19477
2010-01-16 11:37:29 +01:00
libyaml-cpp: add versions 0.5.1 and 0.3.0 The two versions are actively maintained, and the API changed between them.
2013-07-02 22:42:47 +02:00
libyamlcpp = callPackage ../development/libraries/libyaml-cpp { };
libyamlcpp03 = callPackage ../development/libraries/libyaml-cpp/0.3.x.nix { };
Add libyubikey (aka yubico-c) package
2014-01-25 03:13:34 +01:00
libyubikey = callPackage ../development/libraries/libyubikey {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libzip = callPackage ../development/libraries/libzip { };
add zlibStatic svn path=/nixpkgs/trunk/; revision=5933
2006-07-25 10:44:05 +02:00
Add packages for libzdb, libsearpc, ccnet, seafile-shared, and seafile-client
2014-02-04 20:02:46 +01:00
libzdb = callPackage ../development/libraries/libzdb { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libzrtpcpp = callPackage ../development/libraries/libzrtpcpp { };
Twinkle needs an older version of ccrtp svn path=/nixpkgs/trunk/; revision=27333
2011-05-31 11:09:35 +02:00
libzrtpcpp_1_6 = callPackage ../development/libraries/libzrtpcpp/1.6.nix {
ccrtp = ccrtp_1_8;
};
adding twinkle, a voice over IP phone software svn path=/nixpkgs/trunk/; revision=17303
2009-09-20 19:01:19 +02:00
Add gnome3.gnome_settings_daemon
2014-01-19 23:14:11 +01:00
libwacom = callPackage ../development/libraries/libwacom { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lightning = callPackage ../development/libraries/lightning { };
Add GNU lightning, a run-time code generation library. svn path=/nixpkgs/trunk/; revision=12237
2008-07-01 16:47:49 +02:00
Add lirc svn path=/nixpkgs/trunk/; revision=31450
2012-01-09 11:25:49 +01:00
lirc = callPackage ../development/libraries/lirc { };
liquidfun: added google liquidfun (a box2d fork)
2014-07-24 10:12:47 +02:00
liquidfun = callPackage ../development/libraries/liquidfun { };
Adding liquidwar6 svn path=/nixpkgs/trunk/; revision=18996
2009-12-16 17:06:30 +01:00
liquidwar = builderDefsPackage ../games/liquidwar {
inherit (xlibs) xproto libX11 libXrender;
libpng15: use it by some packages to fix build
2013-02-16 18:07:37 +01:00
inherit gmp mesa libjpeg
Adding liquidwar6 svn path=/nixpkgs/trunk/; revision=18996
2009-12-16 17:06:30 +01:00
expat gettext perl
SDL SDL_image SDL_mixer SDL_ttf
curl sqlite
Update LiquidWar6 to 0.4
2014-08-03 13:59:13 +02:00
libogg libvorbis libcaca csound cunit
Adding liquidwar6 svn path=/nixpkgs/trunk/; revision=18996
2009-12-16 17:06:30 +01:00
;
libpng15: use it by some packages to fix build
2013-02-16 18:07:37 +01:00
guile = guile_1_8;
libpng = libpng15; # 0.0.13 needs libpng 1.2--1.5
Adding liquidwar6 svn path=/nixpkgs/trunk/; revision=18996
2009-12-16 17:06:30 +01:00
};
Adding avxsynth. To add it, I also add ffms and log4cpp.
2013-04-10 15:12:02 +02:00
log4cpp = callPackage ../development/libraries/log4cpp { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
log4cxx = callPackage ../development/libraries/log4cxx { };
* Converted more packages. svn path=/nixpkgs/trunk/; revision=488
2003-11-06 16:24:19 +01:00
log4cplus: added version 1.0.4 svn path=/nixpkgs/trunk/; revision=30777
2011-12-06 16:05:57 +01:00
log4cplus = callPackage ../development/libraries/log4cplus { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
loudmouth = callPackage ../development/libraries/loudmouth { };
loudmouth library added svn path=/nixpkgs/trunk/; revision=10359
2008-01-28 20:49:25 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lzo = callPackage ../development/libraries/lzo { };
* Converted more packages. svn path=/nixpkgs/trunk/; revision=488
2003-11-06 16:24:19 +01:00
Add older mdds as libreoffice does not build with current version.
2013-12-21 22:24:07 +01:00
mdds_0_7_1 = callPackage ../development/libraries/mdds/0.7.1.nix { };
Add mdds (libreoffice dependency)
2012-08-29 22:25:30 +02:00
mdds = callPackage ../development/libraries/mdds { };
* Added Audacious, a fork of beep-media-player (which doesn't seem to work very well after the Glibc update), plus its dependencies. TODO: make an audacious-wrapper that lets Audacious find its plugins automatically. Currently you have to install audacious-plugins and symlink ~/.nix-profile/lib/audacious/* in ~/.local/share/audacious/Plugins. svn path=/nixpkgs/trunk/; revision=10927
2008-03-03 11:55:20 +01:00
# failed to build
mediastreamer: use default/latest ffmpeg
2013-12-23 10:49:18 +01:00
mediastreamer = callPackage ../development/libraries/mediastreamer { };
alsaUtils = alsa.alsaUtils added: services need this svn path=/nixpkgs/branches/stdenv-updates/; revision=10535
2008-02-07 10:43:10 +01:00
Add pcmanfm-1.2.0
2014-03-01 19:37:39 +01:00
menu-cache = callPackage ../development/libraries/menu-cache { };
pkgs/top-level/all-packages.nix: implement 'mesaSupported' attribute on top of mesaPlatforms Thanks to Florian Friesdorf for pointing out the inconsistency in these attributes.
2012-12-06 11:28:23 +01:00
mesaSupported = lib.elem system lib.platforms.mesaPlatforms;
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
mesaDarwinOr = alternative: if stdenv.isDarwin
then callPackage ../development/libraries/mesa-darwin { }
else alternative;
mesa_noglu = mesaDarwinOr (callPackage ../development/libraries/mesa {
mesa: use grsec at build time, override at run time This is needed for grsecurity kernels to be able to build stuff (e.g. pango). With grsec the libGL is slower, but we don't care much at build time, so we can share binaries among grsec and nogrsec. This adds 2-3 MB to nogrsec closures that use mesa drivers (libGL is doubled).
2014-03-02 08:50:41 +01:00
# makes it slower, but during runtime we link against just mesa_drivers
# through /run/opengl-driver*, which is overriden according to config.grsecurity
grsecEnabled = true;
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
});
mesa_glu = mesaDarwinOr (callPackage ../development/libraries/mesa-glu { });
fix mesa_drivers
2014-08-13 06:31:37 +02:00
mesa_drivers = mesaDarwinOr (
let mo = mesa_noglu.override {
grsecEnabled = config.grsecurity or false;
mesa: create a buildEnv that joins mesa (without glu) and glu Since mesa-9.x, upstream has separated mesa and glu. @peti suggested using buildEnv to create a mesa environment that acts like old mesa, which is what this commit does.
2013-03-24 12:36:33 +01:00
};
fix mesa_drivers
2014-08-13 06:31:37 +02:00
in mo.drivers
);
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
mesa = mesaDarwinOr (buildEnv {
name = "mesa-${mesa_noglu.version}";
paths = [ mesa_noglu mesa_glu ];
});
pkgs/build-support/native-darwin-x11-and-opengl: lift native X11 and OpenGL implementation from Darwin into the Nix store
2013-01-28 19:30:32 +01:00
added seperate meta-environment packages, use callpackage for aterm28 svn path=/nixpkgs/trunk/; revision=23394
2010-08-24 15:20:55 +02:00
metaEnvironment = recurseIntoAttrs (let callPackage = newScope pkgs.metaEnvironment; in rec {
sdfLibrary = callPackage ../development/libraries/sdf-library { aterm = aterm28; };
toolbuslib = callPackage ../development/libraries/toolbuslib { aterm = aterm28; inherit (windows) w32api; };
cLibrary = callPackage ../development/libraries/c-library { aterm = aterm28; };
errorSupport = callPackage ../development/libraries/error-support { aterm = aterm28; };
ptSupport = callPackage ../development/libraries/pt-support { aterm = aterm28; };
ptableSupport = callPackage ../development/libraries/ptable-support { aterm = aterm28; };
configSupport = callPackage ../development/libraries/config-support { aterm = aterm28; };
asfSupport = callPackage ../development/libraries/asf-support { aterm = aterm28; };
tideSupport = callPackage ../development/libraries/tide-support { aterm = aterm28; };
rstoreSupport = callPackage ../development/libraries/rstore-support { aterm = aterm28; };
sdfSupport = callPackage ../development/libraries/sdf-support { aterm = aterm28; };
sglr = callPackage ../development/libraries/sglr { aterm = aterm28; };
ascSupport = callPackage ../development/libraries/asc-support { aterm = aterm28; };
pgen = callPackage ../development/libraries/pgen { aterm = aterm28; };
});
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ming = callPackage ../development/libraries/ming { };
Add Ming, a C library to generate Flash files. svn path=/nixpkgs/trunk/; revision=12786
2008-09-02 15:43:53 +02:00
minizip: New package based on zlib derivation. This is needed by Chromium and is part of the zlib source tree in contrib/, so let's propagate the version of zlib and use the same source tree. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-18 02:21:10 +01:00
minizip = callPackage ../development/libraries/minizip { };
Add new package minmay in version 1.0.0. This is a fork of the iksemel library, which is no longer maintained and is highly broken in regards to TLS support (even in the release versions). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-07-04 11:12:01 +02:00
minmay = callPackage ../development/libraries/minmay { };
miro: New package, version 6.0. I actually had this breeding in my nixpkgs overrides for a year and only recently took the time to fix it and thus revive my video feeds :-) The package uses a patch which is removing the dependency on gconf and switches to storage within a shelve in ~/.miro/config instead. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-10-28 19:15:32 +01:00
miro = callPackage ../applications/video/miro {
inherit (pythonPackages) pywebkitgtk pysqlite pycurl mutagen;
};
mkvtoolnix: 4.4.0 svn path=/nixpkgs/trunk/; revision=25925
2011-02-12 21:18:53 +01:00
mkvtoolnix = callPackage ../applications/video/mkvtoolnix { };
Add SDL variant with pulseaudio enabled, this fixes choppy sound in Kdenlive I would rather enable pulseaudio by default for SDL as it will probably fix issues for other programs too.
2014-07-27 19:35:09 +02:00
mlt-qt4 = callPackage ../development/libraries/mlt {
qt = qt4;
SDL = SDL_pulseaudio;
};
Adding kdenlive, and as a side effect, mlt. Kdenlive looks for some binaries in PATH, so some dependencies may be fulfilled not by kdenlive nix expression. svn path=/nixpkgs/trunk/; revision=21458
2010-04-30 15:12:07 +02:00
Add SDL variant with pulseaudio enabled, this fixes choppy sound in Kdenlive I would rather enable pulseaudio by default for SDL as it will probably fix issues for other programs too.
2014-07-27 19:35:09 +02:00
mlt-qt5 = callPackage ../development/libraries/mlt {
qt = qt5;
SDL = SDL_pulseaudio;
};
mps: version 1.113.0 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-25 02:32:39 +01:00
Add movit: High-performance, high-quality video filters for the GPU NOTE: movit expected to be able to read source files from gtest, so I also made them available. squash
2014-07-27 12:17:10 +02:00
movit = callPackage ../development/libraries/movit { };
Adding kdenlive, and as a side effect, mlt. Kdenlive looks for some binaries in PATH, so some dependencies may be fulfilled not by kdenlive nix expression. svn path=/nixpkgs/trunk/; revision=21458
2010-04-30 15:12:07 +02:00
mps: version 1.113.0 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-25 02:32:39 +01:00
mps = callPackage ../development/libraries/mps { };
* mpeg2dec -> libmpeg2, and updated to 0.5.1. svn path=/nixpkgs/branches/kde-4.7/; revision=27949
2011-07-25 21:07:36 +02:00
libmpeg2 = callPackage ../development/libraries/libmpeg2 { };
mpeg2dec = libmpeg2;
Tried to add kuickshow (a pretty fast image viewer that used to be distributed by default in KDE). Unfortunately it doesn't work, because of some strange problems with mime types. But well, it compiles. The libraries are useful anyway: - arts (kde) - imlib (gnome) - libungif (aka libgif) svn path=/nixpkgs/trunk/; revision=6111
2006-08-13 11:46:54 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
msilbc = callPackage ../development/libraries/msilbc { };
ilbc and msilbc libraries added svn path=/nixpkgs/branches/stdenv-updates/; revision=10570
2008-02-10 18:35:03 +01:00
Add mp4v2 svn path=/nixpkgs/trunk/; revision=23795
2010-09-14 16:29:31 +02:00
mp4v2 = callPackage ../development/libraries/mp4v2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mpc = callPackage ../development/libraries/mpc { };
Add MPC. svn path=/nixpkgs/trunk/; revision=21399
2010-04-28 14:36:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mpich2 = callPackage ../development/libraries/mpich2 { };
Add MPICH2, an implementation of the Message Passing Interface. svn path=/nixpkgs/trunk/; revision=10807
2008-02-21 17:17:43 +01:00
Add mtdev svn path=/nixpkgs/trunk/; revision=28366
2011-08-08 02:25:38 +02:00
mtdev = callPackage ../development/libraries/mtdev { };
added mtpfs to mount MTP devices via usb using FUSE
2014-03-30 13:00:25 +02:00
mtpfs = callPackage ../tools/filesystems/mtpfs { };
mu: fix build by using older texinfo
2013-08-27 15:41:00 +02:00
mu = callPackage ../tools/networking/mu {
texinfo = texinfo4;
};
mu0 -> mu, version bump
2012-12-25 20:59:48 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
muparser = callPackage ../development/libraries/muparser { };
Adding muparser and meshlab. svn path=/nixpkgs/trunk/; revision=15585
2009-05-13 12:21:29 +02:00
added gpodder package
2014-07-20 21:12:05 +02:00
mygpoclient = callPackage ../development/python-modules/mygpoclient { };
Adding Rigs of Rods. Basically it builds, but I still don't know how to run it. I imagine the installPhase is still too poor, but it's better than nothing. I also added two mygui versions. That stable, and that required by Rigs of Roads (svn). svn path=/nixpkgs/trunk/; revision=26618
2011-03-31 00:08:33 +02:00
mygui = callPackage ../development/libraries/mygui {};
myguiSvn = callPackage ../development/libraries/mygui/svn.nix {};
Updating angelscript to 2.22.1. Adding mysocketw. Adding ogre-paged. Fixing the caelum licence. svn path=/nixpkgs/trunk/; revision=32549
2012-02-24 22:13:14 +01:00
mysocketw = callPackage ../development/libraries/mysocketw { };
Add MyThes
2012-08-29 22:35:30 +02:00
mythes = callPackage ../development/libraries/mythes { };
nanomsg: new package Socket library built in C but provides bindings in many languages. Highly efficient and easy to use. [@bjornfor: whitespace fixes, quote shell variables and add meta.platforms]
2013-11-15 17:50:59 +01:00
nanomsg = callPackage ../development/libraries/nanomsg { };
ncurses: Remove version 5.4 It's not used anywhere, and doesn't build: http://hydra.nixos.org/build/7204910
2013-12-20 11:14:15 +01:00
ncurses = callPackage ../development/libraries/ncurses {
utf-8 was not working in cross-built ncurses programs due to some old problem cross-building ncursesw not present anymore. I reenable unicode cross-building. svn path=/nixpkgs/branches/stdenv-updates/; revision=24245
2010-10-12 21:06:04 +02:00
unicode = system != "i686-cygwin";
I made the whole nixpkgs dependencies available to the cross compiler, no needing to keep a new tree of expressions apart for the expressions to get cross-compiled. I changed the whole way of using cross compilation with nixpkgs, which before was done through a simple adapter. Now the adapter became complex, and I've tried to avoid the most obvious recursivities. For example, the fetchurl expression should never be cross-compiled, as the gmp, mpfr, and some others, like some ncurses, perl, ... I made overrided copies of those necessary as perlNoCross, ncursesNoCross, as stdenvNoCross, keeping in mind that the stdenv (capable of cross compilation) is built upon stdenvNoCross using an adapter. So, to cross compile, instead of building using "nixpkgs/default.nix", you should build with your own "myarchiteture.nix", which should have contents like these, for example: import /etc/nixos/nixpkgs/default.nix { crossSystem = { config = "armv5tel-unknown-linux-gnueabi"; bigEndian = false; arch = "arm"; float = "soft"; }; } svn path=/nixpkgs/branches/stdenv-updates/; revision=18398
2009-11-17 23:58:48 +01:00
};
neon: remove obsolete versions 0.26 and 0.28
2013-02-21 12:03:18 +01:00
neon = callPackage ../development/libraries/neon {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
compressionSupport = true;
sslSupport = true;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
All-packages changes for last commits svn path=/nixpkgs/trunk/; revision=15561
2009-05-12 06:28:30 +02:00
nethack = builderDefsPackage (import ../games/nethack) {
inherit ncurses flex bison;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nettle = callPackage ../development/libraries/nettle { };
Add GNU Nettle, a cryptographic library. svn path=/nixpkgs/trunk/; revision=16127
2009-07-01 17:42:01 +02:00
Updating elfutils/perf to cross-build. I tested this for the nanonote. I add newt, checking that it cross-builds too. I update perf to have newt support, and now it's also finding python, whatever that means. I've not tested if 'python' as buildInputs is enough. svn path=/nixpkgs/trunk/; revision=31353
2012-01-06 17:45:14 +01:00
newt = callPackage ../development/libraries/newt { };
Add nix-plugins package
2014-06-28 00:25:34 +02:00
nix-plugins = callPackage ../development/libraries/nix-plugins {
nix = pkgs.nixUnstable;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nspr = callPackage ../development/libraries/nspr { };
* Added NSPR, the Netscape Portable Runtime, and use it in Xulrunner and Firefox. * Xulrunner: don't install the tests. This saves a few megabytes. svn path=/nixpkgs/trunk/; revision=16173
2009-07-04 14:25:35 +02:00
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
nss = lowPrio (callPackage ../development/libraries/nss { });
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
pkgs/top-level/all-packages.nix: strip trailing whitenspace svn path=/nixpkgs/trunk/; revision=23118
2010-08-11 17:49:42 +02:00
nssTools = callPackage ../development/libraries/nss {
updated nss and nspr, added variant of nss including tools svn path=/nixpkgs/trunk/; revision=23105
2010-08-11 11:38:09 +02:00
includeTools = true;
};
Use fresh libnl for ntrack
2013-12-07 09:36:31 +01:00
ntrack = callPackage ../development/libraries/ntrack { };
ntrack-011 svn path=/nixpkgs/trunk/; revision=27386
2011-06-07 23:50:48 +02:00
Add nvidia-texture-tools.
2014-06-18 23:17:43 +02:00
nvidia-texture-tools = callPackage ../development/libraries/nvidia-texture-tools { };
Minor cleanup
2012-11-29 14:40:25 +01:00
ode = builderDefsPackage (import ../development/libraries/ode) { };
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
Adding OGRE - object-oriented graphical engine svn path=/nixpkgs/trunk/; revision=25240
2010-12-22 15:50:13 +01:00
ogre = callPackage ../development/libraries/ogre {};
Added Open Dynamics Engine svn path=/nixpkgs/trunk/; revision=13520
2008-11-30 17:50:05 +01:00
Updating angelscript to 2.22.1. Adding mysocketw. Adding ogre-paged. Fixing the caelum licence. svn path=/nixpkgs/trunk/; revision=32549
2012-02-24 22:13:14 +01:00
ogrepaged = callPackage ../development/libraries/ogrepaged { };
Added libdwarf, libevent 1.4, libmcrypt, libmemcached, oniguruma. These are dependencies for HipHop Virtual Machine.
2012-12-01 21:28:32 +01:00
oniguruma = callPackage ../development/libraries/oniguruma { };
Updating angelscript to 2.22.1. Adding mysocketw. Adding ogre-paged. Fixing the caelum licence. svn path=/nixpkgs/trunk/; revision=32549
2012-02-24 22:13:14 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openal = callPackage ../development/libraries/openal { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
# added because I hope that it has been easier to compile on x86 (for blender)
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openalSoft = callPackage ../development/libraries/openal-soft { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openbabel = callPackage ../development/libraries/openbabel { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Updating opencascade to 6.6.0
2013-05-30 12:09:44 +02:00
opencascade = callPackage ../development/libraries/opencascade { };
Adding opencascade 6.4.0. svn path=/nixpkgs/trunk/; revision=13874
2009-01-27 09:14:27 +01:00
I forgot to bring back opencascade 6.5 overrides.
2013-05-31 10:08:38 +02:00
opencascade_6_5 = callPackage ../development/libraries/opencascade/6.5.nix {
opencascade: fixing build by downgrading the automake used
2012-08-09 17:10:46 +02:00
automake = automake111x;
Updating opencascade to 6.5.2. I had to bring an older ftgl in. svn path=/nixpkgs/trunk/; revision=32742
2012-03-02 14:47:37 +01:00
ftgl = ftgl212;
};
Adding opencascade 6.4.0. svn path=/nixpkgs/trunk/; revision=13874
2009-01-27 09:14:27 +01:00
opencascade: Adding ode version (Open Community version)
2013-03-15 14:34:07 +01:00
opencascade_oce = callPackage ../development/libraries/opencascade/oce.nix { };
Adding CGAL: Computational Geometry Algorithms Library svn path=/nixpkgs/trunk/; revision=31868
2012-01-26 19:28:53 +01:00
opencsg = callPackage ../development/libraries/opencsg { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openct = callPackage ../development/libraries/openct { };
Downgrading the opensc library version to 0.11.7, that required for the Spanish national id smartcard (DNIe). Adding the opensc dnie driver. svn path=/nixpkgs/trunk/; revision=19325
2010-01-10 01:22:29 +01:00
opencv: use default/latest ffmpeg
2013-12-23 10:50:07 +01:00
opencv = callPackage ../development/libraries/opencv { };
Fixing the gcc-wrapper, so it does not link when gcc is called with '-x something'. It should not link at least for '-x c-header' and '-x c++-header', and maybe link for '-x c' or '-x c++', but we expect noone will be linking using these later strings. Adding opencv, which required '-x c-header' working, and that's why I have updated gcc wrapper. svn path=/nixpkgs/branches/stdenv-updates/; revision=19491
2010-01-16 22:26:10 +01:00
Fixing libdecodeqr build by using previous OpenCV svn path=/nixpkgs/trunk/; revision=28169
2011-08-05 18:13:20 +02:00
opencv_2_1 = callPackage ../development/libraries/opencv/2.1.nix {
More 'libpng = libpng12' svn path=/nixpkgs/branches/libpng15/; revision=31889
2012-01-27 18:55:41 +01:00
libpng = libpng12;
Fixing the gcc-wrapper, so it does not link when gcc is called with '-x something'. It should not link at least for '-x c-header' and '-x c++-header', and maybe link for '-x c' or '-x c++', but we expect noone will be linking using these later strings. Adding opencv, which required '-x c-header' working, and that's why I have updated gcc wrapper. svn path=/nixpkgs/branches/stdenv-updates/; revision=19491
2010-01-16 22:26:10 +01:00
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
# this ctl version is needed by openexr_viewers
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openexr_ctl = callPackage ../development/libraries/openexr_ctl { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openexr = callPackage ../development/libraries/openexr { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
openldap: fix build on darwin
2014-09-01 05:55:46 +02:00
openldap = callPackage ../development/libraries/openldap {
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
openlierox: fixing and updating.
2013-04-06 12:09:07 +02:00
openlierox = callPackage ../games/openlierox { };
Adding OpenLieroX svn path=/nixpkgs/trunk/; revision=16617
2009-08-08 20:18:33 +02:00
libopensc-dnie: fix reference to opensc The package is still broken, though.
2013-12-02 13:26:21 +01:00
libopensc_dnie = callPackage ../development/libraries/libopensc-dnie { };
Downgrading the opensc library version to 0.11.7, that required for the Spanish national id smartcard (DNIe). Adding the opensc dnie driver. svn path=/nixpkgs/trunk/; revision=19325
2010-01-10 01:22:29 +01:00
Rename oiio to openimageio (more explicit) and add opencolorio
2013-03-28 00:47:47 +01:00
opencolorio = callPackage ../development/libraries/opencolorio { };
Blender 2.66 WIP
2013-03-27 22:25:33 +01:00
Corresponding all-packages.nix changes svn path=/nixpkgs/trunk/; revision=25233
2010-12-22 11:47:12 +01:00
ois = callPackage ../development/libraries/ois {};
Adding Ekiga svn path=/nixpkgs/trunk/; revision=23653
2010-09-06 01:37:54 +02:00
opal = callPackage ../development/libraries/opal {};
keep lcms versioning in all-packages.nix
2013-06-29 16:07:15 +02:00
openjpeg = callPackage ../development/libraries/openjpeg { lcms = lcms2; };
Adding 'mupdf', a lightweight PDF 1.7 viewer As a side effect, I add openjpeg and jbig2dec. svn path=/nixpkgs/trunk/; revision=23069
2010-08-09 22:59:38 +02:00
Passing giflib 4.1.x to OpenSceneGraph for now
2013-12-08 10:13:19 +01:00
openscenegraph = callPackage ../development/libraries/openscenegraph {
giflib = giflib_4_1;
openscenegraph: pin to ffmpeg 0.10
2013-12-16 14:36:15 +01:00
ffmpeg = ffmpeg_0_10;
Passing giflib 4.1.x to OpenSceneGraph for now
2013-12-08 10:13:19 +01:00
};
Adding OpenSceneGraph and SimGear svn path=/nixpkgs/trunk/; revision=26769
2011-04-09 18:43:00 +02:00
openspades: Initial 0.0.12
2014-06-27 18:21:17 +02:00
openspades = callPackage ../games/openspades {};
nixpkgs: libressl 2.0.5 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-08-20 07:51:15 +02:00
libressl = callPackage ../development/libraries/libressl { };
nixpkgs: boringssl 20140820-a7d1363f Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-08-20 08:23:40 +02:00
boringssl = callPackage ../development/libraries/boringssl { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
openssl = callPackage ../development/libraries/openssl {
* curl: build with OpenSSL (https) support by default. * Some fetchurl-related refactoring. The `realCurl' attribute is gone, `curl' is the real thing. To prevent an infinite recursion in `fetchurl' (because it depends on curl and building curl needs fetchurl), curl and its dependencies (openssl, zlib, perl) use `fetchurlBoot', which is the fetchurl used by the previous bootstrap phase (e.g. the statically linked version of curl for stdenv-linux). So as a result you can use https:// urls almost everywhere. There's also some hackery to prevent a different curl from being built in every stdenv-linux bootstrap phase (namely the stdenv.fetchurl attribute which allows fetchurl to be overriden everywhere). svn path=/nixpkgs/trunk/; revision=11905
2008-05-27 09:49:55 +02:00
fetchurl = fetchurlBoot;
Adding cryptodev-linux, and made openssl use it optionally. I'm trying to get the CESA of the sheevaplug available to openssl.
2012-09-23 20:50:24 +02:00
cryptodevHeaders = linuxPackages.cryptodev.override {
fetchurl = fetchurlBoot;
onlyHeaders = true;
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Linphone 3.6.1 Lots of updates and new/old libs to get the latest linphone It segfaults on running.
2013-06-29 16:50:56 +02:00
ortp = callPackage ../development/libraries/ortp {
srtp = srtp_linphone;
};
ortp added svn path=/nixpkgs/trunk/; revision=10358
2008-01-28 20:49:08 +01:00
p11-kit svn path=/nixpkgs/trunk/; revision=30292
2011-11-07 17:48:14 +01:00
p11_kit = callPackage ../development/libraries/p11-kit { };
added paperkey package
2014-08-04 13:11:29 +02:00
paperkey = callPackage ../tools/security/paperkey { };
No need to inherit glib, gtk etc. from gnome/gtkLibs svn path=/nixpkgs/trunk/; revision=33081
2012-03-14 20:35:49 +01:00
pangoxsl = callPackage ../development/libraries/pangoxsl { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Adding pcl. (Also updating flann, reworking vtk)
2013-05-09 12:23:21 +02:00
pcl = callPackage ../development/libraries/pcl {
vtk = vtkWithQt4;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pcre = callPackage ../development/libraries/pcre {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
unicodeSupport = config.pcre.unicode or true;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
Added gdmap, changed builder-defs to use derivation attribute on propagatedBuildInputs, manually fixed Xorg expression problem for Compiz, various fixes. svn path=/nixpkgs/trunk/; revision=9812
2007-12-01 17:20:23 +01:00
added libxpdf and pdf2xml svn path=/nixpkgs/trunk/; revision=23427
2010-08-25 16:25:51 +02:00
pdf2xml = callPackage ../development/libraries/pdf2xml {} ;
* Move Phonon out of KDE. svn path=/nixpkgs/branches/kde-4.7/; revision=27988
2011-07-28 14:20:12 +02:00
phonon = callPackage ../development/libraries/phonon { };
phonon_backend_gstreamer = callPackage ../development/libraries/phonon-backend-gstreamer { };
phonon-backend-vlc: use callPackage svn path=/nixpkgs/trunk/; revision=31402
2012-01-07 16:31:27 +01:00
phonon_backend_vlc = callPackage ../development/libraries/phonon-backend-vlc { };
Add phonon-backend-vlc svn path=/nixpkgs/trunk/; revision=22939
2010-08-04 12:04:40 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
physfs = callPackage ../development/libraries/physfs { };
Updating neverball. That required adding physfs. svn path=/nixpkgs/trunk/; revision=18220
2009-11-06 20:25:45 +01:00
Adding meo: Multiple Eyepairs Only I also add the pkcs11helper it needs.
2013-05-20 23:12:21 +02:00
pkcs11helper = callPackage ../development/libraries/pkcs11helper { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
plib = callPackage ../development/libraries/plib { };
PLIB: a suite of portable game libraries. svn path=/nixpkgs/trunk/; revision=13051
2008-10-12 16:27:51 +02:00
Add the pocketsphinx voice recognition library svn path=/nixpkgs/trunk/; revision=26686
2011-04-04 20:50:39 +02:00
pocketsphinx = callPackage ../development/libraries/pocketsphinx { };
Fixing one missed trouble coming from the merge from trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=23841
2010-09-17 21:14:47 +02:00
podofo = callPackage ../development/libraries/podofo { };
Adding calibre. This involved also: - Adding podofo - Adding some new python packages - Making new pkgs attributes for python packages to build with python 2.6 - Updating some python packages expressions to allow python 2.6, and not only 2.5. svn path=/nixpkgs/trunk/; revision=19303
2010-01-07 23:47:30 +01:00
polkit: major update 0.105 -> 0.112 - It now uses JavaScript for configuration (only), so I had to "convert" config for NetworkManager. - I tested suspend/restart/(un)mount on KDE/Xfce, Phreedom tested NetworkManager config conversion.
2013-11-09 16:29:18 +01:00
polkit = callPackage ../development/libraries/polkit {
spidermonkey = spidermonkey_185;
};
* Added PolicyKit and eggdbus. There is a newer version of PolicyKit (0.93), but it doesn't compile with the current glib. svn path=/nixpkgs/trunk/; revision=16704
2009-08-13 09:55:11 +02:00
* Move Attica and polkit-qt-1 out of desktops/kde (since they're not part of a KDE release). svn path=/nixpkgs/branches/kde-4.7/; revision=27643
2011-07-07 22:47:38 +02:00
polkit_qt_1 = callPackage ../development/libraries/polkit-qt-1 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
policykit = callPackage ../development/libraries/policykit { };
Fix GConf from Gnome 2.26 svn path=/nixpkgs/trunk/; revision=16751
2009-08-17 20:31:42 +02:00
Fix .deepOverride on poppler, glib By moving the default derivation into callPackage call, close #1115.
2013-10-24 18:08:48 +02:00
poppler = callPackage ../development/libraries/poppler { lcms = lcms2; };
poppler: share most things between glib and qt4 versions Most of the stuff was duplicated (headers, the core library). The new solution makes the _qt4 package use the _glib one, because it depended on glib through cairo anyway (and _glib bindings themselves are just ~350kB). This also fixes a problem that mergeAttrsByFuncDefaultsClean didn't merge patches, which affected dbus.libs.
2013-04-21 22:15:38 +02:00
popplerQt4 = poppler.poppler_qt4;
whoops, add libgcrypt and libotr here too svn path=/nixpkgs/trunk/; revision=9143
2007-08-16 23:45:10 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
popt = callPackage ../development/libraries/popt { };
Tried to add kuickshow (a pretty fast image viewer that used to be distributed by default in KDE). Unfortunately it doesn't work, because of some strange problems with mime types. But well, it compiles. The libraries are useful anyway: - arts (kde) - imlib (gnome) - libungif (aka libgif) svn path=/nixpkgs/trunk/; revision=6111
2006-08-13 11:46:54 +02:00
portaudio: fix build on darwin * remove alsaLib from build inputs * add --build=x86_64 to configure flags * add --without-oss to configure flags * add --enable-static to configure flags * add --enable-shared to configure flags * add framework header files * disable failed tests * copy all headers on install * build with gccApple
2013-07-06 09:56:54 +02:00
portaudio = callPackage ../development/libraries/portaudio {
# resolves a variety of compile-time errors
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
};
Try fixing Audacity svn path=/nixpkgs/trunk/; revision=25340
2011-01-02 18:13:34 +01:00
portaudioSVN = callPackage ../development/libraries/portaudio/svn-head.nix { };
Adding espeak (and one of the libraries it needs, portaudio) svn path=/nixpkgs/trunk/; revision=23351
2010-08-22 14:08:55 +02:00
portmidi: New package in version 217. This uses a patch from Gentoo to disable Java support for now, as it is not needed for supporting Mixxx (which is the package I'm preparing). Hopefully, the patch will be applied upstream so we can safely drop it here. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-10-28 03:09:10 +01:00
portmidi = callPackage ../development/libraries/portmidi {};
Add prison svn path=/nixpkgs/trunk/; revision=28593
2011-08-15 20:05:16 +02:00
prison = callPackage ../development/libraries/prison { };
Adding espeak (and one of the libraries it needs, portaudio) svn path=/nixpkgs/trunk/; revision=23351
2010-08-22 14:08:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
proj = callPackage ../development/libraries/proj { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
postgis = callPackage ../development/libraries/postgis { };
adding postgis + script enabling postgis features Exporting builder.pl because it will be used in NixOS postgresql module svn path=/nixpkgs/trunk/; revision=21691
2010-05-09 22:38:16 +02:00
Add Google's Protocol Buffers. svn path=/nixpkgs/trunk/; revision=24547
2010-10-30 23:44:22 +02:00
protobuf = callPackage ../development/libraries/protobuf { };
Adding umurmur and protobuf-c.
2012-09-25 19:35:03 +02:00
protobufc = callPackage ../development/libraries/protobufc { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pth = callPackage ../development/libraries/pth { };
pth added svn path=/nixpkgs/trunk/; revision=10340
2008-01-28 20:43:03 +01:00
Adding Ekiga svn path=/nixpkgs/trunk/; revision=23653
2010-09-06 01:37:54 +02:00
ptlib = callPackage ../development/libraries/ptlib {};
Add re2, an efficient, principled regular expression library
2013-08-15 15:07:04 +02:00
re2 = callPackage ../development/libraries/re2 { };
Move qca2 outside of kde-4.x svn path=/nixpkgs/trunk/; revision=26053
2011-02-22 10:53:01 +01:00
qca2 = callPackage ../development/libraries/qca2 {};
qca2_ossl = callPackage ../development/libraries/qca2/ossl.nix {};
Move qimageblitz outside of kde-4.x svn path=/nixpkgs/trunk/; revision=26056
2011-02-22 12:54:42 +01:00
qimageblitz = callPackage ../development/libraries/qimageblitz {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
qjson = callPackage ../development/libraries/qjson { };
Add qjson svn path=/nixpkgs/trunk/; revision=22451
2010-07-04 22:59:47 +02:00
Add qoauth
2012-08-08 10:59:03 +02:00
qoauth = callPackage ../development/libraries/qoauth { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
qt3 = callPackage ../development/libraries/qt-3 {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
openglSupport = mesaSupported;
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
libpng = libpng12;
* MythTV 0.21. svn path=/nixpkgs/trunk/; revision=12177
2008-06-23 11:01:04 +02:00
};
Switch to kde-4.5 by default svn path=/nixpkgs/trunk/; revision=24192
2010-10-10 09:39:01 +02:00
qt4 = pkgs.kde4.qt4;
* qt-4 -> qt-4.4. * kde-4.2 shouldn't depend on poppler built with qt 4.5. svn path=/nixpkgs/trunk/; revision=17084
2009-09-13 13:04:54 +02:00
Qt-4.8.0 Hardcode paths to many dlopen()ed libraries. This should fix: * Print dialog fails to find CUPS; * flashplugin. Add optional support for GTK style. Disabled by default. svn path=/nixpkgs/trunk/; revision=31064
2011-12-24 22:52:08 +01:00
qt48 = callPackage ../development/libraries/qt-4.x/4.8 {
# GNOME dependencies are not used unless gtkStyle == true
qt4: maintenance update 4.8.4 -> 4.8.5 Also fixed search path for libGL. Tested building against master.
2013-07-04 11:37:25 +02:00
mesa = mesa_noglu;
Make nixpkgs ready to gtkLibs attrset removal svn path=/nixpkgs/trunk/; revision=33091
2012-03-14 23:44:41 +01:00
inherit (pkgs.gnome) libgnomeui GConf gnome_vfs;
qt48: minimize default dependencies on non-Linux
2013-06-18 22:00:20 +02:00
cups = if stdenv.isLinux then cups else null;
qt48: fix build on darwin * build with clang
2013-07-04 07:05:41 +02:00
# resolve unrecognised flag '-fconstant-cfstrings' errors
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
Qt-4.8.0 Hardcode paths to many dlopen()ed libraries. This should fix: * Print dialog fails to find CUPS; * flashplugin. Add optional support for GTK style. Disabled by default. svn path=/nixpkgs/trunk/; revision=31064
2011-12-24 22:52:08 +01:00
};
qt: make package names of "full" variants appear as such Currently there is no distinction in the package names of Qt packages whether they are "full" or not (i.e. coming from a qt5Full or qt5 attribute). Currently: $ nix-env -f. -qaP | grep "^qt[45]" qt48Full qt-4.8.6 qt5Full qt-5.2.1 qt5 qt-5.2.1 qt53 qt-5.3.1 qt53Full qt-5.3.1 [...] With this change: $ nix-env -f. -qaP | grep "^qt[45]" qt5 qt-5.2.1 qt53 qt-5.3.1 qt48Full qt-full-4.8.6 qt5Full qt-full-5.2.1 qt53Full qt-full-5.3.1 [...]
2014-08-23 13:31:17 +02:00
qt48Full = appendToName "full" (qt48.override {
qtcreator: Update to 2.7.1 and improvements (merge #579) - Qt is now directly overriden in QtCreator's definition. - qt48Full can be used in a development environment to enable access to docs demos and examples. NOTE: It may be required to remove older configuration files located in ~/.config/QtProject and at ~/.config/Trolltech.conf to reconfigure qtcreator with the correct paths. I have found /nix/store/... paths in the following files: $HOME/.config/QtProject/qtcreator/toolchains.xml $HOME/.config/QtProject/qtcreator/qtversion.xml $HOME/.config/QtProject/qtcreator/helpcollection.qhc At the first launch, be sure to check your qtcreator's configuration by selecting Tools->Options. The most important parts are the Kits and QtVersion tabs located in the Build & Run section.
2013-06-01 00:05:29 +02:00
docs = true;
demos = true;
examples = true;
qtcreator: Make the qt package optional and introduce the QtSDK To give the ability to use a different Qt version than the default one (which can build 3 different times Qt Libraries if we mixed the default one, the qtcreator one and the version including all the examples and the docs). Right now a developer can choose to directly install the QtSDK which includes a "full" (developerBuild + docs + examples) Qt version and uses it to build QtCreator. The possibility to only install QtCreator and its previous behavior has been kept for flexibility purposes (we do not need to force someone on the SDK approach).
2013-09-30 15:15:25 +02:00
developerBuild = true;
qt: make package names of "full" variants appear as such Currently there is no distinction in the package names of Qt packages whether they are "full" or not (i.e. coming from a qt5Full or qt5 attribute). Currently: $ nix-env -f. -qaP | grep "^qt[45]" qt48Full qt-4.8.6 qt5Full qt-5.2.1 qt5 qt-5.2.1 qt53 qt-5.3.1 qt53Full qt-5.3.1 [...] With this change: $ nix-env -f. -qaP | grep "^qt[45]" qt5 qt-5.2.1 qt53 qt-5.3.1 qt48Full qt-full-4.8.6 qt5Full qt-full-5.2.1 qt53Full qt-full-5.3.1 [...]
2014-08-23 13:31:17 +02:00
});
qtcreator: Make the qt package optional and introduce the QtSDK To give the ability to use a different Qt version than the default one (which can build 3 different times Qt Libraries if we mixed the default one, the qtcreator one and the version including all the examples and the docs). Right now a developer can choose to directly install the QtSDK which includes a "full" (developerBuild + docs + examples) Qt version and uses it to build QtCreator. The possibility to only install QtCreator and its previous behavior has been kept for flexibility purposes (we do not need to force someone on the SDK approach).
2013-09-30 15:15:25 +02:00
qt4SDK = qtcreator.override {
sdkBuild = true;
qtLib = qt48Full;
};
qt: make package names of "full" variants appear as such Currently there is no distinction in the package names of Qt packages whether they are "full" or not (i.e. coming from a qt5Full or qt5 attribute). Currently: $ nix-env -f. -qaP | grep "^qt[45]" qt48Full qt-4.8.6 qt5Full qt-5.2.1 qt5 qt-5.2.1 qt53 qt-5.3.1 qt53Full qt-5.3.1 [...] With this change: $ nix-env -f. -qaP | grep "^qt[45]" qt5 qt-5.2.1 qt53 qt-5.3.1 qt48Full qt-full-4.8.6 qt5Full qt-full-5.2.1 qt53Full qt-full-5.3.1 [...]
2014-08-23 13:31:17 +02:00
qt53Full = appendToName "full" (qt53.override {
added attrPath="qt53Full" and "attrPath="qt53"; qt-5.2 still default
2014-07-25 12:00:21 +02:00
buildDocs = true;
buildExamples = true;
buildTests = true;
developerBuild = true;
qt: make package names of "full" variants appear as such Currently there is no distinction in the package names of Qt packages whether they are "full" or not (i.e. coming from a qt5Full or qt5 attribute). Currently: $ nix-env -f. -qaP | grep "^qt[45]" qt48Full qt-4.8.6 qt5Full qt-5.2.1 qt5 qt-5.2.1 qt53 qt-5.3.1 qt53Full qt-5.3.1 [...] With this change: $ nix-env -f. -qaP | grep "^qt[45]" qt5 qt-5.2.1 qt53 qt-5.3.1 qt48Full qt-full-4.8.6 qt5Full qt-full-5.2.1 qt53Full qt-full-5.3.1 [...]
2014-08-23 13:31:17 +02:00
});
added attrPath="qt53Full" and "attrPath="qt53"; qt-5.2 still default
2014-07-25 12:00:21 +02:00
qt53 = callPackage ../development/libraries/qt-5/qt-5.3.nix {
mesa = mesa_noglu;
cups = if stdenv.isLinux then cups else null;
# GNOME dependencies are not used unless gtkStyle == true
inherit (gnome) libgnomeui GConf gnome_vfs;
bison = bison2; # error: too few arguments to function 'int yylex(...
};
Add Qt 5.1.1 and its SDK Consider this as a first step towards the integration of Qt5 into nixpkgs, it does not yet intends to replace Qt4 on every packages even if possible. My goal here is to have a first derivation in common between people who needs qt5 for development purposes. The derivation has been written from scratch but I took care to read at the version 4 to re-integrate some patches which are still compatible. However, I did not had enough time to test gtkStyle and flashplayerFix as I do not use any of them. Also, OSX users will have to do some extra work because I do not have any mac. Finally, as some configure flags have changed and in an hope to provide a clear package definition before it becomes mature, I voluntary added some flags which are default. Once every option will be mastered, we will just have to redo a pass on qt5 configure flags and remove the ones which are set by default.
2013-10-16 20:07:18 +02:00
qt5 = callPackage ../development/libraries/qt-5 {
mesa = mesa_noglu;
cups = if stdenv.isLinux then cups else null;
# GNOME dependencies are not used unless gtkStyle == true
inherit (gnome) libgnomeui GConf gnome_vfs;
xxdiff, qt5: use bison2
2014-01-19 11:47:58 +01:00
bison = bison2; # error: too few arguments to function 'int yylex(...
Add Qt 5.1.1 and its SDK Consider this as a first step towards the integration of Qt5 into nixpkgs, it does not yet intends to replace Qt4 on every packages even if possible. My goal here is to have a first derivation in common between people who needs qt5 for development purposes. The derivation has been written from scratch but I took care to read at the version 4 to re-integrate some patches which are still compatible. However, I did not had enough time to test gtkStyle and flashplayerFix as I do not use any of them. Also, OSX users will have to do some extra work because I do not have any mac. Finally, as some configure flags have changed and in an hope to provide a clear package definition before it becomes mature, I voluntary added some flags which are default. Once every option will be mastered, we will just have to redo a pass on qt5 configure flags and remove the ones which are set by default.
2013-10-16 20:07:18 +02:00
};
qt: make package names of "full" variants appear as such Currently there is no distinction in the package names of Qt packages whether they are "full" or not (i.e. coming from a qt5Full or qt5 attribute). Currently: $ nix-env -f. -qaP | grep "^qt[45]" qt48Full qt-4.8.6 qt5Full qt-5.2.1 qt5 qt-5.2.1 qt53 qt-5.3.1 qt53Full qt-5.3.1 [...] With this change: $ nix-env -f. -qaP | grep "^qt[45]" qt5 qt-5.2.1 qt53 qt-5.3.1 qt48Full qt-full-4.8.6 qt5Full qt-full-5.2.1 qt53Full qt-full-5.3.1 [...]
2014-08-23 13:31:17 +02:00
qt5Full = appendToName "full" (qt5.override {
Add Qt 5.1.1 and its SDK Consider this as a first step towards the integration of Qt5 into nixpkgs, it does not yet intends to replace Qt4 on every packages even if possible. My goal here is to have a first derivation in common between people who needs qt5 for development purposes. The derivation has been written from scratch but I took care to read at the version 4 to re-integrate some patches which are still compatible. However, I did not had enough time to test gtkStyle and flashplayerFix as I do not use any of them. Also, OSX users will have to do some extra work because I do not have any mac. Finally, as some configure flags have changed and in an hope to provide a clear package definition before it becomes mature, I voluntary added some flags which are default. Once every option will be mastered, we will just have to redo a pass on qt5 configure flags and remove the ones which are set by default.
2013-10-16 20:07:18 +02:00
buildDocs = true;
buildExamples = true;
buildTests = true;
developerBuild = true;
qt: make package names of "full" variants appear as such Currently there is no distinction in the package names of Qt packages whether they are "full" or not (i.e. coming from a qt5Full or qt5 attribute). Currently: $ nix-env -f. -qaP | grep "^qt[45]" qt48Full qt-4.8.6 qt5Full qt-5.2.1 qt5 qt-5.2.1 qt53 qt-5.3.1 qt53Full qt-5.3.1 [...] With this change: $ nix-env -f. -qaP | grep "^qt[45]" qt5 qt-5.2.1 qt53 qt-5.3.1 qt48Full qt-full-4.8.6 qt5Full qt-full-5.2.1 qt53Full qt-full-5.3.1 [...]
2014-08-23 13:31:17 +02:00
});
Add Qt 5.1.1 and its SDK Consider this as a first step towards the integration of Qt5 into nixpkgs, it does not yet intends to replace Qt4 on every packages even if possible. My goal here is to have a first derivation in common between people who needs qt5 for development purposes. The derivation has been written from scratch but I took care to read at the version 4 to re-integrate some patches which are still compatible. However, I did not had enough time to test gtkStyle and flashplayerFix as I do not use any of them. Also, OSX users will have to do some extra work because I do not have any mac. Finally, as some configure flags have changed and in an hope to provide a clear package definition before it becomes mature, I voluntary added some flags which are default. Once every option will be mastered, we will just have to redo a pass on qt5 configure flags and remove the ones which are set by default.
2013-10-16 20:07:18 +02:00
qt5SDK = qtcreator.override {
sdkBuild = true;
qtLib = qt5Full;
};
qtcreator: Make the qt package optional and introduce the QtSDK To give the ability to use a different Qt version than the default one (which can build 3 different times Qt Libraries if we mixed the default one, the qtcreator one and the version including all the examples and the docs). Right now a developer can choose to directly install the QtSDK which includes a "full" (developerBuild + docs + examples) Qt version and uses it to build QtCreator. The possibility to only install QtCreator and its previous behavior has been kept for flexibility purposes (we do not need to force someone on the SDK approach).
2013-09-30 15:15:25 +02:00
qtcreator = callPackage ../development/qtcreator {
qtLib = qt48.override { developerBuild = true; };
Add qt4_for_skype This build disables some optional features. I'm going to pass this to skype_linux to reduce the size occupied by i686 packages on x86_64 system. svn path=/nixpkgs/trunk/; revision=33217
2012-03-17 21:57:28 +01:00
};
Make qt47 more override-friendly svn path=/nixpkgs/trunk/; revision=23240
2010-08-19 00:53:42 +02:00
qtscriptgenerator = callPackage ../development/libraries/qtscriptgenerator { };
xlock: fixed build and updated to version 5.24 svn path=/nixpkgs/trunk/; revision=17356
2009-09-22 22:16:38 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
quesoglc = callPackage ../development/libraries/quesoglc { };
quesoglc: New nixpkg. svn path=/nixpkgs/trunk/; revision=21580
2010-05-03 17:38:16 +02:00
Add qwt-5.2.1 svn path=/nixpkgs/trunk/; revision=28482
2011-08-11 11:35:10 +02:00
qwt = callPackage ../development/libraries/qwt {};
qwt: add version 6.x (we already have 5.x) 'qgis', one of the few 'qwt' dependees in nixpkgs, fails to build with qwt 6. So I'm not moving the default version away from 5.x. Also, not changing the default allows easy/safe cherry-picking to the stable branch.
2014-05-03 14:09:22 +02:00
qwt6 = callPackage ../development/libraries/qwt/6.nix { };
rabbitmq-c: add version 0.4.1
2013-12-13 17:10:06 +01:00
rabbitmq-c = callPackage ../development/libraries/rabbitmq-c {};
RabbitMQ Java client library: package
2014-07-26 13:32:55 +02:00
rabbitmq-java-client = callPackage ../development/libraries/rabbitmq-java-client {};
Add raul: A C++ utility library primarily aimed at audio/musical applications
2014-03-09 18:00:52 +01:00
raul = callPackage ../development/libraries/audio/raul { };
Adding GNU readline 6.3 apart I set bashInteractive to use it, as it has many relevant fixes.
2014-03-20 13:00:46 +01:00
readline = readline6; # 6.2 works, 6.3 breaks python, parted
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
readline4 = callPackage ../development/libraries/readline/readline4.nix { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
readline5 = callPackage ../development/libraries/readline/readline5.nix { };
Added Axis 1.3. svn path=/nixpkgs/trunk/; revision=5138
2006-04-03 15:02:05 +02:00
readline: Don't use gcc-apple
2014-07-01 13:08:09 +02:00
readline6 = callPackage ../development/libraries/readline/readline6.nix { };
GNU Readline 6.0. svn path=/nixpkgs/branches/stdenv-updates/; revision=14208
2009-02-23 19:10:41 +01:00
readline: Don't use gcc-apple
2014-07-01 13:08:09 +02:00
readline63 = callPackage ../development/libraries/readline/readline6.3.nix { };
Adding GNU readline 6.3 apart I set bashInteractive to use it, as it has many relevant fixes.
2014-03-20 13:00:46 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
librdf_raptor = callPackage ../development/libraries/librdf/raptor.nix { };
pkgs/applications/editors/emacs-modes/magit: updated to version magit-0.7-94-gbf42bf8 Magit has seen plenty of development since version 0.7, but for some reason there haven't been any new releases. This version bump updates the expression to build a current version of Magit directly from the Git repository. This change adds buildInputs 'autoconf' and 'automake'. These tools are required only because we aren't building from a proper release tarball. Once version 0.8 comes out, these dependencies can be dropped again. svn path=/nixpkgs/trunk/; revision=20650
2010-03-16 13:13:40 +01:00
* Update a bunch of dependencies of kdelibs. svn path=/nixpkgs/branches/kde-4.7/; revision=27702
2011-07-11 12:49:21 +02:00
librdf_raptor2 = callPackage ../development/libraries/librdf/raptor2.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
librdf_rasqal = callPackage ../development/libraries/librdf/rasqal.nix { };
pkgs/applications/editors/emacs-modes/magit: updated to version magit-0.7-94-gbf42bf8 Magit has seen plenty of development since version 0.7, but for some reason there haven't been any new releases. This version bump updates the expression to build a current version of Magit directly from the Git repository. This change adds buildInputs 'autoconf' and 'automake'. These tools are required only because we aren't building from a proper release tarball. Once version 0.8 comes out, these dependencies can be dropped again. svn path=/nixpkgs/trunk/; revision=20650
2010-03-16 13:13:40 +01:00
redland-1.0.14, move to librdf/ * rename redland to librdf_redland * add compatibility alias * propagate some inputs svn path=/nixpkgs/trunk/; revision=28589
2011-08-15 20:04:51 +02:00
librdf_redland = callPackage ../development/libraries/librdf/redland.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
librdf = callPackage ../development/libraries/librdf { };
updating redland, adding rasqal, raptor, librdf svn path=/nixpkgs/trunk/; revision=17320
2009-09-21 11:58:21 +02:00
Adding lv2 support LV2 is a portable plugin standard for audio systems, similar in scope to LADSPA, VST, AU, and others. The Calf audio plugin pack uses LV2 and Ardour3 has also been updated to support LV2 Plugins
2012-07-05 23:29:45 +02:00
lilv = callPackage ../development/libraries/audio/lilv { };
lv2 = callPackage ../development/libraries/audio/lv2 { };
add lvtk: A set C++ wrappers around the LV2 C API
2014-03-09 22:12:17 +01:00
lvtk = callPackage ../development/libraries/audio/lvtk { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
qrupdate = callPackage ../development/libraries/qrupdate { };
updating redland, adding rasqal, raptor, librdf svn path=/nixpkgs/trunk/; revision=17320
2009-09-21 11:58:21 +02:00
redland-1.0.14, move to librdf/ * rename redland to librdf_redland * add compatibility alias * propagate some inputs svn path=/nixpkgs/trunk/; revision=28589
2011-08-15 20:04:51 +02:00
redland = pkgs.librdf_redland;
Added my initial KDE 4.4 expression svn path=/nixpkgs/trunk/; revision=19906
2010-02-10 16:06:50 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
rhino = callPackage ../development/libraries/java/rhino {
Add Mozilla Rhino. svn path=/nixpkgs/trunk/; revision=17884
2009-10-19 16:47:04 +02:00
javac = gcj;
jvm = gcj;
};
encfs: packaged. Patch by Ambrus Kaposi. svn path=/nixpkgs/trunk/; revision=24900
2010-11-28 10:59:13 +01:00
rlog = callPackage ../development/libraries/rlog { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
rubberband = callPackage ../development/libraries/rubberband {
adding vamp sdk and rubberband svn path=/nixpkgs/trunk/; revision=17323
2009-09-21 11:58:30 +02:00
fftw = fftwSinglePrec;
inherit (vamp) vampSDK;
};
Add sbc
2012-07-31 23:13:53 +02:00
sbc = callPackage ../development/libraries/sbc { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
schroedinger = callPackage ../development/libraries/schroedinger { };
update liboil to 0.3.13 (and add some (new) missing deps) add schroedinger, a free codec (might be moved to its own category instead of libs) svn path=/nixpkgs/trunk/; revision=11043
2008-03-10 21:13:44 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
SDL = callPackage ../development/libraries/SDL {
I also had forgot to enable opengl support in SDL. svn path=/nixpkgs/branches/stdenv-updates/; revision=24616
2010-11-07 22:55:01 +01:00
openglSupport = mesaSupported;
beret: Fix build on darwin (close #923)
2013-09-06 03:47:49 +02:00
alsaSupport = (!stdenv.isDarwin);
Enabling x11Support in SDL. I think I had committed in error the x11Support = false at some point. svn path=/nixpkgs/branches/stdenv-updates/; revision=24613
2010-11-07 22:17:23 +01:00
x11Support = true;
beret: Fix build on darwin (close #923)
2013-09-06 03:47:49 +02:00
pulseaudioSupport = stdenv.isDarwin; # better go through ALSA
# resolve the unrecognized -fpascal-strings option error
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
* Build splashutils properly. svn path=/nixpkgs/trunk/; revision=7134
2006-11-26 00:41:53 +01:00
Add SDL variant with pulseaudio enabled, this fixes choppy sound in Kdenlive I would rather enable pulseaudio by default for SDL as it will probably fix issues for other programs too.
2014-07-27 19:35:09 +02:00
# Fixes major problems with choppy sound in MLT / Kdenlive / Shotcut
SDL_pulseaudio = SDL.override { pulseaudioSupport = true; };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
SDL_gfx = callPackage ../development/libraries/SDL_gfx { };
Add SDL_gfx. Contributed by Brian Gough <bjg@gnu.org>. svn path=/nixpkgs/trunk/; revision=21554
2010-05-02 11:27:45 +02:00
beret: Fix build on darwin (close #923)
2013-09-06 03:47:49 +02:00
SDL_image = callPackage ../development/libraries/SDL_image {
# provide an Objective-C compiler
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
};
Added libsigsegv svn path=/nixpkgs/trunk/; revision=1313
2004-08-23 11:35:36 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
SDL_mixer = callPackage ../development/libraries/SDL_mixer { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
SDL_net = callPackage ../development/libraries/SDL_net { };
forgot to update all-packages.nix svn path=/nixpkgs/trunk/; revision=10530
2008-02-06 22:26:17 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
SDL_sound = callPackage ../development/libraries/SDL_sound { };
Adding gltron. svn path=/nixpkgs/trunk/; revision=22519
2010-07-07 23:44:09 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
SDL_ttf = callPackage ../development/libraries/SDL_ttf { };
* Added libexif and the exif frontend utility. svn path=/nixpkgs/trunk/; revision=2376
2005-03-11 11:46:20 +01:00
SDL2: add release candidate The tarball is not marked as such, but current 2.0.0 version is still a release candidate for SDL2.
2013-07-02 23:06:05 +02:00
SDL2 = callPackage ../development/libraries/SDL2 {
openglSupport = mesaSupported;
alsaSupport = true;
x11Support = true;
pulseaudioSupport = false; # better go through ALSA
};
Add SDL2_image and SDL2_mixer, release candidate.
2013-07-04 19:59:43 +02:00
SDL2_image = callPackage ../development/libraries/SDL2_image { };
SDL2_mixer = callPackage ../development/libraries/SDL2_mixer { };
Add SDL2_net v2.0.0
2014-08-03 19:49:32 +02:00
SDL2_net = callPackage ../development/libraries/SDL2_net { };
Add SDL2_gfx (svn version) There is no package yet, adding latest revision.
2013-07-06 08:40:50 +02:00
SDL2_gfx = callPackage ../development/libraries/SDL2_gfx { };
Adding lv2 support LV2 is a portable plugin standard for audio systems, similar in scope to LADSPA, VST, AU, and others. The Calf audio plugin pack uses LV2 and Ardour3 has also been updated to support LV2 Plugins
2012-07-05 23:29:45 +02:00
serd = callPackage ../development/libraries/serd {};
icedtea: Remove It has apparently never worked. Also drop xerces and xalan, which were only used by icedtea.
2014-01-03 15:55:27 +01:00
Re-add HTTP/HTTPS support back to Subversion by adding serf. Tested.
2013-12-30 20:32:53 +01:00
serf = callPackage ../development/libraries/serf {};
all-packages.nix: strip trailing whitespace
2012-07-10 15:57:56 +02:00
TeXLive: update to 2012 snapshot from Debian
2012-07-13 16:18:52 +02:00
silgraphite = callPackage ../development/libraries/silgraphite {};
Updating TeXLive to 2013 using updated Debian snapshots. Kept the old hacks where they don't break the build in case they things they fix are still relevant. I checked that the upgrade doesn't break: 1) Asymptote and EProver builds. 2) My XeLaTeX demo from configurations/ repository. 3) Some of my own files. The upgrade fixes problems with simultaneous use of 3D and LaTeX labels in Asymptote. Please provide a test that worked previously and is broken now if you need to revert this update or its parts.
2013-10-14 08:36:39 +02:00
graphite2 = callPackage ../development/libraries/silgraphite/graphite2.nix {};
TeXLive: update to 2012 snapshot from Debian
2012-07-13 16:18:52 +02:00
simgear: fix via update
2013-02-23 20:10:15 +01:00
simgear = callPackage ../development/libraries/simgear { };
Adding OpenSceneGraph and SimGear svn path=/nixpkgs/trunk/; revision=26769
2011-04-09 18:43:00 +02:00
Getting mars to build. Somehow the fetchsvn in sfml_svn did not work anymore. svn path=/nixpkgs/trunk/; revision=27037
2011-04-28 22:50:12 +02:00
sfml_git = callPackage ../development/libraries/sfml { };
development/libraries/sfml: New nixpkg. svn path=/nixpkgs/trunk/; revision=26433
2011-03-20 19:21:37 +01:00
skalibs: new package Skalibs is a set of general-purpose C programming libraries used for building all software at skarnet.org.
2014-08-23 06:22:55 +02:00
skalibs = callPackage ../development/libraries/skalibs { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
slang = callPackage ../development/libraries/slang { };
* Added sqlite, a "zero administration" database; I like the sound of that ;-) svn path=/nixpkgs/trunk/; revision=2377
2005-03-11 11:55:21 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
slibGuile = callPackage ../development/libraries/slib {
all-packages.nix: build slibGuile with guile version 1.8 rather than 2.0 The guile 2.0 build of slib generates plenty of errors. svn path=/nixpkgs/trunk/; revision=27684
2011-07-09 14:11:36 +02:00
scheme = guile_1_8;
slibGuile: fix build via using older texinfo
2013-08-29 14:59:25 +02:00
texinfo = texinfo4; # otherwise erros: must be after `@defun' to use `@defunx'
Add SLIB, a portable Scheme library. svn path=/nixpkgs/trunk/; revision=17546
2009-09-30 15:10:58 +02:00
};
Making btanks work (and adding smpeg). svn path=/nixpkgs/trunk/; revision=26585
2011-03-28 20:58:49 +02:00
smpeg = callPackage ../development/libraries/smpeg { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
snack = callPackage ../development/libraries/snack {
added wavesurfer (sound analysis tool) and its dependency snack (tcl /python sound tool library) svn path=/nixpkgs/trunk/; revision=12904
2008-09-24 02:42:06 +02:00
# optional
};
Adding snappy 1.1.0
2013-02-18 22:12:11 +01:00
snappy = callPackage ../development/libraries/snappy { };
Add Sodium cryptography library
2013-03-07 07:59:03 +01:00
sodium = callPackage ../development/libraries/sodium {};
Batch update telepathy-related packages Some of these packages need glib-2.30.x, so I commit it to this branch. Add sofia-sip and telepathy-rakia. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33475
2012-03-29 18:33:32 +02:00
sofia_sip = callPackage ../development/libraries/sofia-sip { };
Soprano: revert clucene update because it isn't found by the build system
2013-07-29 11:13:58 +02:00
soprano = callPackage ../development/libraries/soprano { };
Move soprano to top-level namespace svn path=/nixpkgs/trunk/; revision=29513
2011-09-27 17:40:40 +02:00
Drop soqt and paraview/Qt-4.7 Hydra built these packages with qt-4.8. svn path=/nixpkgs/trunk/; revision=32474
2012-02-22 16:02:21 +01:00
soqt = callPackage ../development/libraries/soqt { };
Adding xercesc, the references to coin3d and soqt, and trying to add freecad (that still does not build). svn path=/nixpkgs/trunk/; revision=26135
2011-03-02 18:18:30 +01:00
Adding lv2 support LV2 is a portable plugin standard for audio systems, similar in scope to LADSPA, VST, AU, and others. The Calf audio plugin pack uses LV2 and Ardour3 has also been updated to support LV2 Plugins
2012-07-05 23:29:45 +02:00
sord = callPackage ../development/libraries/sord {};
Added BareSIP
2012-09-24 19:02:19 +02:00
spandsp = callPackage ../development/libraries/spandsp {};
Trying to add mumble. It still does not build. svn path=/nixpkgs/trunk/; revision=25890
2011-02-10 20:23:27 +01:00
speechd = callPackage ../development/libraries/speechd { };
Update Lazarus svn path=/nixpkgs/trunk/; revision=27302
2011-05-25 11:04:54 +02:00
speech_tools = callPackage ../development/libraries/speech-tools {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
speex = callPackage ../development/libraries/speex { };
whoops, add libgcrypt and libotr here too svn path=/nixpkgs/trunk/; revision=9143
2007-08-16 23:45:10 +02:00
Add the sphinxbase library svn path=/nixpkgs/trunk/; revision=26684
2011-04-04 20:50:23 +02:00
sphinxbase = callPackage ../development/libraries/sphinxbase { };
Added Sphinx Search package
2014-07-06 14:08:39 +02:00
sphinxsearch = callPackage ../servers/search/sphinxsearch { };
add spice-0.10.1 spice is a next-generation remote desktop protocol, aimed at virtual machines. focus is not just on display/input devices, but clipboard, audio, video, opengl, smartcards, usb devices as well, no matter if the virtual machine runs locally or on a remote host. not everything is implemented yet, and I didn't enable all available features yet. Currently, spice is able to make qemu-kvm virtual machines very usable for workstation guests, with good 2d video support, clipboard sharing, full resolutions, auto-mouse-grab/ungrab, xinerama / multiple guest monitors. Good drivers for windows 7 guests are available, as well as linux Xorg drivers / agents. Basically, kvm was already the best-performing VM solution (using virtio drivers), but virtualbox, while slower, had better desktop-integration support (still wins if you want opengl). Spice fixes this, making the choice very easy.
2012-08-28 00:47:00 +02:00
spice = callPackage ../development/libraries/spice {
celt = celt_0_5_1;
inherit (xlibs) libXrandr libXfixes libXext libXrender libXinerama;
spice: upgrade to 0.12.0
2012-12-05 11:54:21 +01:00
inherit (pythonPackages) pyparsing;
add spice-0.10.1 spice is a next-generation remote desktop protocol, aimed at virtual machines. focus is not just on display/input devices, but clipboard, audio, video, opengl, smartcards, usb devices as well, no matter if the virtual machine runs locally or on a remote host. not everything is implemented yet, and I didn't enable all available features yet. Currently, spice is able to make qemu-kvm virtual machines very usable for workstation guests, with good 2d video support, clipboard sharing, full resolutions, auto-mouse-grab/ungrab, xinerama / multiple guest monitors. Good drivers for windows 7 guests are available, as well as linux Xorg drivers / agents. Basically, kvm was already the best-performing VM solution (using virtio drivers), but virtualbox, while slower, had better desktop-integration support (still wins if you want opengl). Spice fixes this, making the choice very easy.
2012-08-28 00:47:00 +02:00
};
virt-manager: Add graphical support for the Spice protocol
2014-01-10 20:43:55 +01:00
spice_gtk = callPackage ../development/libraries/spice-gtk { };
Rename spiceProtocol -> spice_protocol
2012-09-13 16:13:16 +02:00
spice_protocol = callPackage ../development/libraries/spice-protocol { };
add spice-protocol-0.10.1
2012-08-28 00:36:16 +02:00
Adding lv2 support LV2 is a portable plugin standard for audio systems, similar in scope to LADSPA, VST, AU, and others. The Calf audio plugin pack uses LV2 and Ardour3 has also been updated to support LV2 Plugins
2012-07-05 23:29:45 +02:00
sratom = callPackage ../development/libraries/audio/sratom { };
Adding Ekiga svn path=/nixpkgs/trunk/; revision=23653
2010-09-06 01:37:54 +02:00
srtp = callPackage ../development/libraries/srtp {};
Linphone 3.6.1 Lots of updates and new/old libs to get the latest linphone It segfaults on running.
2013-06-29 16:50:56 +02:00
srtp_linphone = callPackage ../development/libraries/srtp/linphone.nix { };
remove sqlite alias now there is only 1 version
2013-09-17 22:28:31 +02:00
sqlite = lowPrio (callPackage ../development/libraries/sqlite {
svn path=/nixpkgs/trunk/; revision=22826
2010-07-30 15:05:52 +02:00
readline = null;
ncurses = null;
* Mark sqlite and sqliteFull as low priority (as opposed to sqliteInteractive). svn path=/nixpkgs/trunk/; revision=34112
2012-05-15 18:08:10 +02:00
});
Added an interactive variant of sqlite3 that has readline support enabled. svn path=/nixpkgs/trunk/; revision=19823
2010-02-04 17:07:15 +01:00
pkgs/top-level/all-packages.nix: prefer sqliteInteractive in user environments, i.e. when running "nix-env -i sqlite" svn path=/nixpkgs/trunk/; revision=22944
2010-08-04 13:42:10 +02:00
sqliteInteractive = appendToName "interactive" (sqlite.override {
svn path=/nixpkgs/trunk/; revision=22826
2010-07-30 15:05:52 +02:00
inherit readline ncurses;
pkgs/top-level/all-packages.nix: prefer sqliteInteractive in user environments, i.e. when running "nix-env -i sqlite" svn path=/nixpkgs/trunk/; revision=22944
2010-08-04 13:42:10 +02:00
});
* Added ClearSilver 0.10.3. * Added SQLite 3.3. * Added PySQLite 2.2.2. * Added Trac 0.9.5. To get you started; a new project environment is created by executing: $ trac-admin /path/to/trac_project_env initenv Running the server can be done by executing: $ tracd --port 8000 /path/to/projectenv Trac is then available at http://localhost:8000/projectenv. More information available at http://www.edgewall.com/trac/. svn path=/nixpkgs/trunk/; revision=5195
2006-04-22 20:08:37 +02:00
Adding sqlcipher.
2014-07-02 11:18:27 +02:00
sqlcipher = lowPrio (callPackage ../development/libraries/sqlcipher {
readline = null;
ncurses = null;
});
newsbeuter: add expression
2013-06-02 08:27:00 +02:00
stfl = callPackage ../development/libraries/stfl {
stdenv = if stdenv.isDarwin
then overrideGCC stdenv gccApple
else stdenv;
};
stlink: new package stlink is an in-circuit debugging and programming tool for ST-Link v1 and v2 devices. It is similar to OpenOCD but just for ST-Link devices. https://github.com/texane/stlink IMPORTANT: You need permissions to access the stlink usb devices. Here are example udev rules for stlink v1 and v2 so you don't need to have root permissions (copied from <stlink>/49-stlink*.rules): SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3744", MODE:="0666", SYMLINK+="stlinkv1_%n" SUBSYSTEMS=="usb", ATTRS{idVendor}=="0483", ATTRS{idProduct}=="3748", MODE:="0666", SYMLINK+="stlinkv2_%n"
2013-02-23 12:05:22 +01:00
stlink = callPackage ../development/tools/misc/stlink { };
Add steghide to top level.
2014-02-06 12:00:41 +01:00
steghide = callPackage ../tools/security/steghide {};
stepmania: A dance (rhythm) game in the spirit of DDR.
2013-05-16 06:53:49 +02:00
stepmania = callPackage ../games/stepmania {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
stlport = callPackage ../development/libraries/stlport { };
Move stlport to the top-level. svn path=/nixpkgs/trunk/; revision=12811
2008-09-05 19:17:00 +02:00
clucene_core: upgrade some packages to clucene_core_2 on my systems, I can now override "clucene_core = clucene_core_2" globally in nixpkgs. so perhaps we can soon drop v1?
2013-06-29 11:49:46 +02:00
strigi = callPackage ../development/libraries/strigi { clucene_core = clucene_core_2; };
Move strigi outside of kde-4.x svn path=/nixpkgs/trunk/; revision=26057
2011-02-22 12:54:49 +01:00
subtitleeditor, gstreamermm: new packages
2014-05-21 20:45:58 +02:00
subtitleeditor = callPackage ../applications/video/subtitleeditor { };
Adding lv2 support LV2 is a portable plugin standard for audio systems, similar in scope to LADSPA, VST, AU, and others. The Calf audio plugin pack uses LV2 and Ardour3 has also been updated to support LV2 Plugins
2012-07-05 23:29:45 +02:00
suil = callPackage ../development/libraries/audio/suil { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
suitesparse = callPackage ../development/libraries/suitesparse { };
added qrupdate, suitesparse needed to build octave from source svn path=/nixpkgs/trunk/; revision=22867
2010-08-02 13:20:39 +02:00
Add the bspwm window manager to Nix.
2014-08-09 23:31:05 +02:00
sutils = callPackage ../tools/misc/sutils { };
added the sword framework svn path=/nixpkgs/trunk/; revision=24586
2010-11-03 21:36:36 +01:00
sword = callPackage ../development/libraries/sword { };
added eclipse 3.6.1, maven3, szip svn path=/nixpkgs/trunk/; revision=24772
2010-11-19 14:24:11 +01:00
szip = callPackage ../development/libraries/szip { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
t1lib = callPackage ../development/libraries/t1lib { };
* Added lcms, a color management system. svn path=/nixpkgs/trunk/; revision=2378
2005-03-11 12:02:31 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
taglib = callPackage ../development/libraries/taglib { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=24045
2010-10-04 11:49:25 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
taglib_extras = callPackage ../development/libraries/taglib-extras { };
- Added Qt script generator package (dependency for Amarok) - Added taglib-extras package (dependency for Amarok) - Upgraded Amarok to 2.1.1 svn path=/nixpkgs/trunk/; revision=17045
2009-09-11 14:05:23 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
talloc = callPackage ../development/libraries/talloc { };
talloc 2.0.1 svn path=/nixpkgs/trunk/; revision=22009
2010-05-27 21:33:28 +02:00
Add tclap (required for new hugin) svn path=/nixpkgs/trunk/; revision=32169
2012-02-10 11:13:34 +01:00
tclap = callPackage ../development/libraries/tclap {};
tclgpg: New package, pre-1.0 release. The library has not been released so far, but it is used by Tkabber and some other software in Tcl (none of them is in nixpkgs so far). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-09-09 05:20:31 +02:00
tclgpg = callPackage ../development/libraries/tclgpg { };
Add tkabber dependency tcllib v1.14.
2012-06-04 20:07:58 +02:00
tcllib = callPackage ../development/libraries/tcllib { };
Add tkabber dependency tcltls v1.6.
2012-06-04 20:08:56 +02:00
tcltls = callPackage ../development/libraries/tcltls { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tdb = callPackage ../development/libraries/tdb { };
TDB, the trivial database. svn path=/nixpkgs/trunk/; revision=19895
2010-02-10 12:28:18 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tecla = callPackage ../development/libraries/tecla { };
maude, tecla, buddy: new packages Maude is a high-level specification language. Buddy and libtecla are required to build Maude. svn path=/nixpkgs/trunk/; revision=12358
2008-07-15 11:58:30 +02:00
Move dev/libs/telepathy-* to a subdir svn path=/nixpkgs/trunk/; revision=33079
2012-03-14 20:35:41 +01:00
telepathy_glib = callPackage ../development/libraries/telepathy/glib { };
Added some telepathy+tapioca stuff. svn path=/nixpkgs/trunk/; revision=10360
2008-01-28 20:49:44 +01:00
Add telepathy-farstream svn path=/nixpkgs/trunk/; revision=33128
2012-03-15 22:50:02 +01:00
telepathy_farstream = callPackage ../development/libraries/telepathy/farstream {};
Move dev/libs/telepathy-* to a subdir svn path=/nixpkgs/trunk/; revision=33079
2012-03-14 20:35:41 +01:00
telepathy_qt = callPackage ../development/libraries/telepathy/qt { };
Added some telepathy+tapioca stuff. svn path=/nixpkgs/trunk/; revision=10360
2008-01-28 20:49:44 +01:00
Adding Apache Thrift.
2013-12-13 11:16:40 +01:00
thrift = callPackage ../development/libraries/thrift { };
Added TinyXML-2.6.2.
2012-12-31 11:13:55 +01:00
tinyxml = tinyxml2;
all-packages.nix: strip trailing whitespace
2013-01-04 20:55:41 +01:00
Added TinyXML-2.6.2.
2012-12-31 11:13:55 +01:00
tinyxml2 = callPackage ../development/libraries/tinyxml/2.6.2.nix { };
tk: update to 8.5.15, enable xft support
2014-01-13 13:08:20 +01:00
tk = callPackage ../development/libraries/tk { };
Added gdmap, changed builder-defs to use derivation attribute on propagatedBuildInputs, manually fixed Xorg expression problem for Compiz, various fixes. svn path=/nixpkgs/trunk/; revision=9812
2007-12-01 17:20:23 +01:00
TNT library: packaged svn path=/nixpkgs/trunk/; revision=24276
2010-10-14 13:53:53 +02:00
tnt = callPackage ../development/libraries/tnt { };
Add Tokyo Cabinet, a key-value database that performs better. svn path=/nixpkgs/trunk/; revision=24548
2010-10-30 23:44:29 +02:00
tokyocabinet = callPackage ../development/libraries/tokyo-cabinet { };
Add Tokyo-Tyrant, the network interface to Tokyo-Cabinet. svn path=/nixpkgs/trunk/; revision=30728
2011-12-04 23:02:55 +01:00
tokyotyrant = callPackage ../development/libraries/tokyo-tyrant { };
Add Tokyo Cabinet, a key-value database that performs better. svn path=/nixpkgs/trunk/; revision=24548
2010-10-30 23:44:29 +02:00
Adding GMU, a music player for small portable devices, written in SDL. svn path=/nixpkgs/trunk/; revision=26266
2011-03-10 23:20:35 +01:00
tremor = callPackage ../development/libraries/tremor { };
Add unicap svn path=/nixpkgs/trunk/; revision=24271
2010-10-14 12:10:45 +02:00
unicap = callPackage ../development/libraries/unicap {};
Torsocks is not compatible with certain apps like Kopete. Will integrate both in NixOS. Revert "removing tsocks as it has been replaced by torsocks." This reverts commit f947527f184446572ad3e36c4423b23e797aeb5a.
2013-01-15 06:13:30 +01:00
tsocks = callPackage ../development/libraries/tsocks { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
unixODBC = callPackage ../development/libraries/unixODBC { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
added unixODBCDrivers expression containing unixODBC Postgres connector driver integrating prior pkgs/development/libraries/mysql-connector-odbc/default.nix driver Also provides ini strings for assembling /etc/odbcinst.ini svn path=/nixpkgs/trunk/; revision=12044
2008-06-12 01:03:30 +02:00
unixODBCDrivers = recurseIntoAttrs (import ../development/libraries/unixODBCDrivers {
inherit fetchurl stdenv unixODBC glibc libtool openssl zlib;
* unixODBCDrivers needs sqlite. svn path=/nixpkgs/trunk/; revision=12072
2008-06-13 11:44:43 +02:00
inherit postgresql mysql sqlite;
added unixODBCDrivers expression containing unixODBC Postgres connector driver integrating prior pkgs/development/libraries/mysql-connector-odbc/default.nix driver Also provides ini strings for assembling /etc/odbcinst.ini svn path=/nixpkgs/trunk/; revision=12044
2008-06-12 01:03:30 +02:00
});
URT library: packaged svn path=/nixpkgs/trunk/; revision=24278
2010-10-14 13:54:06 +02:00
urt = callPackage ../development/libraries/urt { };
ustr: cleanup svn path=/nixpkgs/trunk/; revision=26556
2011-03-28 01:31:31 +02:00
ustr = callPackage ../development/libraries/ustr { };
ustr: packaged svn path=/nixpkgs/trunk/; revision=26540
2011-03-27 06:46:05 +02:00
virt-manager: update to 1.0.1, fix & update dependencies, gtk3 support - Vte, add gtk3 support, enable introspection, update to 0.35.90 - Spice-gtk, add gtk3 support - gtk-vnc, add gtk3 support - Add libvirt-glib (thanks @bjornfor) - Add usbredir - qemu, enable usbredir - spice-gtk, enable usbredir - virt-manager, update to 1.0.1 [Bjørn: * Set namePrefix = "" to preserve package name "virt-manager" (instead of "python2.7-virt-manager") * Add dconf to GIO_EXTRA_MODULES to get persistent settings in virt-manager. Without it: GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. * Add ${gtk3}/share to XDG_DATA_DIRS to unbreak "Take Screenshot" feature (fixes "Settings schema 'org.gtk.Settings.FileChooser' is not installed") * gtk-vnc: don't pull "pkgs" attrset for optionalString, use stdenv.lib.optionalString instead. ]
2014-03-23 18:12:07 +01:00
usbredir = callPackage ../development/libraries/usbredir {
libusb = libusb1;
};
Adding GNU SIP Witch. svn path=/nixpkgs/trunk/; revision=25634
2011-01-19 22:17:05 +01:00
ucommon = callPackage ../development/libraries/ucommon { };
Move non-java libraries to "DEVELOPMENT / LIBRARIES" section
2014-05-11 23:08:47 +02:00
v8 = callPackage ../development/libraries/v8 {
inherit (pythonPackages) gyp;
};
Adding the vaapi Intel driver. I also renamed the vdpau driver to 'vaapiDriver' in all-packages. I think it's a better name.
2013-01-29 00:31:35 +01:00
vaapiIntel = callPackage ../development/libraries/vaapi-intel { };
vaapiVdpau = callPackage ../development/libraries/vaapi-vdpau { };
Updates related to VAAPI/VDPAU Making ffmpeg link to libva. Add the vdpau driver for vaapi.
2013-01-29 00:26:20 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vamp = callPackage ../development/libraries/audio/vamp { };
adding vamp sdk and rubberband svn path=/nixpkgs/trunk/; revision=17323
2009-09-21 11:58:30 +02:00
Add GNU vcdimager svn path=/nixpkgs/trunk/; revision=31449
2012-01-09 11:25:42 +01:00
vcdimager = callPackage ../development/libraries/vcdimager { };
vigra-1.8.0 svn path=/nixpkgs/trunk/; revision=32346
2012-02-17 14:03:41 +01:00
vigra = callPackage ../development/libraries/vigra {
inherit (pkgs.pythonPackages) numpy;
};
adding vamp sdk and rubberband svn path=/nixpkgs/trunk/; revision=17323
2009-09-21 11:58:30 +02:00
Add package for vlock from Debian mirror. This is mainly because the original upstream URL is not available anymore. svn path=/nixpkgs/trunk/; revision=34442
2012-06-11 09:16:11 +02:00
vlock = callPackage ../misc/screensavers/vlock { };
Adding vmime svn path=/nixpkgs/trunk/; revision=25783
2011-02-06 16:27:14 +01:00
vmime = callPackage ../development/libraries/vmime { };
Add VRPN. svn path=/nixpkgs/trunk/; revision=33640
2012-04-06 10:32:50 +02:00
vrpn = callPackage ../development/libraries/vrpn { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vtk = callPackage ../development/libraries/vtk { };
Adding vtk-5.2.1, The Visualization Toolkit. svn path=/nixpkgs/trunk/; revision=14006
2009-02-08 17:27:57 +01:00
vtk: Use the Qt libraries as an argument instead of a boolean To prevent multiple Qt libraries when developing with a custom one, the Qt support can now be activated by directly supplying the Qt libraries as an argument (qtLib). qtSDK and qtFull users/developers now just have to define an override such as the following one in order to use it inside their development environment: vtk.override { qtLib = qt4SDK; }; The previous behavior is still the same for vtk and vtkWithQt4 end-users. Change-Id: I517762d4ff7de46d32cc46e6e725fd62737caa52
2013-10-28 09:56:19 +01:00
vtkWithQt4 = vtk.override { qtLib = qt4; };
vtk: latest version + useQt4 option - Updated vtk to v5.10.0 (latest tagged release) - Introduced a useQt4 option which allows to set the VTK_USE_QT option to true - Added a package named vtkWithQt4 in the all-packages list Signed-off-by: Baptist BENOIST <return_0@live.com>
2012-10-16 23:19:59 +02:00
Fixing the vxl build. svn path=/nixpkgs/trunk/; revision=32848
2012-03-07 11:16:53 +01:00
vxl = callPackage ../development/libraries/vxl {
libpng = libpng12;
};
Committing Lluís Batlle's submissions from mailing list posting <45219fb00901110456i6f21db35tbd1894eaea2146ff@mail.gmail.com>: * nixpkgs-ccrypt-1.7-new.patch * nixpkgs-cmake-add-ccmake.patch * nixpkgs-cpufrequtils-005-new.patch * nixpkgs-dwm-5.1-fix.patch * nixpkgs-freeimage-3.11.0-new.patch * nixpkgs-proxychains-3.1-new.patch * nixpkgs-psi-to-0.12.patch * nixpkgs-skype-to-2.0.0.72.patch * nixpkgs-truecrypt-6.1a-fix.patch * nixpkgs-vxl-1.11.0-new.patch * nixpkgs-xkb-popular-esperanto-symbols.patch * nixpkgs-xorg-via-video-fix.patch svn path=/nixpkgs/trunk/; revision=13751
2009-01-12 22:12:07 +01:00
Add wayland library
2013-02-17 03:16:00 +01:00
wayland = callPackage ../development/libraries/wayland { };
get rid of old webkit and webkit_gtk2 packages
2014-03-30 03:02:07 +02:00
webkit = webkitgtk;
Porting a fix from nixpkgs trunk - vimprobable2 now builds (against obsolete WebKit/GTK2) svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33467
2012-03-29 12:30:47 +02:00
add webkitgtk 2.2.3 With minor changes from @vcunat, see #1197.
2013-12-05 16:24:05 +01:00
webkitgtk = callPackage ../development/libraries/webkitgtk {
harfbuzz = harfbuzz.override {
withIcu = true;
Porting a fix from nixpkgs trunk - vimprobable2 now builds (against obsolete WebKit/GTK2) svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33467
2012-03-29 12:30:47 +02:00
};
webkitgtk: update to 2.2.4, enable html5 video support
2014-01-23 01:12:36 +01:00
gst-plugins-base = gst_all_1.gst-plugins-base;
add webkitgtk 2.2.3 With minor changes from @vcunat, see #1197.
2013-12-05 16:24:05 +01:00
};
Porting a fix from nixpkgs trunk - vimprobable2 now builds (against obsolete WebKit/GTK2) svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33467
2012-03-29 12:30:47 +02:00
webkitgtk: add gtk2 version
2014-03-27 09:11:56 +01:00
webkitgtk2 = webkitgtk.override {
withGtk2 = true;
enableIntrospection = false;
};
wildmidi: new package WildMIDI is a simple software midi player which has a core softsynth library that can be use with other applications. I have tested the wildmidi executable with a MIDI file. It works.
2013-05-18 20:13:32 +02:00
wildmidi = callPackage ../development/libraries/wildmidi { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wvstreams = callPackage ../development/libraries/wvstreams { };
adding wvdial, wvstreams, usb_modeswitch svn path=/nixpkgs/trunk/; revision=21131
2010-04-16 17:56:28 +02:00
Setting wxGTK to use the old gtk libs. Until wxGTK 2.8.11 they will not fix a symbol clash with glib 2.21. So we keep with glib 2.20. I also changed the default wxGTK from 2.6 to 2.8, caring so no hash is changed due to this change. Some packages using 2.6 may well build with 2.8, so we can try updating them for another commit. svn path=/nixpkgs/trunk/; revision=18133
2009-11-05 14:29:52 +01:00
wxGTK = wxGTK28;
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
wxGTK28 = callPackage ../development/libraries/wxGTK-2.8 {
wxGTK-2.x: enable support for media control svn path=/nixpkgs/trunk/; revision=31516
2012-01-13 11:32:02 +01:00
inherit (gnome) GConf;
all-packages.nix: use mesaPlatforms list to determine whether wxGTX should be built with OpenGL support or not svn path=/nixpkgs/trunk/; revision=33070
2012-03-14 18:45:13 +01:00
withMesa = lib.elem system lib.platforms.mesaPlatforms;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
wxGTK-2.9: updated the development version of wxGTK to 2.9.3 I deleted older snapshots because my attempts to use 2.9.0 or 2.9.1 ran into problems with our recent version of libpng. The 2.9.3 version seems to work fine, though. If you still need the older versions, please feel free to reinstate them. svn path=/nixpkgs/trunk/; revision=33812
2012-04-17 15:56:30 +02:00
wxGTK29 = callPackage ../development/libraries/wxGTK-2.9/default.nix {
wxGTK-2.x: enable support for media control svn path=/nixpkgs/trunk/; revision=31516
2012-01-13 11:32:02 +01:00
inherit (gnome) GConf;
all-packages.nix: use mesaPlatforms list to determine whether wxGTX should be built with OpenGL support or not svn path=/nixpkgs/trunk/; revision=33070
2012-03-14 18:45:13 +01:00
withMesa = lib.elem system lib.platforms.mesaPlatforms;
wxGTK29: fix build on darwin * use clang to compile * add configure flags to enable building for 64-bit * add setFile to build inputs
2013-07-04 00:49:30 +02:00
# use for Objective-C++ compiler
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
Bitcoin. svn path=/nixpkgs/trunk/; revision=26544
2011-03-27 08:44:34 +02:00
};
Adding wxWidgets 3.0.0
2013-12-30 17:03:23 +01:00
wxGTK30 = callPackage ../development/libraries/wxGTK-3.0/default.nix {
inherit (gnome) GConf;
withMesa = lib.elem system lib.platforms.mesaPlatforms;
# use for Objective-C++ compiler
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wtk = callPackage ../development/libraries/wtk { };
Adding the Sun Wireless ToolKit for i686-linux at least. svn path=/nixpkgs/trunk/; revision=14666
2009-03-23 21:36:48 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
x264 = callPackage ../development/libraries/x264 { };
x264 codec lib added svn path=/nixpkgs/trunk/; revision=11876
2008-05-22 02:18:45 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xapian = callPackage ../development/libraries/xapian { };
adding xapian and xapian-bindings svn path=/nixpkgs/trunk/; revision=16788
2009-08-20 22:18:58 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xapianBindings = callPackage ../development/libraries/xapian/bindings { # TODO perl php Java, tcl, C#, python
adding xapian and xapian-bindings svn path=/nixpkgs/trunk/; revision=16788
2009-08-20 22:18:58 +02:00
};
renamed current xapian/xapianBindings to xapian10/xapianBindings10 svn path=/nixpkgs/trunk/; revision=26979
2011-04-26 22:57:11 +02:00
xapian10 = callPackage ../development/libraries/xapian/1.0.x.nix { };
adding xapian and xapian-bindings svn path=/nixpkgs/trunk/; revision=16788
2009-08-20 22:18:58 +02:00
renamed current xapian/xapianBindings to xapian10/xapianBindings10 svn path=/nixpkgs/trunk/; revision=26979
2011-04-26 22:57:11 +02:00
xapianBindings10 = callPackage ../development/libraries/xapian/bindings/1.0.x.nix { # TODO perl php Java, tcl, C#, python
adding xapian and xapian-bindings svn path=/nixpkgs/trunk/; revision=16788
2009-08-20 22:18:58 +02:00
};
Making the current versions of flex/bison the default. Evaluation test passes. Please explicitly pass older versions to any package that can be adversely affected by too-fresh versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=25086
2010-12-12 22:48:29 +01:00
Xaw3d = callPackage ../development/libraries/Xaw3d { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Add xbase svn path=/nixpkgs/trunk/; revision=23897
2010-09-22 20:04:34 +02:00
xbase = callPackage ../development/libraries/xbase { };
awesome-3-5: add expression and nixos module
2013-11-13 03:34:49 +01:00
xcb-util-cursor = callPackage ../development/libraries/xcb-util-cursor { };
all-packages.nix: strip trailing whitespace
2014-08-20 11:57:56 +02:00
Add the bspwm window manager to Nix.
2014-08-09 23:31:05 +02:00
xdo = callPackage ../tools/misc/xdo { };
awesome-3-5: add expression and nixos module
2013-11-13 03:34:49 +01:00
xinelib: pin to ffmpeg 1
2013-12-16 14:38:19 +01:00
xineLib = callPackage ../development/libraries/xine-lib {
ffmpeg = ffmpeg_1;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xautolock = callPackage ../misc/screensavers/xautolock { };
Added xautolock 2.1. Xautolock can be used to fire up a screen saver like xautolock after a certain period of inactivity. The tool probably doesn't belong into misc/screensavers, but I had no better idea. svn path=/nixpkgs/trunk/; revision=12305
2008-07-07 13:54:25 +02:00
Adding xercesc, the references to coin3d and soqt, and trying to add freecad (that still does not build). svn path=/nixpkgs/trunk/; revision=26135
2011-03-02 18:18:30 +01:00
xercesc = callPackage ../development/libraries/xercesc {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
xlibsWrapper = callPackage ../development/libraries/xlibs-wrapper {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
packages = [
freetype fontconfig xlibs.xproto xlibs.libX11 xlibs.libXt
xlibs.libXft xlibs.libXext xlibs.libSM xlibs.libICE
xlibs.xextproto
];
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Fix cmake-2.6.4 build (add xmlrpc-c) svn path=/nixpkgs/trunk/; revision=32505
2012-02-23 12:27:47 +01:00
xmlrpc_c = callPackage ../development/libraries/xmlrpc-c { };
Move non-java libraries to "DEVELOPMENT / LIBRARIES" section
2014-05-11 23:08:47 +02:00
xmlsec = callPackage ../development/libraries/xmlsec { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xvidcore = callPackage ../development/libraries/xvidcore { };
Adding xvid, to ffmpeg and mplayer. svn path=/nixpkgs/trunk/; revision=21469
2010-04-30 23:47:09 +02:00
Add library: xylib
2014-08-14 01:13:12 +02:00
xylib = callPackage ../development/libraries/xylib { };
Add yaml - Yet Another JSON Library svn path=/nixpkgs/trunk/; revision=29837
2011-10-14 16:00:50 +02:00
yajl = callPackage ../development/libraries/yajl { };
All-packages changes for last commits svn path=/nixpkgs/trunk/; revision=15561
2009-05-12 06:28:30 +02:00
zangband = builderDefsPackage (import ../games/zangband) {
* Better not use stdenv.coreutils, since not every stdenv has a coreutils. svn path=/nixpkgs/trunk/; revision=15564
2009-05-12 11:45:24 +02:00
inherit ncurses flex bison autoconf automake m4 coreutils;
All-packages changes for last commits svn path=/nixpkgs/trunk/; revision=15561
2009-05-12 06:28:30 +02:00
};
zeitgeist: new package Zeitgeist is a service which logs the users's activities and events https://launchpad.net/zeitgeist
2014-05-02 17:39:18 +02:00
zeitgeist = callPackage ../development/libraries/zeitgeist { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
zlib = callPackage ../development/libraries/zlib {
* curl: build with OpenSSL (https) support by default. * Some fetchurl-related refactoring. The `realCurl' attribute is gone, `curl' is the real thing. To prevent an infinite recursion in `fetchurl' (because it depends on curl and building curl needs fetchurl), curl and its dependencies (openssl, zlib, perl) use `fetchurlBoot', which is the fetchurl used by the previous bootstrap phase (e.g. the statically linked version of curl for stdenv-linux). So as a result you can use https:// urls almost everywhere. There's also some hackery to prevent a different curl from being built in every stdenv-linux bootstrap phase (namely the stdenv.fetchurl attribute which allows fetchurl to be overriden everywhere). svn path=/nixpkgs/trunk/; revision=11905
2008-05-27 09:49:55 +02:00
fetchurl = fetchurlBoot;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
* Added libgphoto2. svn path=/nixpkgs/trunk/; revision=2379
2005-03-11 12:08:38 +01:00
Minor cleanup
2012-11-29 14:40:25 +01:00
zlibStatic = lowPrio (appendToName "static" (callPackage ../development/libraries/zlib {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
static = true;
}));
* Added `zapping', a TV viewer application. It depends on Gnome, so lots of packages are needed. svn path=/nixpkgs/trunk/; revision=681
2004-01-21 10:34:19 +01:00
zeromq: add version 3.x
2012-10-24 18:17:27 +02:00
zeromq2 = callPackage ../development/libraries/zeromq/2.x.nix {};
zeromq3 = callPackage ../development/libraries/zeromq/3.x.nix {};
add zeromq4 and zeromq4-haskell
2014-05-01 13:52:21 +02:00
zeromq4 = callPackage ../development/libraries/zeromq/4.x.nix {};
Added zeromq and haskell-zeromq-haskell. svn path=/nixpkgs/trunk/; revision=30878
2011-12-14 09:31:14 +01:00
Move non-java libraries to "DEVELOPMENT / LIBRARIES" section
2014-05-11 23:08:47 +02:00
zziplib = callPackage ../development/libraries/zziplib { };
Add a builder for Agda packages.
2014-08-31 19:40:11 +02:00
### DEVELOPMENT / LIBRARIES / AGDA
agda = callPackage ../build-support/agda {
glibcLocales = if pkgs.stdenv.isLinux then pkgs.glibcLocales else null;
extension = self : super : {};
Agda = haskellPackages.Agda;
inherit writeScriptBin;
};
Minor cleanup
2012-11-29 14:40:25 +01:00
Use agda builder for stdlib. mv to all-packages
2014-09-01 02:31:17 +02:00
AgdaStdlib = callPackage ../development/compilers/agda/stdlib.nix {
ghcWithPackages = haskellPackages.ghcWithPackages;
};
Minor cleanup
2012-11-29 14:40:25 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### DEVELOPMENT / LIBRARIES / JAVA
* Added the Cairo graphics library. * Updated GTK and friends to 2.8.x. svn path=/nixpkgs/trunk/; revision=4073
2005-10-12 13:57:24 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
atermjava = callPackage ../development/libraries/java/aterm {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
stdenv = overrideInStdenv stdenv [gnumake380];
};
* Converted more packages. svn path=/nixpkgs/trunk/; revision=488
2003-11-06 16:24:19 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
commonsFileUpload = callPackage ../development/libraries/java/jakarta-commons/file-upload { };
Add FastJar. svn path=/nixpkgs/trunk/; revision=16469
2009-07-27 12:43:20 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fastjar = callPackage ../development/tools/java/fastjar { };
Added libwmf for handling embedded graphics in .doc files. svn path=/nixpkgs/trunk/; revision=9153
2007-08-18 11:35:54 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
httpunit = callPackage ../development/libraries/java/httpunit { };
Added gwt-dragdrop library svn path=/nixpkgs/trunk/; revision=10856
2008-02-26 09:48:40 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gwtdragdrop = callPackage ../development/libraries/java/gwt-dragdrop { };
Added gwt-widgets svn path=/nixpkgs/trunk/; revision=10851
2008-02-25 13:45:17 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gwtwidgets = callPackage ../development/libraries/java/gwt-widgets { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
jakartabcel = callPackage ../development/libraries/java/jakarta-bcel {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
regexp = jakartaregexp;
};
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jakartaregexp = callPackage ../development/libraries/java/jakarta-regexp { };
* Add libxcrypt for Blowfish support in pam_unix2. svn path=/nixpkgs/trunk/; revision=7305
2006-12-11 03:35:05 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
javaCup = callPackage ../development/libraries/java/cup { };
* Some applications (notably, everything based on wxGTK) don't work yet with GTK 2.4. Fortunately, having several GTKs in parallel is no problem for Nix. svn path=/nixpkgs/trunk/; revision=915
2004-04-05 16:09:01 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
javasvn = callPackage ../development/libraries/java/javasvn { };
* Gnome terminal. svn path=/nixpkgs/trunk/; revision=8172
2007-03-05 00:37:34 +01:00
Remove obsolete JDK versions These are the JDK 5 on powerpc-linux (no longer a maintained Nixpkgs platform), JDK 1.4 (required a manual download) and JDK 5 on Linux (idem).
2012-08-22 21:24:04 +02:00
jclasslib = callPackage ../development/tools/java/jclasslib { };
* Converted GTK 1 / Sylpheed, with optional support for gdk-pixbuf. svn path=/nixpkgs/trunk/; revision=490
2003-11-06 17:28:57 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jdom = callPackage ../development/libraries/java/jdom { };
add wmii window manager + all dependencies. Interesting excercise... svn path=/nixpkgs/trunk/; revision=8338
2007-03-19 00:58:22 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jflex = callPackage ../development/libraries/java/jflex { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
jjtraveler = callPackage ../development/libraries/java/jjtraveler {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
stdenv = overrideInStdenv stdenv [gnumake380];
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Change junit to actually compile from source rather than download binaries
2014-08-10 02:50:16 +02:00
junit = callPackage ../development/libraries/java/junit { antBuild = releaseTools.antBuild; };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
junixsocket: Add
2014-01-25 02:28:19 +01:00
junixsocket = callPackage ../development/libraries/java/junixsocket { };
Add jzmq package.
2013-02-06 13:24:57 +01:00
jzmq = callPackage ../development/libraries/java/jzmq { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lucene = callPackage ../development/libraries/java/lucene { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mockobjects = callPackage ../development/libraries/java/mockobjects { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
saxon = callPackage ../development/libraries/java/saxon { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
saxonb = callPackage ../development/libraries/java/saxon/default8.nix { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
sharedobjects = callPackage ../development/libraries/java/shared-objects {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
stdenv = overrideInStdenv stdenv [gnumake380];
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
smack = callPackage ../development/libraries/java/smack { };
Added smack library svn path=/nixpkgs/trunk/; revision=10857
2008-02-26 10:07:12 +01:00
swt: updated to version 3.7.2-201202080800 Committed on behalf of "Corey O'Connor" <coreyoconnor@gmail.com> via <CANTmfBTtRRQoc9UXCmNC8z1BNhnmiQZNVhB1TNK-PUGV-9om_w@mail.gmail.com>. svn path=/nixpkgs/trunk/; revision=32952
2012-03-09 14:24:16 +01:00
swt = callPackage ../development/libraries/java/swt {
inherit (gnome) libsoup;
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Added jQuery UI. svn path=/nixpkgs/trunk/; revision=25465
2011-01-09 16:43:53 +01:00
### DEVELOPMENT / LIBRARIES / JAVASCRIPT
jquery_ui = callPackage ../development/libraries/javascript/jquery-ui { };
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
Add expression for the YUI compressor
2014-05-27 11:13:07 +02:00
yuicompressor = callPackage ../development/tools/yuicompressor { };
icedtea: Remove It has apparently never worked. Also drop xerces and xalan, which were only used by icedtea.
2014-01-03 15:55:27 +01:00
Adding ASDF package definition system for Common Lisp
2013-10-13 08:40:25 +02:00
### DEVELOPMENT / LISP MODULES
LISP: Don't build/download texlive for every lispPackage. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-12-12 18:49:14 +01:00
asdf = callPackage ../development/lisp-modules/asdf {
texLive = null;
};
icedtea: Remove It has apparently never worked. Also drop xerces and xalan, which were only used by icedtea.
2014-01-03 15:55:27 +01:00
Adding a Common Lisp wrapper. Features: + configurable via environment variables + can skip the actual launching of the lisp implementation (source it with NIX_LISP_SKIP_CODE=1 to get all the settings) + currently supports SBCL, CLisp, ECL + determines lisp implementation from NIX_LISP_COMMAND variable or from buildInputs + sets ASDF search path for packages using buildInputs
2013-10-13 08:45:07 +02:00
clwrapperFunction = callPackage ../development/lisp-modules/clwrapper;
icedtea: Remove It has apparently never worked. Also drop xerces and xalan, which were only used by icedtea.
2014-01-03 15:55:27 +01:00
wrapLisp = lisp: clwrapperFunction { inherit lisp; };
lispPackagesFor = clwrapper: callPackage ../development/lisp-modules/lisp-packages.nix {
Adding lisp-packages subset. Adding a few test packages without dependencies.
2013-10-13 08:57:30 +02:00
inherit clwrapper;
};
icedtea: Remove It has apparently never worked. Also drop xerces and xalan, which were only used by icedtea.
2014-01-03 15:55:27 +01:00
Adding lisp-packages subset. Adding a few test packages without dependencies.
2013-10-13 08:57:30 +02:00
lispPackagesClisp = lispPackagesFor (wrapLisp clisp);
lispPackagesSBCL = lispPackagesFor (wrapLisp sbcl);
lispPackages = recurseIntoAttrs lispPackagesSBCL;
Use systemd instead of udev, and don't use consolekit
2012-11-06 13:01:44 +01:00
icedtea: Remove It has apparently never worked. Also drop xerces and xalan, which were only used by icedtea.
2014-01-03 15:55:27 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### DEVELOPMENT / PERL MODULES
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* A function "buildPerlPackage" to replace all those "import ../development/perl-modules/generic perl" incantations. svn path=/nixpkgs/trunk/; revision=13387
2008-11-24 11:24:51 +01:00
buildPerlPackage = import ../development/perl-modules/generic perl;
Added maybench, an automated benchmarking tool. The tool depends on benchpress, a Haskell library for timed command execution. For starters, the expression lives in development/libraries/haskell/maybench. It doesn't really belong there because, though, because, technically, it's an executable, not a library. If someone has a better idea, please feel free to move it. svn path=/nixpkgs/trunk/; revision=12761
2008-08-29 11:05:49 +02:00
* Make Perl package show up in nix-env. svn path=/nixpkgs/trunk/; revision=15174
2009-04-20 14:24:13 +02:00
perlPackages = recurseIntoAttrs (import ./perl-packages.nix {
* Move all the Perl packages out of all-packages.nix into a separate file, perl-packages.nix. svn path=/nixpkgs/trunk/; revision=15171
2009-04-20 14:08:09 +02:00
inherit pkgs;
Remove uses of __overrides feature In addition to replacing use of a feature with IMO confusing semantics, this will also let us cleanly separate out all-packages.nix into category-specific files without changing the structure of the pkgs attrset. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-30 17:04:45 +01:00
overrides = (config.perlPackageOverrides or (p: {})) pkgs;
* Make Perl package show up in nix-env. svn path=/nixpkgs/trunk/; revision=15174
2009-04-20 14:24:13 +02:00
});
Added maybench, an automated benchmarking tool. The tool depends on benchpress, a Haskell library for timed command execution. For starters, the expression lives in development/libraries/haskell/maybench. It doesn't really belong there because, though, because, technically, it's an executable, not a library. If someone has a better idea, please feel free to move it. svn path=/nixpkgs/trunk/; revision=12761
2008-08-29 11:05:49 +02:00
slic3r: new package Slic3r is a G-code generator for 3D printers. - Math-Clipper and Boost-Geometry-Utils have been bumped to satisfy Slic3r. - Slic3r has problems with perl 5.16 due to a locale issue (comma vs period in floating point numbers). So we use perl 5.14. - The tests fail, so we skip them. According to the author of Slic3r, that should be safe: "Tests failed because of a typo when the 0.9.10b tag was applied. You can safely ignore the test results, Slic3r will work." See https://github.com/alexrj/Slic3r/issues/1303 For reference, the errors look like this: Use of uninitialized value $deg in numeric eq (==) at /tmp/nix-build-perl-slic3r-0.9.10b.drv-0/git-export/t/../lib/Slic3r/TriangleMesh.pm line 328. # Looks like your test exited with 255 before it could output anything.
2013-04-28 12:59:00 +02:00
perl514Packages = import ./perl-packages.nix {
pkgs = pkgs // {
perl = perl514;
buildPerlPackage = import ../development/perl-modules/generic perl514;
};
Remove uses of __overrides feature In addition to replacing use of a feature with IMO confusing semantics, this will also let us cleanly separate out all-packages.nix into category-specific files without changing the structure of the pkgs attrset. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-30 17:04:45 +01:00
overrides = (config.perl514PackageOverrides or (p: {})) pkgs;
slic3r: new package Slic3r is a G-code generator for 3D printers. - Math-Clipper and Boost-Geometry-Utils have been bumped to satisfy Slic3r. - Slic3r has problems with perl 5.16 due to a locale issue (comma vs period in floating point numbers). So we use perl 5.14. - The tests fail, so we skip them. According to the author of Slic3r, that should be safe: "Tests failed because of a typo when the 0.9.10b tag was applied. You can safely ignore the test results, Slic3r will work." See https://github.com/alexrj/Slic3r/issues/1303 For reference, the errors look like this: Use of uninitialized value $deg in numeric eq (==) at /tmp/nix-build-perl-slic3r-0.9.10b.drv-0/git-export/t/../lib/Slic3r/TriangleMesh.pm line 328. # Looks like your test exited with 255 before it could output anything.
2013-04-28 12:59:00 +02:00
};
* Drop the "perl" prefix from Perl attribute names. It's redundant now that Perl packages are in their own namespace (perlPackages.<pkg>). svn path=/nixpkgs/trunk/; revision=15176
2009-04-20 14:49:35 +02:00
perlXMLParser = perlPackages.XMLParser;
* added generic Cabal builder * transformed zlib, vty, binary, X11 to use generic Cabal builder * note that Cabal library packages are now by default prefixed with "haskell-" svn path=/nixpkgs/trunk/; revision=10247
2008-01-22 17:26:57 +01:00
add ack-1.92 patch provided by Francois Perrad svn path=/nixpkgs/trunk/; revision=20864
2010-03-30 01:36:38 +02:00
ack = perlPackages.ack;
* Added ghc-6.8.3 as the new default version of ghc. * Added a ghc HEAD snapshot (ghc-6.9.x). svn path=/nixpkgs/trunk/; revision=12391
2008-07-21 16:43:33 +02:00
Make initrd and the kernel builds repeatable.
2013-08-16 02:42:11 +02:00
perlArchiveCpio = perlPackages.ArchiveCpio;
add perlcritic 1.105 (and Test::Perl::Critic 1.02) and some depndencies: total perl libs added: BKeywords ConfigTiny ExceptionClass FileRemove FileWhich HookLexWrap IOString IPCRun3 PerlCritic PerlTidy PPI PodSpell ProbePerl ReadonlyXS RegexpParser StringFormat TestObject TestPerlCritic TestScript TestSubCalls patch provided by Francois Perrad svn path=/nixpkgs/trunk/; revision=20865
2010-03-30 01:36:40 +02:00
perlcritic = perlPackages.PerlCritic;
all-packages.nix: drop trailing whitespace
2014-04-11 10:06:06 +02:00
add Planetary Annihilation: next-generation RTS that takes the genre to a planetary scale
2014-03-16 23:31:00 +01:00
planetary_annihilation = callPackage ../games/planetaryannihilation { };
* Added ghc-6.8.3 as the new default version of ghc. * Added a ghc HEAD snapshot (ghc-6.9.x). svn path=/nixpkgs/trunk/; revision=12391
2008-07-21 16:43:33 +02:00
pkgs/top-level/all-packages.nix: stripped trailing whitespace svn path=/nixpkgs/trunk/; revision=22734
2010-07-26 15:41:09 +02:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### DEVELOPMENT / PYTHON MODULES
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
recurse into python33 and pypy packages
2013-07-29 14:52:19 +02:00
# python function with default python interpreter
* Move buildPythonPackage and setuptools into python-packages.nix. This ensures that they're built with the same "python" argument. svn path=/nixpkgs/branches/modular-python/; revision=26593
2011-03-29 17:02:15 +02:00
buildPythonPackage = pythonPackages.buildPythonPackage;
Adding calibre. This involved also: - Adding podofo - Adding some new python packages - Making new pkgs attributes for python packages to build with python 2.6 - Updating some python packages expressions to allow python 2.6, and not only 2.5. svn path=/nixpkgs/trunk/; revision=19303
2010-01-07 23:47:30 +01:00
add comment
2013-01-15 18:29:42 +01:00
# `nix-env -i python-nose` installs for 2.7, the default python.
# Therefore we do not recurse into attributes here, in contrast to
# python27Packages. `nix-env -iA python26Packages.nose` works
# regardless.
* Let nix-env only search Python 2.7 packages. Reported by Konrad Hinsen. We should add a check to enforce that every package/version pair in "nix-env -qa" is unique :-) svn path=/nixpkgs/trunk/; revision=33424
2012-03-26 16:07:34 +02:00
python26Packages = import ./python-packages.nix {
Change Nevow, SimpleJSON, and Foolscap to use `buildPythonPackage'. svn path=/nixpkgs/trunk/; revision=15707
2009-05-24 23:08:39 +02:00
inherit pkgs;
Adding calibre. This involved also: - Adding podofo - Adding some new python packages - Making new pkgs attributes for python packages to build with python 2.6 - Updating some python packages expressions to allow python 2.6, and not only 2.5. svn path=/nixpkgs/trunk/; revision=19303
2010-01-07 23:47:30 +01:00
python = python26;
* Let nix-env only search Python 2.7 packages. Reported by Konrad Hinsen. We should add a check to enforce that every package/version pair in "nix-env -qa" is unique :-) svn path=/nixpkgs/trunk/; revision=33424
2012-03-26 16:07:34 +02:00
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
python and pythonPackage attr naming - cosmetic changes
2014-07-07 18:55:43 +02:00
python27Packages = lib.hiPrioSet (recurseIntoAttrs (import ./python-packages.nix {
inherit pkgs;
python = python27;
}));
python32Packages = import ./python-packages.nix {
inherit pkgs;
python = python32;
};
add python3 support to pythonPackages
2013-07-27 20:51:54 +02:00
recurse into python33 and pypy packages
2013-07-29 14:52:19 +02:00
python33Packages = recurseIntoAttrs (import ./python-packages.nix {
add python3 support to pythonPackages
2013-07-27 20:51:54 +02:00
inherit pkgs;
python = python33;
recurse into python33 and pypy packages
2013-07-29 14:52:19 +02:00
});
add python3 support to pythonPackages
2013-07-27 20:51:54 +02:00
python: update 3.4.0 to stable release
2014-03-17 15:19:24 +01:00
python34Packages = recurseIntoAttrs (import ./python-packages.nix {
add python 3.4.0rc2
2014-03-03 14:21:07 +01:00
inherit pkgs;
python = python34;
python: update 3.4.0 to stable release
2014-03-17 15:19:24 +01:00
});
add python 3.4.0rc2
2014-03-03 14:21:07 +01:00
recurse into python33 and pypy packages
2013-07-29 14:52:19 +02:00
pypyPackages = recurseIntoAttrs (import ./python-packages.nix {
inherit pkgs;
python = pypy;
});
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
foursuite = callPackage ../development/python-modules/4suite { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bsddb3 = callPackage ../development/python-modules/bsddb3 { };
* changed from haddock-2.0.0.0 to haddock-2.1.0 (both only work with ghc-6.8.2, not ghc-6.8.3) * added haddock-0.9 as a version that compiles with nearly all ghc's we have * added haddock-0.9-boot the works with ghc-6.4.2-boot * the haddock-0.9-boot is now used to generate library documentation while building ghc-6.8.3 svn path=/nixpkgs/trunk/; revision=12392
2008-07-22 15:01:30 +02:00
electrum: initial expression Electrum is a Bitcoin thin-wallet. https://electrum.org
2014-03-23 16:22:57 +01:00
ecdsa = callPackage ../development/python-modules/ecdsa { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
numeric = callPackage ../development/python-modules/numeric { };
Add recent versions of the Haskell libraries HTTP, HaXml, haxr, and haxr-th. Unfortunately, the latter library doesn't build successfully because of the following error: Setup: ../LICENSE: copyFile: does not exist (No such file or directory) I'm not sure where this comes from. Also, it seems that passing haxr-th the library haxr as a build input doesn't suffice; it also needs to be passed the libraries that haxr depends on to configure successfully. Something isn't right. Andreas, do you know how to fix this? svn path=/nixpkgs/trunk/; revision=12722
2008-08-26 14:50:03 +02:00
pythonPackages: use unversioned to blend into pkgs, no functional change
2013-01-11 15:15:52 +01:00
pil = pythonPackages.pil;
Add recent versions of the Haskell libraries HTTP, HaXml, haxr, and haxr-th. Unfortunately, the latter library doesn't build successfully because of the following error: Setup: ../LICENSE: copyFile: does not exist (No such file or directory) I'm not sure where this comes from. Also, it seems that passing haxr-th the library haxr as a build input doesn't suffice; it also needs to be passed the libraries that haxr depends on to configure successfully. Something isn't right. Andreas, do you know how to fix this? svn path=/nixpkgs/trunk/; revision=12722
2008-08-26 14:50:03 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
psyco = callPackage ../development/python-modules/psyco { };
Add recent versions of the Haskell libraries HTTP, HaXml, haxr, and haxr-th. Unfortunately, the latter library doesn't build successfully because of the following error: Setup: ../LICENSE: copyFile: does not exist (No such file or directory) I'm not sure where this comes from. Also, it seems that passing haxr-th the library haxr as a build input doesn't suffice; it also needs to be passed the libraries that haxr depends on to configure successfully. Something isn't right. Andreas, do you know how to fix this? svn path=/nixpkgs/trunk/; revision=12722
2008-08-26 14:50:03 +02:00
pycairo: move to pythonPackages
2013-01-11 15:23:44 +01:00
pycairo = pythonPackages.pycairo;
* updated the ghc HEAD snapshot svn path=/nixpkgs/trunk/; revision=12454
2008-07-31 14:36:47 +02:00
pycapnp: Add package
2014-04-25 20:33:01 +02:00
pycapnp = pythonPackages.pycapnp;
pythonPackages: use unversioned to blend into pkgs, no functional change
2013-01-11 15:15:52 +01:00
pycrypto = pythonPackages.pycrypto;
* gtk2hs switched to ghc-6.8.2 (but still not following the scheme of the other Haskell libs) * HDBC with postgresql and sqlite3 drivers added svn path=/nixpkgs/trunk/; revision=10287
2008-01-25 13:42:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pycups = callPackage ../development/python-modules/pycups { };
* gtk2hs switched to ghc-6.8.2 (but still not following the scheme of the other Haskell libs) * HDBC with postgresql and sqlite3 drivers added svn path=/nixpkgs/trunk/; revision=10287
2008-01-25 13:42:07 +01:00
add jbrout, a photo manager using IPTC keywords/EXIF svn path=/nixpkgs/trunk/; revision=28759
2011-08-22 22:26:11 +02:00
pyexiv2 = callPackage ../development/python-modules/pyexiv2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pygame = callPackage ../development/python-modules/pygame { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
pygobject: in pythonPackages, removed hack handled now by pth
2013-01-11 15:30:56 +01:00
pygobject = pythonPackages.pygobject;
Add recent versions of the Haskell libraries HTTP, HaXml, haxr, and haxr-th. Unfortunately, the latter library doesn't build successfully because of the following error: Setup: ../LICENSE: copyFile: does not exist (No such file or directory) I'm not sure where this comes from. Also, it seems that passing haxr-th the library haxr as a build input doesn't suffice; it also needs to be passed the libraries that haxr depends on to configure successfully. Something isn't right. Andreas, do you know how to fix this? svn path=/nixpkgs/trunk/; revision=12722
2008-08-26 14:50:03 +02:00
Adding pygobject3 (for bluez4). bluez-simple-agent fails to work otherwise. We discussed this a bit on #486, and this looks like the simplest way to get bluez-simple-agent again.
2013-05-09 21:11:30 +02:00
pygobject3 = pythonPackages.pygobject3;
pygtk in pythonPackages, checks disabled, demo works, relates #223 Previously the checkPhase was not executed. It is now and a couple of issues with it are seded away.
2013-01-11 17:45:26 +01:00
pygtk = pythonPackages.pygtk;
MonadLab: Haskell tool (and library) for automatic generation of layered monads svn path=/nixpkgs/trunk/; revision=13105
2008-10-23 16:22:36 +02:00
pygtk in pythonPackages, checks disabled, demo works, relates #223 Previously the checkPhase was not executed. It is now and a couple of issues with it are seded away.
2013-01-11 17:45:26 +01:00
pyGtkGlade = pythonPackages.pyGtkGlade;
* small fix for the generic Cabal builder * added Crypto and pcre-light packages svn path=/nixpkgs/trunk/; revision=10250
2008-01-22 20:02:55 +01:00
Move namePrefix="" python packages out of python-packges.nix It doesn't make sense to build tools/applications with three different python interpreter versions, so move them out of python modules list. Also reverts 53ffc6e0ef395a2bd7651423d9783ad8184be1d0.
2013-07-31 13:32:25 +02:00
pylint = callPackage ../development/python-modules/pylint { };
Added Gajim XMPP client in nearly full-feature configuration with all dependencies svn path=/nixpkgs/trunk/; revision=15001
2009-04-12 21:34:20 +02:00
pyopenssl = builderDefsPackage (import ../development/python-modules/pyopenssl) {
inherit python openssl;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rhpl = callPackage ../development/python-modules/rhpl { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
sip: update to 4.15.4 and add python3 support
2014-01-08 09:06:08 +01:00
sip = callPackage ../development/python-modules/sip { };
Added SVK. svn path=/nixpkgs/trunk/; revision=11937
2008-05-30 20:15:25 +02:00
pyqt4: update to 4.10.3 and add python3 support also add python3 support for dbus-python
2014-01-08 09:39:05 +01:00
pyqt4 = callPackage ../development/python-modules/pyqt/4.x.nix {
pyqt4: fix build on darwin (close #751) * build with clangStdenv
2013-07-14 05:41:26 +02:00
stdenv = if stdenv.isDarwin
then clangStdenv
else stdenv;
};
Added PyQt 4.7 expression required by KDE 4.4.x svn path=/nixpkgs/trunk/; revision=19911
2010-02-10 17:09:12 +01:00
pyside-1.0.9 svn path=/nixpkgs/trunk/; revision=30950
2011-12-17 21:16:45 +01:00
pysideApiextractor = callPackage ../development/python-modules/pyside/apiextractor.nix { };
pysideGeneratorrunner = callPackage ../development/python-modules/pyside/generatorrunner.nix { };
pyside = callPackage ../development/python-modules/pyside { };
pysideTools = callPackage ../development/python-modules/pyside/tools.nix { };
pysideShiboken = callPackage ../development/python-modules/pyside/shiboken.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pyx = callPackage ../development/python-modules/pyx { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pyxml = callPackage ../development/python-modules/pyxml { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Move namePrefix="" python packages out of python-packges.nix It doesn't make sense to build tools/applications with three different python interpreter versions, so move them out of python modules list. Also reverts 53ffc6e0ef395a2bd7651423d9783ad8184be1d0.
2013-07-31 13:32:25 +02:00
rbtools = callPackage ../development/python-modules/rbtools { };
* Move buildPythonPackage and setuptools into python-packages.nix. This ensures that they're built with the same "python" argument. svn path=/nixpkgs/branches/modular-python/; revision=26593
2011-03-29 17:02:15 +02:00
setuptools = pythonPackages.setuptools;
Added SVK. svn path=/nixpkgs/trunk/; revision=11937
2008-05-30 20:15:25 +02:00
electrum: initial expression Electrum is a Bitcoin thin-wallet. https://electrum.org
2014-03-23 16:22:57 +01:00
slowaes = callPackage ../development/python-modules/slowaes { };
* Move wxPython into python-packages.nix so that you can get wxPython built for the appropriate Python version (e.g. python26Packages.wxPython). svn path=/nixpkgs/trunk/; revision=27127
2011-05-04 10:41:50 +02:00
wxPython = pythonPackages.wxPython;
wxPython28 = pythonPackages.wxPython28;
Added SVK. svn path=/nixpkgs/trunk/; revision=11937
2008-05-30 20:15:25 +02:00
Remove from `all-packages.nix' packages that are now in `python-packages.nix'. svn path=/nixpkgs/trunk/; revision=15710
2009-05-24 23:27:30 +02:00
twisted = pythonPackages.twisted;
* Latest Catalyst packages, include FormFu and its gazillion dependencies. svn path=/nixpkgs/trunk/; revision=14042
2009-02-12 16:59:22 +01:00
pythonPackages.zopeInterface is now pythonPackages.zope_interface
2013-01-22 00:11:49 +01:00
ZopeInterface = pythonPackages.zope_interface;
* Latest Catalyst packages, include FormFu and its gazillion dependencies. svn path=/nixpkgs/trunk/; revision=14042
2009-02-12 16:59:22 +01:00
Wrapped R's package system similarly to perlPackages
2013-09-20 01:26:07 +02:00
### DEVELOPMENT / R MODULES
all-packages.nix: move all R-related attributes into one place
2014-05-04 20:51:30 +02:00
R = callPackage ../applications/science/math/R {
inherit (xlibs) libX11 libXt;
texLive = texLiveAggregationFun { paths = [ texLive texLiveExtra ]; };
R: don't install the "recommended packages" These packages come with R, but if we install them as part of this build, then we cannot update them without re-building R as well. Instead, we add those packages to the R environment through the r-wrapper. This means that recommended packages can be updated in cran-packgaes.nix, and those updates have an effect on the installation without re-building R itself.
2014-05-04 21:12:34 +02:00
withRecommendedPackages = false;
all-packages.nix: move all R-related attributes into one place
2014-05-04 20:51:30 +02:00
};
R: simplify the generic builder
2014-05-04 23:54:11 +02:00
rWrapper = callPackage ../development/r-modules/wrapper.nix {
R: don't install the "recommended packages" These packages come with R, but if we install them as part of this build, then we cannot update them without re-building R as well. Instead, we add those packages to the R environment through the r-wrapper. This means that recommended packages can be updated in cran-packgaes.nix, and those updates have an effect on the installation without re-building R itself.
2014-05-04 21:12:34 +02:00
# Those packages are usually installed as part of the R build.
recommendedPackages = with rPackages; [ MASS lattice Matrix nlme
survival boot cluster codetools foreign KernSmooth rpart class
nnet spatial mgcv ];
# Override this attribute to register additional libraries.
all-packages.nix: move all R-related attributes into one place
2014-05-04 20:51:30 +02:00
packages = [];
};
Wrapped R's package system similarly to perlPackages
2013-09-20 01:26:07 +02:00
R: don't recurse into the rPackages set to conserve memory and CPU time The addition of CRAN has made "nix-env -qa \*" run ~30% longer than before [1]. [1] https://github.com/NixOS/nixpkgs/commit/0d264c17616646a7d68e0a465fdc0f335e0d2fb3
2014-05-07 19:12:15 +02:00
rPackages = import ../development/r-modules/cran-packages.nix {
Wrapped R's package system similarly to perlPackages
2013-09-20 01:26:07 +02:00
inherit pkgs;
Remove uses of __overrides feature In addition to replacing use of a feature with IMO confusing semantics, this will also let us cleanly separate out all-packages.nix into category-specific files without changing the structure of the pkgs attrset. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-30 17:04:45 +01:00
overrides = (config.rPackageOverrides or (p: {})) pkgs;
R: don't recurse into the rPackages set to conserve memory and CPU time The addition of CRAN has made "nix-env -qa \*" run ~30% longer than before [1]. [1] https://github.com/NixOS/nixpkgs/commit/0d264c17616646a7d68e0a465fdc0f335e0d2fb3
2014-05-07 19:12:15 +02:00
};
* Latest Catalyst packages, include FormFu and its gazillion dependencies. svn path=/nixpkgs/trunk/; revision=14042
2009-02-12 16:59:22 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### SERVERS
Added SVK. svn path=/nixpkgs/trunk/; revision=11937
2008-05-30 20:15:25 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
rdf4store = callPackage ../servers/http/4store { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
apache: add version 2.4
2012-07-07 08:41:21 +02:00
apacheHttpd = pkgs.apacheHttpd_2_2;
apacheHttpd_2_2 = callPackage ../servers/http/apache-httpd/2.2.nix {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
sslSupport = true;
* Updated some Catalyst packages. svn path=/nixpkgs/trunk/; revision=14137
2009-02-20 11:56:47 +01:00
};
apache: add version 2.4
2012-07-07 08:41:21 +02:00
apacheHttpd_2_4 = lowPrio (callPackage ../servers/http/apache-httpd/2.4.nix {
sslSupport = true;
});
apcupsd: new package apcupsd is a daemon for controlling APC UPSes.
2013-07-17 01:53:30 +02:00
apcupsd = callPackage ../servers/apcupsd { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sabnzbd = callPackage ../servers/sabnzbd { };
Added sabnzbd usenet download tool :) svn path=/nixpkgs/trunk/; revision=18294
2009-11-08 20:55:37 +01:00
bind: avoid build impurity by explicitly enabling/disabling features The BIND configure script finds extra dependencies in /usr/include and /usr/lib, and activates additional features if it does. This may cause the build to fail on systems that cannot use a chroot environment. Actively disabling those additional features prevents this issue from occurring.
2013-06-09 19:25:46 +02:00
bind = callPackage ../servers/dns/bind { };
* Latest Catalyst packages, include FormFu and its gazillion dependencies. svn path=/nixpkgs/trunk/; revision=14042
2009-02-12 16:59:22 +01:00
Adding the reference to bird
2013-09-15 11:38:52 +02:00
bird = callPackage ../servers/bird { };
Add ElasticMQ, a message queue service
2012-07-09 21:26:07 +02:00
couchdb = callPackage ../servers/http/couchdb {
spidermonkey = spidermonkey_185;
couchdb: remove redundant customConfigFile
2014-02-27 14:34:19 +01:00
python = python27;
sphinx = python27Packages.sphinx;
erlangR16: updated to R16B03-1 - couchdb: using erlangR16 (fails to build with R17) - rename erlang attr names to use only major version in attr name
2014-06-05 02:16:50 +02:00
erlang = erlangR16;
Add ElasticMQ, a message queue service
2012-07-09 21:26:07 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dico = callPackage ../servers/dico { };
* Latest Catalyst packages, include FormFu and its gazillion dependencies. svn path=/nixpkgs/trunk/; revision=14042
2009-02-12 16:59:22 +01:00
Revert "Revert "dictd: Update to latest upstream (0.12.1)."" and add the missing libmaa.nix. This reverts commit d59778678a23d72297a5dd813387d38c0448df3c.
2014-01-31 13:17:37 +01:00
dict = callPackage ../servers/dict {
libmaa = callPackage ../servers/dict/libmaa.nix {};
};
Added dict and working on adding dictionaries svn path=/nixpkgs/trunk/; revision=10976
2008-03-06 05:39:05 +01:00
dictdDBs = recurseIntoAttrs (import ../servers/dict/dictd-db.nix {
inherit builderDefs;
});
Updated: RelFS. Added DictDB aggregation. svn path=/nixpkgs/trunk/; revision=11006
2008-03-07 07:11:08 +01:00
dictDBCollector = import ../servers/dict/dictd-db-collector.nix {
inherit stdenv lib dict;
};
dictd-wiktionary: Let dictd serve an offline copy of wiktionary. @vcunat: add -O to python, as it takes lots of time to process
2012-10-27 23:02:44 +02:00
dictdWiktionary = callPackage ../servers/dict/dictd-wiktionary.nix {};
dictd-wordnet: Make wordnet available via local dictd.
2012-10-27 23:01:53 +02:00
dictdWordnet = callPackage ../servers/dict/dictd-wordnet.nix {};
diod: New package, a 9P server implementation for Linux
2013-08-20 17:24:30 +02:00
diod = callPackage ../servers/diod { };
dovecot: Add version 2.2.4 as attribute dovecot22 I also added a patch that makes dovecot search for plugins in /var/lib/dovecot/modules. This way, you can add plugins from several packages without running into circular dependencies. The module dir needs to be populated before the dovecot service is started, for example. This is currently not done in NixOS, so you need to implement your own service in order to get the plugins working. The module patch has not been added to the old 2.1.x package.
2013-07-15 14:48:34 +02:00
dovecot = dovecot21;
dovecot21 = callPackage ../servers/mail/dovecot { };
dovecot22 = callPackage ../servers/mail/dovecot/2.2.x.nix { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
New package: dovecot_pigeonhole, a sieve plugin for dovecot
2013-07-15 15:15:35 +02:00
dovecot_pigeonhole = callPackage ../servers/mail/dovecot-pigeonhole { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
add etcd package
2014-06-23 10:55:46 +02:00
etcd = callPackage ../servers/etcd { };
all-packages.nix: strip trailing whitespace
2014-05-04 14:39:40 +02:00
ejabberd = callPackage ../servers/xmpp/ejabberd {
erlangR16: updated to R16B03-1 - couchdb: using erlangR16 (fails to build with R17) - rename erlang attr names to use only major version in attr name
2014-06-05 02:16:50 +02:00
erlang = erlangR16;
Readding Erlang R16B02: R17 is a major update and it breaks Ejabberd.
2014-05-02 18:50:58 +02:00
};
Added erlang/ejabberd packages svn path=/nixpkgs/trunk/; revision=10258
2008-01-23 11:06:07 +01:00
Add ElasticMQ, a message queue service
2012-07-09 21:26:07 +02:00
elasticmq = callPackage ../servers/elasticmq { };
pkgs/top-level/all-packages.nix: strip trailing white space svn path=/nixpkgs/trunk/; revision=21416
2010-04-29 10:54:02 +02:00
add etcdctl package
2014-06-23 11:03:03 +02:00
etcdctl = callPackage ../development/tools/etcdctl { };
fcgiwrap: new package Simple server for running CGI applications over FastCGI https://nginx.localdomain.pl/wiki/FcgiWrap
2014-05-10 18:37:58 +02:00
fcgiwrap = callPackage ../servers/fcgiwrap { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
felix = callPackage ../servers/felix { };
pkgs/top-level/all-packages.nix: strip trailing white space svn path=/nixpkgs/trunk/; revision=21416
2010-04-29 10:54:02 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
felix_remoteshell = callPackage ../servers/felix/remoteshell.nix { };
added couchdb 0.8.1-incubating svn path=/nixpkgs/trunk/; revision=18141
2009-11-05 15:41:05 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fingerd_bsd = callPackage ../servers/fingerd/bsd-fingerd { };
finger client and daemon added svn path=/nixpkgs/trunk/; revision=10364
2008-01-28 20:51:14 +01:00
firebirdSuper settings document why its better to not use --with-system-icu See patch for nixos adding firebird service Signed-off-by: Marc Weber <marco-oweber@gmx.de>
2013-07-30 16:33:46 +02:00
firebird = callPackage ../servers/firebird { icu = null; };
firebirdSuper = callPackage ../servers/firebird { superServer = true; };
adding firebird (and embedded library ?) svn path=/nixpkgs/trunk/; revision=22130
2010-06-03 17:19:56 +02:00
add fleet package
2014-06-23 11:20:41 +02:00
fleet = callPackage ../servers/fleet { };
Add freepops. svn path=/nixpkgs/trunk/; revision=27450
2011-06-14 04:41:28 +02:00
freepops = callPackage ../servers/mail/freepops { };
Adding freeswitch svn path=/nixpkgs/trunk/; revision=25664
2011-01-21 23:12:34 +01:00
freeswitch = callPackage ../servers/sip/freeswitch { };
Ghost One: packaged svn path=/nixpkgs/trunk/; revision=25137
2010-12-15 03:19:59 +01:00
ghostOne = callPackage ../servers/games/ghost-one {
ghost-one: the linking phase requires boost in tagged layout
2012-07-07 11:57:52 +02:00
boost = boost144.override { taggedLayout = true; };
Ghost One: packaged svn path=/nixpkgs/trunk/; revision=25137
2010-12-15 03:19:59 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ircdHybrid = callPackage ../servers/irc/ircd-hybrid { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jboss = callPackage ../servers/http/jboss { };
Added JBoss svn path=/nixpkgs/trunk/; revision=10259
2008-01-23 13:25:08 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jboss_mysql_jdbc = callPackage ../servers/http/jboss/jdbc/mysql { };
Added MySQL driver link to JBoss svn path=/nixpkgs/trunk/; revision=10374
2008-01-29 12:11:26 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jetty = callPackage ../servers/http/jetty { };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jetty61 = callPackage ../servers/http/jetty/6.1 { };
Added jetty 6.1 svn path=/nixpkgs/trunk/; revision=10858
2008-02-26 10:26:17 +01:00
Adding Joseki: HTTP/SparQL server based on Jena framework. Just a unpack/mix/fix paths expression relying on compiled JAR releases. svn path=/nixpkgs/trunk/; revision=26168
2011-03-05 23:05:00 +01:00
joseki = callPackage ../servers/http/joseki {};
Add leafnode for unix systems
2014-04-15 09:54:58 +02:00
leafnode = callPackage ../servers/news/leafnode { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lighttpd = callPackage ../servers/http/lighttpd { };
added lighthttpd svn path=/nixpkgs/trunk/; revision=12907
2008-09-24 02:42:50 +02:00
mailman: add version 2.1.16
2013-10-21 15:02:35 +02:00
mailman = callPackage ../servers/mail/mailman { };
mediatomb: use default/latest ffmpeg
2013-12-23 10:50:20 +01:00
mediatomb = callPackage ../servers/mediatomb { };
MediaTomb: packaged svn path=/nixpkgs/trunk/; revision=27700
2011-07-11 02:42:02 +02:00
Add memcached Patch by Corey O'Connor, see http://reviewboard.loegria.net/r/15/ svn path=/nixpkgs/trunk/; revision=33461
2012-03-29 00:30:13 +02:00
memcached = callPackage ../servers/memcached {};
mod_dnssd: new apache httpd 2.2 module Provide Zeroconf support via DNS-SD using Avahi http://0pointer.de/lennart/projects/mod_dnssd
2014-04-12 12:48:16 +02:00
mod_dnssd = callPackage ../servers/http/apache-modules/mod_dnssd/default.nix { };
Add mod_evasive
2012-07-31 15:51:31 +02:00
mod_evasive = callPackage ../servers/http/apache-modules/mod_evasive { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mod_python = callPackage ../servers/http/apache-modules/mod_python { };
Added libzip svn path=/nixpkgs/trunk/; revision=9637
2007-11-11 17:19:00 +01:00
Added an expression for mod_fastcgi-2.4.6, to be used with Apache 2. svn path=/nixpkgs/trunk/; revision=24406
2010-10-21 17:39:48 +02:00
mod_fastcgi = callPackage ../servers/http/apache-modules/mod_fastcgi { };
Added an expression for mod_wsgi-3.3, to be used with Apache 2. svn path=/nixpkgs/trunk/; revision=24408
2010-10-21 17:39:58 +02:00
mod_wsgi = callPackage ../servers/http/apache-modules/mod_wsgi { };
mpd: fix build on darwin * disable systemd * disable alsaLib * disable ffado * compile with gccApple * disable libmad
2013-07-04 07:07:37 +02:00
mpd = callPackage ../servers/mpd {
mpdcron: add expression
2014-05-23 00:39:28 +02:00
aacSupport = config.mpd.aacSupport or true;
ffmpegSupport = config.mpd.ffmpegSupport or true;
mpd: fix build on darwin * disable systemd * disable alsaLib * disable ffado * compile with gccApple * disable libmad
2013-07-04 07:07:37 +02:00
};
Add ncmpcpp Patch by mornfall svn path=/nixpkgs/trunk/; revision=30730
2011-12-05 02:32:25 +01:00
mpd_clientlib = callPackage ../servers/mpd/clientlib.nix { };
mpd: New nixpkg. svn path=/nixpkgs/trunk/; revision=21148
2010-04-18 21:26:30 +02:00
pkgs/servers/http/mini-httpd: added version 1.1 svn path=/nixpkgs/trunk/; revision=28613
2011-08-16 16:01:38 +02:00
miniHttpd = callPackage ../servers/http/mini-httpd {};
Add mlmmj package and nixos module.
2014-07-09 00:43:26 +02:00
mlmmj = callPackage ../servers/mail/mlmmj { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
myserver = callPackage ../servers/http/myserver { };
Add GNU MyServer. svn path=/nixpkgs/trunk/; revision=16801
2009-08-21 12:20:40 +02:00
nginx: upgrade to 1.6.0, expose many more modules By default, we now build all the optional nginx modules, including the out-of-band ones like moreheaders and rtmp support. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-02 08:18:44 +02:00
nginx = callPackage ../servers/http/nginx {
rtmp = true;
fullWebDAV = true;
syslog = true;
moreheaders = true;
};
Added nginx - lightweight http server svn path=/nixpkgs/trunk/; revision=13518
2008-11-30 10:06:53 +01:00
Add ngircd IRC server
2014-03-20 02:03:19 +01:00
ngircd = callPackage ../servers/irc/ngircd { };
Adding a minimal script set to serve store as a dynamical binary cache
2014-06-29 22:39:54 +02:00
nix-binary-cache = callPackage ../servers/http/nix-binary-cache {};
nsd: add package version 4.0.3
2014-06-12 11:14:44 +02:00
nsd = callPackage ../servers/dns/nsd { };
add nsq package
2014-06-23 11:43:17 +02:00
nsq = callPackage ../servers/nsq { };
nixpkgs: openresty 1.7.4.1rc1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-08-20 07:34:29 +02:00
openresty = callPackage ../servers/http/openresty { };
New package: opensmtpd, an SMTP server from the OpenBSD project.
2013-07-15 15:05:03 +02:00
opensmtpd = callPackage ../servers/mail/opensmtpd { };
petidomo: add version 4.2
2013-02-09 20:27:44 +01:00
petidomo = callPackage ../servers/mail/petidomo { };
popa3d: add version 1.0.2
2012-09-19 01:16:01 +02:00
popa3d = callPackage ../servers/mail/popa3d { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
postfix = callPackage ../servers/mail/postfix { };
Added Postfix to all-packages.nix svn path=/nixpkgs/trunk/; revision=12069
2008-06-13 06:31:31 +02:00
postfix: Add version 2.11.0 as nixpkgs.postfix211 I think this version should replace the current nixpkgs.postfix, but it could potentially break stuff since the version jump is big (2.8 -> 2.11).
2014-04-24 11:56:54 +02:00
postfix211 = callPackage ../servers/mail/postfix/2.11.nix { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pulseaudio = callPackage ../servers/pulseaudio {
Add PulseAudio, an audio server. svn path=/nixpkgs/trunk/; revision=13659
2008-12-19 15:56:37 +01:00
gconf = gnome.GConf;
* Sync with the trunc. * Fixed the hash in PulseAudio: I updated the name/version, but forgot to update the hash. So secretly it was still building the old version. Also, now that we've realised that the PulseAudio server and library don't need to be the same build, disable some dependencies by default (avahi and bluez). svn path=/nixpkgs/branches/kde-4.7/; revision=28023
2011-07-31 21:44:58 +02:00
# The following are disabled in the default build, because if this
# functionality is desired, they are only needed in the PulseAudio
# server.
bluez = null;
avahi = null;
Add PulseAudio, an audio server. svn path=/nixpkgs/trunk/; revision=13659
2008-12-19 15:56:37 +01:00
};
provide pulseaudioFull and set it as default to hardware.pulseaudio.package
2014-08-12 12:50:42 +02:00
pulseaudioFull = pulseaudio.override {
bluez = bluez5;
avahi = avahi;
jackaudioSupport = true;
x11Support = true;
};
Add PulseAudio, an audio server. svn path=/nixpkgs/trunk/; revision=13659
2008-12-19 15:56:37 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tomcat_connectors = callPackage ../servers/http/apache-modules/tomcat-connectors { };
Added apache tomcat connector module svn path=/nixpkgs/trunk/; revision=10260
2008-01-23 15:40:03 +01:00
Add GNU Pies. svn path=/nixpkgs/trunk/; revision=26942
2011-04-23 23:15:11 +02:00
pies = callPackage ../servers/pies { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
portmap = callPackage ../servers/portmap { };
Add portmap, an ONC RPC directory service. svn path=/nixpkgs/trunk/; revision=11138
2008-03-15 23:51:46 +01:00
Adding rpcbind. Patch by Rickard Nilsson. svn path=/nixpkgs/trunk/; revision=33341
2012-03-21 21:35:15 +01:00
rpcbind = callPackage ../servers/rpcbind { };
Remove obsolete JDK versions These are the JDK 5 on powerpc-linux (no longer a maintained Nixpkgs platform), JDK 1.4 (required a manual download) and JDK 5 on Linux (idem).
2012-08-22 21:24:04 +02:00
#monetdb = callPackage ../servers/sql/monetdb { };
adding monetdb database svn path=/nixpkgs/trunk/; revision=16262
2009-07-09 05:50:44 +02:00
Add mariadb
2014-02-24 21:34:57 +01:00
mariadb = callPackage ../servers/sql/mariadb {};
mongodb: upgrade to 2.4.0
2013-03-22 21:23:25 +01:00
mongodb = callPackage ../servers/nosql/mongodb { };
mongodb: new package (nosql database) - nixos integration available svn path=/nixpkgs/trunk/; revision=31655
2012-01-18 21:32:41 +01:00
Add Riak 1.3.1 This modifies how the `riak` and `riak-admin` scripts work such that one has to specify environment variables for where the data, log, and etc directories live.
2013-05-23 11:17:12 +02:00
riak = callPackage ../servers/nosql/riak/1.3.1.nix { };
Add influxdb, scalable datastore for metrics, events, and real-time analytics
2014-05-26 11:12:38 +02:00
influxdb = callPackage ../servers/nosql/influxdb { };
mysql: Move all versions into the same directory
2013-10-17 13:25:13 +02:00
mysql51 = import ../servers/sql/mysql/5.1.x.nix {
mysql 5.1.41 svn path=/nixpkgs/trunk/; revision=19017
2009-12-17 19:54:12 +01:00
inherit fetchurl ncurses zlib perl openssl stdenv;
ps = procps; /* !!! Linux only */
};
mysql: Move all versions into the same directory
2013-10-17 13:25:13 +02:00
mysql55 = callPackage ../servers/sql/mysql/5.5.x.nix { };
Added MySQL 5.5. It's still a bit experimental though svn path=/nixpkgs/trunk/; revision=28145
2011-08-04 00:10:06 +02:00
Making more packages build on the Fuloong2f. I still can't build the kernel because it requires binutils yet to be released. svn path=/nixpkgs/branches/stdenv-updates/; revision=23132
2010-08-11 22:16:09 +02:00
mysql = mysql51;
MySQL5 should be default already. svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10846
2008-02-25 04:16:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mysql_jdbc = callPackage ../servers/sql/mysql/jdbc { };
Added libraries: - gtkmm: C++ bindings for gtk - glibmm: C++ bindings for glib - libsigc++ (C++) Added applications: - Batik: SVG rasterizer (and more) - Inkscape: vector graphics drawing application Upgraded: - boehm-gc svn path=/nixpkgs/trunk/; revision=3792
2005-09-07 16:57:30 +02:00
nagios: significant upgrades - Upgrade Nagios Core to 4.x - Expose mainConfigFile and cgiConfigFile in module for finer configuration control. - Upgrade Plugins to 2.x - Remove default objectDefs, which users probably want to customize. - Systemd-ify Nagios module and simplify directory structure - Upgrade Nagios package with more modern patch, and ensure the statedir is set to /var/lib/nagios Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-22 06:35:09 +02:00
nagios = callPackage ../servers/monitoring/nagios { };
* Build the i810 driver. Only depend on the Mesa headers, not all of Mesa. svn path=/nixpkgs/trunk/; revision=8060
2007-02-27 00:10:25 +01:00
munin: add the package, WIP
2013-05-20 11:18:40 +02:00
munin = callPackage ../servers/monitoring/munin { };
nagios: significant upgrades - Upgrade Nagios Core to 4.x - Expose mainConfigFile and cgiConfigFile in module for finer configuration control. - Upgrade Plugins to 2.x - Remove default objectDefs, which users probably want to customize. - Systemd-ify Nagios module and simplify directory structure - Upgrade Nagios package with more modern patch, and ensure the statedir is set to /var/lib/nagios Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-22 06:35:09 +02:00
nagiosPluginsOfficial = callPackage ../servers/monitoring/nagios/plugins/official-2.x.nix { };
Added pangoxsl and xmlroff svn path=/nixpkgs/trunk/; revision=3574
2005-08-13 23:35:49 +02:00
Add neo4j database
2014-08-16 23:53:03 +02:00
neo4j = callPackage ../servers/nosql/neo4j { };
net-snmp: Moved to pkgs/servers/monitoring
2012-06-21 21:22:17 +02:00
net_snmp = callPackage ../servers/monitoring/net-snmp { };
New package: riemann 0.2.6
2014-08-23 12:39:15 +02:00
riemann = callPackage ../servers/monitoring/riemann { };
* Added oidentd, an implementation of the IDENT protocol. svn path=/nixpkgs/trunk/; revision=30379
2011-11-10 23:29:58 +01:00
oidentd = callPackage ../servers/identd/oidentd { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openfire = callPackage ../servers/xmpp/openfire { };
all-packages.nix: stripped trailing whitespace svn path=/nixpkgs/trunk/; revision=33452
2012-03-28 15:49:16 +02:00
oracle-xe: Add new package, version 11.2.0. This is the Oracle Database which they give out for free, therefore it's called Express Edition. Well, I pretty much packaged this in vain as I finally found out that i don't need that Oracle Database stuff at all. And my original purpose was to do SQL query/constraint testing. So before I'm going to throw this away (forever, oh no!), maybe someone else might have a use case for this. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-03-07 07:49:26 +01:00
oracleXE = callPackage ../servers/sql/oracle-xe { };
EDK2: Significant cleanup and modularization, and add OVMF as an example of how to use it svn path=/nixpkgs/trunk/; revision=33059
2012-03-14 07:57:58 +01:00
OVMF = callPackage ../applications/virtualization/OVMF { };
svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10811
2008-02-21 17:24:44 +01:00
postgresql: Make 9.2 the default PostgreSQL 8.3 is end-of-life so it shouldn't be our default anymore. The problem with changing the default PostgreSQL is that it breaks NixOS installations that have PostgreSQL enabled without specifying an explicit PostgreSQL version, because PostgreSQL does not do automatic schema migration if the major version changes. Thus, it's always a good idea to specify the desired major version explicitly: services.postgresql.package = pkgs.postgresql92; (In fact, maybe we should remove the default value for services.postgresql.package.)
2013-04-04 18:07:49 +02:00
postgresql = postgresql92;
* Postgres updated to 8.3.8 and 8.4.1. Dropped the "with args" and "version" argument. Added a few Postgres mirrors. svn path=/nixpkgs/trunk/; revision=17804
2009-10-14 16:38:16 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
postgresql84 = callPackage ../servers/sql/postgresql/8.4.x.nix { };
add a variant of qt without mysql support svn path=/nixpkgs/trunk/; revision=5462
2006-06-18 00:04:42 +02:00
* Added PostgreSQL 9.0.1. svn path=/nixpkgs/trunk/; revision=25106
2010-12-13 22:55:34 +01:00
postgresql90 = callPackage ../servers/sql/postgresql/9.0.x.nix { };
* Added PostgreSQL 9.1.2. Updated PostgreSQL to 8.3.17 and 8.4.10. svn path=/nixpkgs/trunk/; revision=32475
2012-02-22 17:40:10 +01:00
postgresql91 = callPackage ../servers/sql/postgresql/9.1.x.nix { };
postgresql: Add version 9.2
2012-12-19 13:16:10 +01:00
postgresql92 = callPackage ../servers/sql/postgresql/9.2.x.nix { };
postgresql: Add version 9.3
2014-01-18 16:17:29 +01:00
postgresql93 = callPackage ../servers/sql/postgresql/9.3.x.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
postgresql_jdbc = callPackage ../servers/sql/postgresql/jdbc { };
* Added Qt 3.3.3. Basic installation, except that Xrender and Xft support are enabled (for anti-aliased fonts). BUG: Qt currently searches for plugins and documentation in the temporary build directory, instead of in its prefix. So, e.g., help in Qt Designer doesn't work. svn path=/nixpkgs/trunk/; revision=2066
2005-01-19 23:51:27 +01:00
perl-packages.nix, all-packages.nix: generally refer to 'postgresql' instead of 'postgresql92' This allows users to override the 'postgres' attribute with a different version and have the effect propagated to all other packages that depend on it.
2013-04-06 15:24:11 +02:00
psqlodbc = callPackage ../servers/sql/postgresql/psqlodbc { };
Add psqlodbc for iodbc
2012-10-08 23:26:02 +02:00
Added xmpppy - python XMPP library and pyIRCt - python IRC transport svn path=/nixpkgs/trunk/; revision=15005
2009-04-13 01:27:55 +02:00
pyIRCt = builderDefsPackage (import ../servers/xmpp/pyIRCt) {
inherit xmpppy pythonIRClib python makeWrapper;
};
pyMAILt = builderDefsPackage (import ../servers/xmpp/pyMAILt) {
inherit xmpppy python makeWrapper fetchcvs;
};
Add qpid v0.24 It includes both the broker and the C++ client lib. I had to do some hacks to prevent the installer from putting thins outside $out. Close #1134.
2013-10-24 12:44:03 +02:00
qpid-cpp = callPackage ../servers/amqp/qpid-cpp { };
* Added rabbitmq-server. svn path=/nixpkgs/branches/modular-python/; revision=26623
2011-03-31 13:09:20 +02:00
rabbitmq_server = callPackage ../servers/amqp/rabbitmq-server { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
radius = callPackage ../servers/radius { };
Add GNU Shishi and GNU Radius. Contributed by Brian Gough <bjg@gnu.org>. svn path=/nixpkgs/trunk/; revision=21313
2010-04-26 10:45:23 +02:00
redis: Build with default gcc
2014-08-09 21:49:09 +02:00
redis = callPackage ../servers/nosql/redis { };
redis: added version 2.4.7 Patch submitted by Phil Hagelberg <technomancy@gmail.com>. svn path=/nixpkgs/trunk/; revision=31992
2012-02-03 14:12:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
redstore = callPackage ../servers/http/redstore { };
Adding Redstore HTTP RDF/SPARQL server svn path=/nixpkgs/trunk/; revision=22428
2010-06-30 00:18:49 +02:00
Adding restund
2012-09-25 08:34:45 +02:00
restund = callPackage ../servers/restund {};
add rethinkdb
2013-11-08 23:45:57 +01:00
rethinkdb = callPackage ../servers/nosql/rethinkdb { };
rippled: initial pkg and module expressions rippled is the Ripple P2P payment network reference server https://ripple.com
2014-03-26 23:12:00 +01:00
rippled = callPackage ../servers/rippled { };
s6: new package s6 is skarnet.org's small & secure supervision software suite. The s6-log program is modified to call execlineb directly rather than searching PATH.
2014-08-23 06:42:13 +02:00
s6 = callPackage ../servers/s6 { };
SpamAssassin: add version 3.3.2
2012-07-08 00:32:30 +02:00
spamassassin = callPackage ../servers/mail/spamassassin {
inherit (perlPackages) HTMLParser NetDNS NetAddrIP DBFile
spamassassin: don't pass 'IOSocketInet6' Adding that package as a build input makes SpamAssassin print "function re-defined" warnings at run-time.
2012-10-07 18:55:07 +02:00
HTTPDate MailDKIM LWP IOSocketSSL;
SpamAssassin: add version 3.3.2
2012-07-08 00:32:30 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
samba = callPackage ../servers/samba { };
wip: kdelibs svn path=/nixpkgs/trunk/; revision=4261
2005-11-12 15:52:16 +01:00
Samba: Add a cross-compilable variant. svn path=/nixpkgs/trunk/; revision=30627
2011-11-29 23:54:00 +01:00
# A lightweight Samba, useful for non-Linux-based OSes.
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
samba_light = lowPrio (callPackage ../servers/samba {
Samba: Add a cross-compilable variant. svn path=/nixpkgs/trunk/; revision=30627
2011-11-29 23:54:00 +01:00
pam = null;
fam = null;
cups = null;
acl = null;
openldap = null;
samba_light: Drop dependency on libunwind. svn path=/nixpkgs/trunk/; revision=33781
2012-04-14 12:26:09 +02:00
# libunwind 1.0.1 is not ported to GNU/Hurd.
libunwind = null;
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
});
wip: kdelibs svn path=/nixpkgs/trunk/; revision=4261
2005-11-12 15:52:16 +01:00
add serfdom (close #1672)
2014-02-27 19:11:08 +01:00
serfdom = callPackage ../servers/serfdom { };
Add seyren, an alerting dashboard for Graphite
2014-03-24 21:05:28 +01:00
seyren = callPackage ../servers/monitoring/seyren { };
GNU Shishi 1.0.1. svn path=/nixpkgs/trunk/; revision=33709
2012-04-09 22:51:54 +02:00
shishi = callPackage ../servers/shishi { };
wip: kdelibs svn path=/nixpkgs/trunk/; revision=4261
2005-11-12 15:52:16 +01:00
Adding GNU SIP Witch. svn path=/nixpkgs/trunk/; revision=25634
2011-01-19 22:17:05 +01:00
sipwitch = callPackage ../servers/sip/sipwitch { };
spawn-fcgi: Add package
2014-05-20 00:50:38 +02:00
spawn_fcgi = callPackage ../servers/http/spawn-fcgi { };
squid update. Proposal for multiple versions svn path=/nixpkgs/trunk/; revision=13666
2008-12-21 17:36:47 +01:00
squids = recurseIntoAttrs( import ../servers/squid/squids.nix {
Adding TFTP-HPA svn path=/nixpkgs/trunk/; revision=28915
2011-08-30 09:02:01 +02:00
inherit fetchurl stdenv perl lib composableDerivation
Move all db4 packages to the default db5
2014-01-31 21:05:37 +01:00
openldap pam db cyrus_sasl kerberos libcap expat libxml2 libtool
Adding TFTP-HPA svn path=/nixpkgs/trunk/; revision=28915
2011-08-30 09:02:01 +02:00
openssl;
squid update. Proposal for multiple versions svn path=/nixpkgs/trunk/; revision=13666
2008-12-21 17:36:47 +01:00
});
Adding TFTP-HPA svn path=/nixpkgs/trunk/; revision=28915
2011-08-30 09:02:01 +02:00
squid = squids.squid31; # has ipv6 support
top-level changes .. svn path=/nixpkgs/trunk/; revision=11829
2008-05-15 19:51:41 +02:00
thttpd: New package, version 2.25b. We already have mini_httpd, but IMHO it is *too* minimal as in not very flexible in configuration (for example, I haven't found any runtime configuration for disabling logging), so that's why I decided to add thttpd, which serves quite well as an ad-hoc HTTPd. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-07-29 07:38:59 +02:00
thttpd = callPackage ../servers/http/thttpd { };
Improved Storm package. - Add config to defaults.yaml, to allow topologies to include their own storm.yaml. - Symlink extra jars in lib/ since it's nearly impossible to add a classpath to Storm's config. - Include native jzmq library in java.library.path - Use package default args.
2013-02-14 09:58:49 +01:00
storm = callPackage ../servers/computing/storm { };
Add storm package.
2013-02-07 15:32:10 +01:00
* Updated Tomcat to 5.0.27. svn path=/nixpkgs/trunk/; revision=24066
2010-10-05 12:39:12 +02:00
tomcat5 = callPackage ../servers/http/tomcat/5.0.nix { };
* MonoDevelop (from SVN). svn path=/nixpkgs/trunk/; revision=2356
2005-03-09 18:49:19 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tomcat6 = callPackage ../servers/http/tomcat/6.0.nix { };
Added Apache Tomcat 6.0 svn path=/nixpkgs/trunk/; revision=10400
2008-01-30 10:41:33 +01:00
Merge pull request #1 from sfultongv/sfultong-14.04 updating tomcat to version 7
2014-08-21 05:02:16 +02:00
tomcat7 = callPackage ../servers/http/tomcat/7.0.nix { };
adding tomcat version 8
2014-08-21 05:23:44 +02:00
tomcat8 = callPackage ../servers/http/tomcat/8.0.nix { };
Merge pull request #1 from sfultongv/sfultong-14.04 updating tomcat to version 7
2014-08-21 05:02:16 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tomcat_mysql_jdbc = callPackage ../servers/http/tomcat/jdbc/mysql { };
Added shared JDBC driver support for tomcat svn path=/nixpkgs/trunk/; revision=12476
2008-08-04 14:04:24 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
axis2 = callPackage ../servers/http/tomcat/axis2 { };
Added Apache Axis2 svn path=/nixpkgs/trunk/; revision=10493
2008-02-04 13:24:41 +01:00
unifi: Add derivation
2014-08-05 23:00:10 +02:00
unifi = callPackage ../servers/unifi { };
Add virtuoso 7 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-09-17 20:28:26 +02:00
virtuoso6 = callPackage ../servers/sql/virtuoso/6.x.nix { };
virtuoso7 = callPackage ../servers/sql/virtuoso/7.x.nix { };
virtuoso = virtuoso6;
Add virtuoso database Very minimal installation needed by KDE svn path=/nixpkgs/trunk/; revision=20932
2010-04-03 19:34:14 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vsftpd = callPackage ../servers/ftp/vsftpd { };
* development/libraries/gnome/*: upgraded all gnome packages to 2.8.3. * development/libraries/gnome/*: copied gtk packages to gnome directory. gnome 2.8.3 did not work on gtk 2.4 nor gtk 2.6. Using the specific version of the gnome platform 2.8.3 directory 'solved' the issue. * development/libraries/gnome/gnome-icon-theme: new packag * development/libraries/gnome/libgtkhtml: new package * development/libraries/gnome/gtkhtml: new package * development/libraries/gnome/libgnomeprint: new package * development/libraries/gnome/libgnomeprintui: new package * development/libraries/gnome/gnome-keyring: new package * development/libraries/gnome/gail: new package * applications/editors/monodoc: new package svn path=/nixpkgs/trunk/; revision=2312
2005-02-27 00:45:19 +01:00
New package: winstone 0.9.10, a Java Servlet container
2014-03-12 22:03:02 +01:00
winstone = callPackage ../servers/http/winstone { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xinetd = callPackage ../servers/xinetd { };
Adding the xinetd package. svn path=/nixpkgs/trunk/; revision=16779
2009-08-19 22:19:17 +02:00
Zookeeper
2014-08-24 17:43:45 +02:00
zookeeper = callPackage ../servers/zookeeper { };
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
xquartz = callPackage ../servers/x11/xquartz { };
quartz-wm = callPackage ../servers/x11/quartz-wm { stdenv = clangStdenv; };
* X.org 7.4. svn path=/nixpkgs/branches/stdenv-updates/; revision=13006
2008-10-08 19:02:48 +02:00
xorg = recurseIntoAttrs (import ../servers/x11/xorg/default.nix {
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
inherit clangStdenv fetchurl fetchgit fetchpatch stdenv pkgconfig intltool freetype fontconfig
xorg: add xf86-video-qxl
2014-08-23 18:54:54 +02:00
libxslt expat libpng zlib perl mesa_drivers spice_protocol
xorg xkeyboard-config: update, unify with the other expression
2014-01-30 13:46:02 +01:00
dbus libuuid openssl gperf m4
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
autoconf automake libtool xmlto asciidoc flex bison python mtdev pixman;
vmware driver: depend on mesa_drivers to find libxatracker
2013-05-22 17:07:12 +02:00
mesa = mesa_noglu;
get xorg/x11 working on Darwin
2014-08-13 02:40:57 +02:00
udev = if stdenv.isLinux then udev else null;
libdrm = if stdenv.isLinux then libdrm else null;
xorg: add "intel-testing" video driver, currently 2.99.911
2014-03-23 21:28:14 +01:00
} // {
xf86videointel-testing = callPackage ../servers/x11/xorg/xf86-video-intel-testing.nix { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
});
source fixed of ilmbase and openexr, blender, openal-soft added (can't compile openal yet on x64) svn path=/nixpkgs/trunk/; revision=9811
2007-12-01 06:56:58 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xorgReplacements = callPackage ../servers/x11/xorg/replacements.nix { };
Made it easy to build custom xf86videoati version svn path=/nixpkgs/trunk/; revision=13112
2008-10-25 09:19:07 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xorgVideoUnichrome = callPackage ../servers/x11/xorg/unichrome/default.nix { };
Adding the Unichrome xorg video driver, and updating the Openchrome. svn path=/nixpkgs/trunk/; revision=18161
2009-11-05 22:34:31 +01:00
Add yaws, an Erlang HTTP server
2013-02-20 22:34:55 +01:00
yaws = callPackage ../servers/http/yaws { };
* Zabbix updated to 1.8.1. svn path=/nixpkgs/trunk/; revision=20009
2010-02-15 15:20:28 +01:00
zabbix = recurseIntoAttrs (import ../servers/monitoring/zabbix {
inherit fetchurl stdenv pkgconfig postgresql curl openssl zlib;
});
* Added Zabbix, a system and network monitoring tool. svn path=/nixpkgs/trunk/; revision=11963
2008-06-03 23:59:35 +02:00
zabbix2: Add optional XMPP support using iksemel. This uses recurseForDerivations directly after using callPackage magic to ensure that the input attributes can be overriden *and* nix-env shows the package as in recurseIntoAttrs. The reason for making this optional is because there probably is only a minority of people who want to use XMPP and we don't want to introduce an additional dependency for the majority, do we? Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-06-21 11:34:46 +02:00
zabbix20 = callPackage ../servers/monitoring/zabbix/2.0.nix { };
Add zabbix 2.2.1
2014-01-07 13:11:32 +01:00
zabbix22 = callPackage ../servers/monitoring/zabbix/2.2.nix { };
Add zabbix 2.0.3
2012-12-02 15:28:08 +01:00
Openbabel added. There are some TODO's in its nix-expression. svn path=/nixpkgs/trunk/; revision=9635
2007-11-11 17:15:29 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### OS-SPECIFIC
exrviewer added (needs ctl openexr openexr_ctl) fltk update ilmbase updated ndiswrapper does compile but has to be integrated into the kernel somehow svn path=/nixpkgs/trunk/; revision=9863
2007-12-05 22:25:47 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
afuse = callPackage ../os-specific/linux/afuse { };
adding afuse. A userspace automounter svn path=/nixpkgs/trunk/; revision=19063
2009-12-21 09:55:27 +01:00
Move the AMD microcode to the microcode directory
2013-08-14 03:26:04 +02:00
amdUcode = callPackage ../os-specific/linux/microcode/amd.nix { };
amd-ucode: add AMD processor microcode patch version 2012-01-17 Enable by adding "hardware.firmware = [ pkgs.amdUcode ];" to configuration.nix.
2012-06-28 19:54:24 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
autofs5 = callPackage ../os-specific/linux/autofs/autofs-v5.nix { };
adding automount 5 svn path=/nixpkgs/trunk/; revision=15410
2009-04-30 04:37:00 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
_915resolution = callPackage ../os-specific/linux/915resolution { };
* Added openldap and pam_ldap. svn path=/nixpkgs/trunk/; revision=7641
2007-01-11 22:55:29 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nfsUtils = callPackage ../os-specific/linux/nfs-utils { };
* Added gtksourceview and gtksourceview-sharp. svn path=/nixpkgs/trunk/; revision=2344
2005-03-08 16:44:23 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
acpi = callPackage ../os-specific/linux/acpi { };
Add ACPI, a tiny ACPI client tool for Linux svn path=/nixpkgs/trunk/; revision=10820
2008-02-21 21:13:36 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
acpid = callPackage ../os-specific/linux/acpid { };
* Added acpid, a daemon that monitors ACPI events. svn path=/nixpkgs/trunk/; revision=14026
2009-02-11 00:12:18 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
acpitool = callPackage ../os-specific/linux/acpitool { };
Add ACPI-Tool, a command-line ACPI client for Linux. svn path=/nixpkgs/trunk/; revision=10819
2008-02-21 20:57:40 +01:00
Add alienfx. Only tested with M11x Made some corrections. Added meta-data Use more of the original makefile 2 space indent
2013-11-21 05:36:57 +01:00
alienfx = callPackage ../os-specific/linux/alienfx { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
alsaLib = callPackage ../os-specific/linux/alsa-lib { };
all-packages.nix: commented out package 'vice' error: getting status of `/usr/local/src/nix-pkgs-current/pkgs/misc/emulators/vice': No such file or directory svn path=/nixpkgs/trunk/; revision=15646
2009-05-18 15:53:01 +02:00
* alsa-plugins updated to 1.0.24. svn path=/nixpkgs/branches/kde-4.7/; revision=27956
2011-07-26 02:05:10 +02:00
alsaPlugins = callPackage ../os-specific/linux/alsa-plugins {
jack: change package and attr names to 'jack1' and 'jack2' Currently, we have a 'jack' package with attrname 'jack1d' and a 'jackdbus' package with attrname 'jackaudio'. Make it consistent 'jack1' and 'jack2' in both package name and attrname. This aligns the naming with what can be found on the JACK homepage. Q: what's the difference between jack1 and jack2? A: http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2
2014-07-22 22:06:44 +02:00
jack2 = null;
* alsa-plugins updated to 1.0.24. svn path=/nixpkgs/branches/kde-4.7/; revision=27956
2011-07-26 02:05:10 +02:00
};
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28462
2011-08-10 17:51:20 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
alsaPluginWrapper = callPackage ../os-specific/linux/alsa-plugins/wrapper.nix { };
adding alsa-plugin and patching alsa so that you can tell it about additional plugins svn path=/nixpkgs/trunk/; revision=17316
2009-09-20 23:54:23 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
alsaUtils = callPackage ../os-specific/linux/alsa-utils { };
add alsa oss emulation
2013-01-28 02:48:57 +01:00
alsaOss = callPackage ../os-specific/linux/alsa-oss { };
- svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10823
2008-02-22 04:06:12 +01:00
Improved the expression for intel microcode. svn path=/nixpkgs/trunk/; revision=32042
2012-02-05 21:44:19 +01:00
microcode2ucode = callPackage ../os-specific/linux/microcode/converter.nix { };
Update of skype expression: make the use of pulse audio optional based on the configuration setting for pulse audio (off by default). Removing pulse audio from the build inputs when it is not used prevents the bug of Skype taking 100% cpu from showing up. This demonstrates nicely nix' features: in other distributions the recomended solution was to remove read permission from the pulse audio libs. svn path=/nixpkgs/trunk/; revision=31959
2012-02-01 23:09:35 +01:00
microcodeIntel = callPackage ../os-specific/linux/microcode/intel.nix { };
Apparmor: packaged svn path=/nixpkgs/trunk/; revision=32695
2012-02-29 14:30:10 +01:00
apparmor = callPackage ../os-specific/linux/apparmor {
inherit (perlPackages) LocaleGettext TermReadKey RpcXML;
apparmor: build with bison 2.x; version 3.x causes compiler errors
2014-01-25 20:57:17 +01:00
bison = bison2;
Apparmor: packaged svn path=/nixpkgs/trunk/; revision=32695
2012-02-29 14:30:10 +01:00
};
Atop: add package (atop is one more load monitor)
2012-08-25 19:24:17 +02:00
atop = callPackage ../os-specific/linux/atop { };
Add audit 2.3.2 for the new libsemanage
2013-11-28 10:09:28 +01:00
audit = callPackage ../os-specific/linux/audit { };
Add b43-firmware-5.100.138 Placed into a versioned nix file because kernels older than 3.2 need an older version.
2012-07-14 00:31:09 +02:00
b43Firmware_5_1_138 = callPackage ../os-specific/linux/firmware/b43-firmware/5.1.138.nix { };
Add b43-firmware-cutter
2012-07-14 00:00:00 +02:00
b43FirmwareCutter = callPackage ../os-specific/linux/firmware/b43-firmware-cutter { };
Adding batctl, control for batman
2013-05-28 23:02:22 +02:00
batctl = callPackage ../os-specific/linux/batman-adv/batctl.nix { };
Adding pygobject3 (for bluez4). bluez-simple-agent fails to work otherwise. We discussed this a bit on #486, and this looks like the simplest way to get bluez-simple-agent again.
2013-05-09 21:11:30 +02:00
bluez4 = callPackage ../os-specific/linux/bluez {
pygobject = pygobject3;
};
bluez5: mark bluez5 with loPrio
2013-03-19 09:30:39 +01:00
bluez5 = lowPrio (callPackage ../os-specific/linux/bluez/bluez5.nix { });
bluez5: add experimental expression for bluez5 bluez5 has many changes relative to bluez4. Most notable are dependency on linux-3.4 and new dbus API.
2013-03-13 21:46:30 +01:00
bluez = bluez4;
* Added bluez, the Bluetooth stack for Linux. svn path=/nixpkgs/trunk/; revision=16594
2009-08-05 22:29:36 +02:00
bedup: add top-level attribute Currently I see no standard way of having package name without the "pythonX.Y-" prefix. This is replacement to #2339.
2014-05-11 14:29:13 +02:00
inherit (pythonPackages) bedup;
Add beret game svn path=/nixpkgs/trunk/; revision=30954
2011-12-19 03:13:38 +01:00
beret = callPackage ../games/beret { };
* bridge-utils updated to 1.4. svn path=/nixpkgs/trunk/; revision=23778
2010-09-14 12:54:50 +02:00
bridge_utils = callPackage ../os-specific/linux/bridge-utils { };
* Added `zapping', a TV viewer application. It depends on Gnome, so lots of packages are needed. svn path=/nixpkgs/trunk/; revision=681
2004-01-21 10:34:19 +01:00
busybox: Update to 1.20.1
2012-06-28 20:05:27 +02:00
busybox = callPackage ../os-specific/linux/busybox { };
checkpolicy: packaged svn path=/nixpkgs/trunk/; revision=26538
2011-03-27 06:45:46 +02:00
checkpolicy = callPackage ../os-specific/linux/checkpolicy { };
checksec: version 1.5 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-02-19 12:48:46 +01:00
checksec = callPackage ../os-specific/linux/checksec { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cifs_utils = callPackage ../os-specific/linux/cifs-utils { };
* Added cifs-utils (mount.cifs properly packaged). This obsoletes mount-cifs. svn path=/nixpkgs/trunk/; revision=22124
2010-06-03 16:28:48 +02:00
conky: add config options
2014-03-14 23:39:56 +01:00
conky = callPackage ../os-specific/linux/conky {
mpdSupport = config.conky.mpdSupport or true;
x11Support = config.conky.x11Support or false;
xdamage = config.conky.xdamage or false;
wireless = config.conky.wireless or false;
luaSupport = config.conky.luaSupport or false;
rss = config.conky.rss or false;
weatherMetar = config.conky.weatherMetar or false;
weatherXoap = config.conky.weatherXoap or false;
};
conky: compiled without X support, usefull with dwm. svn path=/nixpkgs/trunk/; revision=22015
2010-05-27 21:33:58 +02:00
* Add cpufrequtils to the channel. svn path=/nixpkgs/trunk/; revision=31017
2011-12-21 17:24:40 +01:00
cpufrequtils = callPackage ../os-specific/linux/cpufrequtils { };
Committing Lluís Batlle's submissions from mailing list posting <45219fb00901110456i6f21db35tbd1894eaea2146ff@mail.gmail.com>: * nixpkgs-ccrypt-1.7-new.patch * nixpkgs-cmake-add-ccmake.patch * nixpkgs-cpufrequtils-005-new.patch * nixpkgs-dwm-5.1-fix.patch * nixpkgs-freeimage-3.11.0-new.patch * nixpkgs-proxychains-3.1-new.patch * nixpkgs-psi-to-0.12.patch * nixpkgs-skype-to-2.0.0.72.patch * nixpkgs-truecrypt-6.1a-fix.patch * nixpkgs-vxl-1.11.0-new.patch * nixpkgs-xkb-popular-esperanto-symbols.patch * nixpkgs-xorg-via-video-fix.patch svn path=/nixpkgs/trunk/; revision=13751
2009-01-12 22:12:07 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cryopid = callPackage ../os-specific/linux/cryopid { };
* Added cryopid (contributed by Marco Maggesi). svn path=/nixpkgs/trunk/; revision=13291
2008-11-14 13:34:18 +01:00
criu: version 1.2 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-02-27 08:05:20 +01:00
criu = callPackage ../os-specific/linux/criu { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cryptsetup = callPackage ../os-specific/linux/cryptsetup { };
Adding LUKS cryptsetup for the devicemapper. svn path=/nixpkgs/trunk/; revision=14289
2009-03-01 12:11:21 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cramfsswap = callPackage ../os-specific/linux/cramfsswap { };
* Added `zapping', a TV viewer application. It depends on Gnome, so lots of packages are needed. svn path=/nixpkgs/trunk/; revision=681
2004-01-21 10:34:19 +01:00
darwin: Add new package maloader. This is the mentioned Mach-O loader that we're yoing to use to execute Apple's proprietary binaries. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 22:02:46 +01:00
darwin = rec {
Add a cross-platform port of cctools. This basically is binutils for Mac OS X, but ported to work on (GNU/)Linux and FreeBSD. And it's up-to-date as well! I'm mentioning this, because it was quite hard to find a recent port of it and I just accidentally stumbled on it while trying to do the port by myself. So thanks to @tpoechtrager for doing this. Also, I've added two more patches, which essentially are: * ld-rpath-nonfinal: This allows -rpath to be used for linking non-final builds, which was allowed for earlier versions of cctools and got a check for that in more recent versions. * ld-ignore-rpath-link: Ignores the -rpath-link option, because the cross-wrapper uses it in different places. Unfortunately, the cctools linker doesn't support it, so we might need to implement this later if it's possible (I'm not a Mach-O man^H^H^Hexpert). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 03:57:48 +01:00
cctools = forceNativeDrv (callPackage ../os-specific/darwin/cctools-port {
cross = assert crossSystem != null; crossSystem;
cctools-port: Pass through wrapped XCToolchain. At the moment, this includes only dyldinfo, dwarfdump and dsymutil, but we'll see whether we need more of these utilities later. Tho reason those are wrapped in cctools-port is because it is the binutils used to cross-compile for Mac OS X. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 22:08:51 +01:00
inherit maloader;
xctoolchain = xcode.toolchain;
Add a cross-platform port of cctools. This basically is binutils for Mac OS X, but ported to work on (GNU/)Linux and FreeBSD. And it's up-to-date as well! I'm mentioning this, because it was quite hard to find a recent port of it and I just accidentally stumbled on it while trying to do the port by myself. So thanks to @tpoechtrager for doing this. Also, I've added two more patches, which essentially are: * ld-rpath-nonfinal: This allows -rpath to be used for linking non-final builds, which was allowed for earlier versions of cctools and got a check for that in more recent versions. * ld-ignore-rpath-link: Ignores the -rpath-link option, because the cross-wrapper uses it in different places. Unfortunately, the cctools linker doesn't support it, so we might need to implement this later if it's possible (I'm not a Mach-O man^H^H^Hexpert). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 03:57:48 +01:00
});
darwin: Add new package maloader. This is the mentioned Mach-O loader that we're yoing to use to execute Apple's proprietary binaries. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 22:02:46 +01:00
maloader = callPackage ../os-specific/darwin/maloader {
inherit opencflite;
};
darwin: Add new package opencflite. This provides a port of Mac OS X's CoreFoundation and is needed if we want to be able to run dsymutil using maloader. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 21:59:26 +01:00
opencflite = callPackage ../os-specific/darwin/opencflite {};
Add a cross-platform port of cctools. This basically is binutils for Mac OS X, but ported to work on (GNU/)Linux and FreeBSD. And it's up-to-date as well! I'm mentioning this, because it was quite hard to find a recent port of it and I just accidentally stumbled on it while trying to do the port by myself. So thanks to @tpoechtrager for doing this. Also, I've added two more patches, which essentially are: * ld-rpath-nonfinal: This allows -rpath to be used for linking non-final builds, which was allowed for earlier versions of cctools and got a check for that in more recent versions. * ld-ignore-rpath-link: Ignores the -rpath-link option, because the cross-wrapper uses it in different places. Unfortunately, the cctools linker doesn't support it, so we might need to implement this later if it's possible (I'm not a Mach-O man^H^H^Hexpert). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 03:57:48 +01:00
xcode = callPackage ../os-specific/darwin/xcode {};
};
Add new package for Apple's XCode. This package provides the SDK and standard library needed for cross-compiling to Mac US X. We're using xpwn here to extract the DMG. Also, this version (XCode 5.0.2) only contains the SDKs for version 10.9 and 10.8, so we might need to add requireFile directives for older versions as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-10 03:39:33 +01:00
* Updated LVM2 to 2.02.56. LVM2 now includes device-mapper, so that package is obsolete. Also install the udev rules. svn path=/nixpkgs/trunk/; revision=19293
2010-01-07 17:14:10 +01:00
devicemapper = lvm2;
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
disk-indicator: Add package A program that will turn a LED into a hard disk indicator.
2014-05-30 17:56:05 +02:00
disk_indicator = callPackage ../os-specific/linux/disk-indicator { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dmidecode = callPackage ../os-specific/linux/dmidecode { };
Added dmidecode and kqemu svn path=/nixpkgs/trunk/; revision=10098
2008-01-08 01:18:20 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dmtcp = callPackage ../os-specific/linux/dmtcp { };
Add new package pkgs/os-specific/linux/dmtcp/ svn path=/nixpkgs/trunk/; revision=19819
2010-02-04 16:41:45 +01:00
Minor cleanup
2012-11-29 14:40:25 +01:00
dietlibc = callPackage ../os-specific/linux/dietlibc { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Fix wxGTK reference for xchm svn path=/nixpkgs/trunk/; revision=18156
2009-11-05 22:08:53 +01:00
directvnc = builderDefsPackage ../os-specific/linux/directvnc {
inherit libjpeg pkgconfig zlib directfb;
inherit (xlibs) xproto;
};
Make dmeventd support in lvm2 optional; use it for dmraid
2014-09-01 00:06:41 +02:00
dmraid = callPackage ../os-specific/linux/dmraid {
devicemapper = devicemapper.override {enable_dmeventd = true;};
};
Adding dmraid svn path=/nixpkgs/trunk/; revision=17292
2009-09-20 10:38:30 +02:00
* Added drbd. svn path=/nixpkgs/trunk/; revision=30163
2011-11-01 16:21:31 +01:00
drbd = callPackage ../os-specific/linux/drbd { };
all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=30399
2011-11-12 23:19:11 +01:00
dstat: enable color output Give dstat access to the "curses" module in the Python standard library so that it can color its output. This is similar to how other distros package it (e.g. Fedora, Ubuntu).
2013-08-30 18:43:54 +02:00
dstat = callPackage ../os-specific/linux/dstat {
# pythonFull includes the "curses" standard library module, for pretty
# dstat color output
python = pythonFull;
};
add package dstat
2012-08-05 14:55:44 +02:00
Add new package libossp-uuid-1.6.2
2014-01-18 20:54:52 +01:00
libossp_uuid = callPackage ../development/libraries/libossp-uuid { };
libuuid: Make cross-buildable for GNU/Hurd (needed by GNU Parted). svn path=/nixpkgs/trunk/; revision=23415
2010-08-25 10:57:10 +02:00
libuuid =
if crossSystem != null && crossSystem.config == "i586-pc-gnu"
* util-linux 2.20.1. svn path=/nixpkgs/branches/stdenv-updates/; revision=30860
2011-12-12 20:56:17 +01:00
then (utillinux // {
Rename hostDrv -> crossDrv, buildDrv -> nativeDrv This is for consistency with terminology in stdenv (and the terms "hostDrv" and "buildDrv" are not very intuitive, even if they're consistent with GNU terminology).
2012-12-28 19:08:19 +01:00
crossDrv = lib.overrideDerivation utillinux.crossDrv (args: {
libuuid: Make cross-buildable for GNU/Hurd (needed by GNU Parted). svn path=/nixpkgs/trunk/; revision=23415
2010-08-25 10:57:10 +02:00
# `libblkid' fails to build on GNU/Hurd.
configureFlags = args.configureFlags
libuuid: Fix cross-GNU builds. svn path=/nixpkgs/branches/stdenv-updates/; revision=25087
2010-12-13 00:21:29 +01:00
+ " --disable-libblkid --disable-mount --disable-libmount"
util-linux: Use `--disable-partx' when cross-building for GNU. svn path=/nixpkgs/branches/stdenv-updates/; revision=32729
2012-03-01 22:48:29 +01:00
+ " --disable-fsck --enable-static --disable-partx";
libuuid: Make cross-buildable for GNU/Hurd (needed by GNU Parted). svn path=/nixpkgs/trunk/; revision=23415
2010-08-25 10:57:10 +02:00
doCheck = false;
CPPFLAGS = # ugly hack for ugly software!
lib.concatStringsSep " "
(map (v: "-D${v}=4096")
[ "PATH_MAX" "MAXPATHLEN" "MAXHOSTNAMELEN" ]);
});
})
else if stdenv.isLinux
* util-linux 2.20.1. svn path=/nixpkgs/branches/stdenv-updates/; revision=30860
2011-12-12 20:56:17 +01:00
then utillinux
libuuid: Make cross-buildable for GNU/Hurd (needed by GNU Parted). svn path=/nixpkgs/trunk/; revision=23415
2010-08-25 10:57:10 +02:00
else null;
* Fixed ntfsprogs. svn path=/nixpkgs/trunk/; revision=14695
2009-03-25 11:55:28 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
e3cfsprogs = callPackage ../os-specific/linux/e3cfsprogs { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Added ebtables. svn path=/nixpkgs/branches/modular-python/; revision=26626
2011-03-31 14:20:22 +02:00
ebtables = callPackage ../os-specific/linux/ebtables { };
eject: Remove This command is part of util-linux now.
2013-01-28 17:25:59 +01:00
eject = utillinux;
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Adding ffado, Linux Firewire audio drivers svn path=/nixpkgs/trunk/; revision=33634
2012-04-05 23:53:42 +02:00
ffado = callPackage ../os-specific/linux/ffado { };
Update FBTerm to current URL of tarball
2012-12-04 08:47:40 +01:00
fbterm = callPackage ../os-specific/linux/fbterm { };
Adding a fbterm variant building with stdenv to get cross-build-ability (I want it in the nanonote) svn path=/nixpkgs/branches/stdenv-updates/; revision=24880
2010-11-26 18:56:23 +01:00
Add Firejail cheap-sandbox-building package
2014-08-18 00:18:20 +02:00
firejail = callPackage ../os-specific/linux/firejail {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fuse = callPackage ../os-specific/linux/fuse { };
* Converted some more packages. * Subversion no longer needs libxml2 (just expat). svn path=/nixpkgs/trunk/; revision=478
2003-11-05 13:17:48 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fxload = callPackage ../os-specific/linux/fxload { };
* Added fxload, a tool to upload firmware to Cypress EZ-USB microcontrollers. svn path=/nixpkgs/trunk/; revision=10483
2008-02-03 15:43:19 +01:00
Adding desktop side of GfxTablet tablet-as-input-device Android app
2013-10-22 07:30:49 +02:00
gfxtablet = callPackage ../os-specific/linux/gfxtablet {};
Making the current versions of flex/bison the default. Evaluation test passes. Please explicitly pass older versions to any package that can be adversely affected by too-fresh versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=25086
2010-12-12 22:48:29 +01:00
gpm = callPackage ../servers/gpm { };
LZMA support in builderDefs; gpm added svn path=/nixpkgs/trunk/; revision=11874
2008-05-21 15:27:41 +02:00
gradm: Attempt to fix build failure by using older flex Thanks to @thoughtpolice for noticing and suggesting the fix!
2014-04-11 16:36:02 +02:00
gradm = callPackage ../os-specific/linux/gradm {
flex = flex_2_5_35;
};
grsecurity: add gradm-3.0-201401291757 This also ensures the appropriate udev rules are installed. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-02-17 15:23:31 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hdparm = callPackage ../os-specific/linux/hdparm { };
Add `hibernate', an swsusp/Tux-on-Ice convenience script. svn path=/nixpkgs/trunk/; revision=11438
2008-04-01 16:02:54 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hibernate = callPackage ../os-specific/linux/hibernate { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
hostapd: packaged. svn path=/nixpkgs/trunk/; revision=27501
2011-06-20 01:30:57 +02:00
hostapd = callPackage ../os-specific/linux/hostapd { };
add htop fork for darwin (close #2690) @vcunat made it a single conditional attribute. Conflicts (trivial): lib/maintainers.nix
2014-05-17 01:28:19 +02:00
htop =
if stdenv.isLinux then
callPackage ../os-specific/linux/htop { }
else if stdenv.isDarwin then
callPackage ../os-specific/darwin/htop { }
else null;
* vlc and required packages. Finally a good DVD player :-) svn path=/nixpkgs/trunk/; revision=574
2003-12-03 22:58:16 +01:00
Move GNU/Hurd package attributes under `os-specific/gnu/default.nix'. svn path=/nixpkgs/trunk/; revision=30173
2011-11-01 23:10:51 +01:00
# GNU/Hurd core packages.
gnu = recurseIntoAttrs (callPackage ../os-specific/gnu {
inherit platform crossSystem;
GNU Hurd: Add libpthread. svn path=/nixpkgs/trunk/; revision=21900
2010-05-19 23:28:57 +02:00
});
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hwdata = callPackage ../os-specific/linux/hwdata { };
Added qt-4 svn path=/nixpkgs/trunk/; revision=8991
2007-07-17 19:08:38 +02:00
i7z: better cpu frequency/turbo boost checker for intel core i{3,5,7} svn path=/nixpkgs/trunk/; revision=32082
2012-02-06 20:09:04 +01:00
i7z = callPackage ../os-specific/linux/i7z { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ifplugd = callPackage ../os-specific/linux/ifplugd { };
* Cleanup. svn path=/nixpkgs/trunk/; revision=6764
2006-10-18 16:04:55 +02:00
iomelt: new package This adds the IOMelt pacakge, "a simple yet effective way to benchmark disk IO in Linux systems."
2014-06-30 05:57:55 +02:00
iomelt = callPackage ../os-specific/linux/iomelt { };
* iotop: don't use pythonFull. svn path=/nixpkgs/branches/modular-python/; revision=26567
2011-03-28 15:23:52 +02:00
iotop = callPackage ../os-specific/linux/iotop { };
Adding IOtop svn path=/nixpkgs/trunk/; revision=24818
2010-11-23 08:46:18 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iproute = callPackage ../os-specific/linux/iproute { };
* vlc and required packages. Finally a good DVD player :-) svn path=/nixpkgs/trunk/; revision=574
2003-12-03 22:58:16 +01:00
Adding the sgml dtd for docbook 3.1 Required by iputils manpages.
2013-03-18 15:05:08 +01:00
iputils = callPackage ../os-specific/linux/iputils {
sp = spCompat;
inherit (perlPackages) SGMLSpm;
};
Added redland library (also known as librdf) svn path=/nixpkgs/trunk/; revision=9390
2007-10-01 17:14:50 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iptables = callPackage ../os-specific/linux/iptables { };
* vlc and required packages. Finally a good DVD player :-) svn path=/nixpkgs/trunk/; revision=574
2003-12-03 22:58:16 +01:00
Adding linux iw.
2012-08-11 19:54:44 +02:00
iw = callPackage ../os-specific/linux/iw { };
jujuutils: fix reference to non-existent version of 'linuxHeaders' Plus minor cosmetic changes to the expression.
2012-10-23 18:47:31 +02:00
jujuutils = callPackage ../os-specific/linux/jujuutils { };
Adding jujuutils. svn path=/nixpkgs/trunk/; revision=34020
2012-05-08 17:31:21 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
kbd = callPackage ../os-specific/linux/kbd { };
Added pygame and some of its dependencies. Also added Python Imaging library. svn path=/nixpkgs/trunk/; revision=9082
2007-08-09 19:33:18 +02:00
Add kmscon, a kms-based replacement for kernel VTs Note that currently this depends on the default nixpkgs mesa and pango. It may be possible to build more limited versions that don't e.g. depend on the full X stack without limiting kmscon (which of course doesn't use X). Depends on libtsm, added in the same commit. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-15 06:58:46 +01:00
kmscon = callPackage ../os-specific/linux/kmscon { };
Adding latencytop. svn path=/nixpkgs/trunk/; revision=33233
2012-03-18 12:45:53 +01:00
latencytop = callPackage ../os-specific/linux/latencytop { };
New package: LDM - Lightweight device mounter Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-11-10 14:30:01 +01:00
ldm = callPackage ../os-specific/linux/ldm { };
* Added libaio. svn path=/nixpkgs/trunk/; revision=26715
2011-04-06 16:21:48 +02:00
libaio = callPackage ../os-specific/linux/libaio { };
* Added udisks, the replacement of the disk management bits of HAL (which is obsolete). * lvm2: updated to 2.02.86. Also install the pkgconfig files and build liblvm2app. * Added libatasmart (udisks dependency for querying ATA SMART status). * Updated sg3_utils to 1.31. svn path=/nixpkgs/branches/kde-4.7/; revision=27908
2011-07-23 03:29:51 +02:00
libatasmart = callPackage ../os-specific/linux/libatasmart { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28462
2011-08-10 17:51:20 +02:00
* Move libcgroup from libcg/ to libcgroup/. svn path=/nixpkgs/trunk/; revision=30547
2011-11-24 14:48:16 +01:00
libcgroup = callPackage ../os-specific/linux/libcgroup { };
libcgroup: library that abstracts the control group file system in Linux. svn path=/nixpkgs/trunk/; revision=22548
2010-07-09 15:15:51 +02:00
Making the current versions of flex/bison the default. Evaluation test passes. Please explicitly pass older versions to any package that can be adversely affected by too-fresh versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=25086
2010-12-12 22:48:29 +01:00
libnl = callPackage ../os-specific/linux/libnl { };
Adding libnl 3.2.19 to use instead of the latest with ntrack ntrack has a bug about fresher libnl compatilbility. There are no updates since September.
2013-12-02 19:47:52 +01:00
libnl_3_2_19 = callPackage ../os-specific/linux/libnl/3.2.19.nix { };
Add Netlink library svn path=/nixpkgs/trunk/; revision=24996
2010-12-06 13:04:36 +01:00
Merge branch 'master' into stdenv-updates. Conflicts have been resolved in: pkgs/tools/misc/file/default.nix pkgs/top-level/all-packages.nix pkgs/top-level/python-packages.nix
2012-11-21 16:20:36 +01:00
linuxConsoleTools = callPackage ../os-specific/linux/consoletools { };
* Some VLC-related updates. * Variability :-) Provide both Autoconf 2.59 and 2.60 (the former being the default for now). svn path=/nixpkgs/trunk/; revision=5539
2006-06-29 14:41:25 +02:00
grsec: refactor grsecurity packages This now provides a handful of different grsecurity kernels for slightly different 'flavors' of packages. This doesn't change the grsecurity module to use them just yet, however. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-14 19:04:40 +02:00
# -- Linux kernel expressions ------------------------------------------------
linux-headers: Add 3.14
2014-04-15 16:59:19 +02:00
linuxHeaders = linuxHeaders_3_7;
The jujuutils are meant for a recent kernel, more recent than our linuxHeaders. Therefore I add recent linuxHeaders for it. It's quite a hack to build it mixed with 2.6.35 headers and 3.3.5, but it builds at least. svn path=/nixpkgs/trunk/; revision=34021
2012-05-08 18:38:21 +02:00
linux-headers-2.6.28: Remove, no longer used
2014-04-15 16:50:29 +02:00
linuxHeaders24Cross = forceNativeDrv (import ../os-specific/linux/kernel-headers/2.4.nix {
I removed the function-shape of the cross-toolchain related attributes in the all-packages.nix. That was more complicating than helping. svn path=/nixpkgs/trunk/; revision=20457
2010-03-07 00:36:55 +01:00
inherit stdenv fetchurl perl;
Adding assertions for the cross-toolchain attributes, so noone feels tempted to build them without setting a crossSystem to build for. svn path=/nixpkgs/trunk/; revision=20459
2010-03-07 01:05:51 +01:00
cross = assert crossSystem != null; crossSystem;
Big fixes in the cross build: - Before this changes, cflags and ldflags for the native and the cross compiler got mixed. Not all the gcc-wrapper/gcc-cross-wrapper variables are independant now, but enough, I think. - Fixed the generic stdenv expression, which did a big mess on buildInputs and buildNativeInputs. Now it distinguishes when there is a stdenvCross or not. Maybe we should have a single stdenv and forget about the stdenvCross adapter - this could end in a stdenv a bit complex, but simpler than the generic stdenv + adapter. - Added basic support in pkgconfig for cross-builds: a single PKG_CONFIG_PATH now works for both the cross and the native compilers, but I think this should work well for most cases I can think of. - I tried to fix the guile expression to cross-biuld; guile is built, but not its manual, so the derivation still fails. Guile requires patching to cross-build, as far as I understnad. - Made the glibcCross build to be done through the usage of a gcc-cross-wrapper over the gcc-cross-stage-static, instead of using it directly. - Trying to make physfs (a neverball dependency) cross build. - Updated the gcc expression to support building a cross compiler without getting derivation variables mixed with those of the stdenvCross. svn path=/nixpkgs/branches/stdenv-updates/; revision=18534
2009-11-22 20:51:45 +01:00
});
My first attempt at getting cross compilers in nixpkgs. My idea is to provide special stdenv expressions that will contain in the path additional cross compilers. As most expressions for programs accept a stdenv parameter, we could substitute this parameter with the special stdenv, which will have a generic builder that attempts the usual "--target=..." and can additionally have an env variable like "cross" with the target architecture set. So, finally we could have additional expressions like this: bashRealArm = makeOverridable (import ../shells/bash) { inherit fetchurl bison; stdenv = stdenvCross "armv5tel-unknown-linux-gnueabi"; }; Meanwhile it does not work - I still cannot get the cross-gcc to build. I think it does not fill the previous expressions with a lot of noise, so I think it may be a good path to follow. I only touched some files of the current stdenv: gcc-4.3, kernel headers 2.6.28, glibc 2.9, ... I tried to use the gcc-cross-wrapper, that may be very outdated. Maybe I will update it, or update the gcc-wrapper expression to make it fit the cross tools, but meanwhile I even cannot build gcc, so I have not tested the wrapper. This new idea on cross compiling is not similar to that of the nixpkgs/branches/cross-compilation, which mostly added bare new expressions for anything to be cross compiled, if I understood it correctly. I cared not to break anything of the usual stdenv in all this work. svn path=/nixpkgs/branches/stdenv-updates/; revision=18343
2009-11-14 09:11:30 +01:00
linux-headers-2.6.28: Remove, no longer used
2014-04-15 16:50:29 +02:00
linuxHeaders26Cross = forceNativeDrv (import ../os-specific/linux/kernel-headers/2.6.32.nix {
I removed the function-shape of the cross-toolchain related attributes in the all-packages.nix. That was more complicating than helping. svn path=/nixpkgs/trunk/; revision=20457
2010-03-07 00:36:55 +01:00
inherit stdenv fetchurl perl;
Adding assertions for the cross-toolchain attributes, so noone feels tempted to build them without setting a crossSystem to build for. svn path=/nixpkgs/trunk/; revision=20459
2010-03-07 01:05:51 +01:00
cross = assert crossSystem != null; crossSystem;
Big fixes in the cross build: - Before this changes, cflags and ldflags for the native and the cross compiler got mixed. Not all the gcc-wrapper/gcc-cross-wrapper variables are independant now, but enough, I think. - Fixed the generic stdenv expression, which did a big mess on buildInputs and buildNativeInputs. Now it distinguishes when there is a stdenvCross or not. Maybe we should have a single stdenv and forget about the stdenvCross adapter - this could end in a stdenv a bit complex, but simpler than the generic stdenv + adapter. - Added basic support in pkgconfig for cross-builds: a single PKG_CONFIG_PATH now works for both the cross and the native compilers, but I think this should work well for most cases I can think of. - I tried to fix the guile expression to cross-biuld; guile is built, but not its manual, so the derivation still fails. Guile requires patching to cross-build, as far as I understnad. - Made the glibcCross build to be done through the usage of a gcc-cross-wrapper over the gcc-cross-stage-static, instead of using it directly. - Trying to make physfs (a neverball dependency) cross build. - Updated the gcc expression to support building a cross compiler without getting derivation variables mixed with those of the stdenvCross. svn path=/nixpkgs/branches/stdenv-updates/; revision=18534
2009-11-22 20:51:45 +01:00
});
My first attempt at getting cross compilers in nixpkgs. My idea is to provide special stdenv expressions that will contain in the path additional cross compilers. As most expressions for programs accept a stdenv parameter, we could substitute this parameter with the special stdenv, which will have a generic builder that attempts the usual "--target=..." and can additionally have an env variable like "cross" with the target architecture set. So, finally we could have additional expressions like this: bashRealArm = makeOverridable (import ../shells/bash) { inherit fetchurl bison; stdenv = stdenvCross "armv5tel-unknown-linux-gnueabi"; }; Meanwhile it does not work - I still cannot get the cross-gcc to build. I think it does not fill the previous expressions with a lot of noise, so I think it may be a good path to follow. I only touched some files of the current stdenv: gcc-4.3, kernel headers 2.6.28, glibc 2.9, ... I tried to use the gcc-cross-wrapper, that may be very outdated. Maybe I will update it, or update the gcc-wrapper expression to make it fit the cross tools, but meanwhile I even cannot build gcc, so I have not tested the wrapper. This new idea on cross compiling is not similar to that of the nixpkgs/branches/cross-compilation, which mostly added bare new expressions for anything to be cross compiled, if I understood it correctly. I cared not to break anything of the usual stdenv in all this work. svn path=/nixpkgs/branches/stdenv-updates/; revision=18343
2009-11-14 09:11:30 +01:00
linux-headers: Add 3.14
2014-04-15 16:59:19 +02:00
linuxHeaders_3_7 = callPackage ../os-specific/linux/kernel-headers/3.7.nix { };
linuxHeaders_3_14 = callPackage ../os-specific/linux/kernel-headers/3.14.nix { };
linux-headers-2.6.28: Remove, no longer used
2014-04-15 16:50:29 +02:00
Adding linux 2.4 kernel headers for cross builds. (I'm thinking of OpenWRT machines out there, mips, with linux 2.4) svn path=/nixpkgs/trunk/; revision=20539
2010-03-10 21:44:48 +01:00
# We can choose:
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
linuxHeadersCrossChooser = ver : if ver == "2.4" then linuxHeaders24Cross
else if ver == "2.6" then linuxHeaders26Cross
Adding linux 2.4 kernel headers for cross builds. (I'm thinking of OpenWRT machines out there, mips, with linux 2.4) svn path=/nixpkgs/trunk/; revision=20539
2010-03-10 21:44:48 +01:00
else throw "Unknown linux kernel version";
linuxHeadersCross = assert crossSystem != null;
linuxHeadersCrossChooser crossSystem.platform.kernelMajor;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
kernelPatches = callPackage ../os-specific/linux/kernel/patches.nix { };
* Use the generic kernel builder. svn path=/nixpkgs/trunk/; revision=13779
2009-01-15 16:54:24 +01:00
Linux 3.2-rc1 svn path=/nixpkgs/trunk/; revision=30336
2011-11-08 17:58:20 +01:00
linux_3_2 = makeOverridable (import ../os-specific/linux/kernel/linux-3.2.nix) {
Rename linuxManualConfig to buildLinux Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-22 02:05:55 +01:00
inherit fetchurl stdenv perl buildLinux;
fix eval after e4961c6
2014-03-21 13:46:31 +01:00
kernelPatches = [];
Linux 3.2-rc1 svn path=/nixpkgs/trunk/; revision=30336
2011-11-08 17:58:20 +01:00
};
linux_3_2_powertop svn path=/nixpkgs/trunk/; revision=31257
2012-01-03 23:25:38 +01:00
Adding linux 3.4. svn path=/nixpkgs/trunk/; revision=34209
2012-05-22 17:29:51 +02:00
linux_3_4 = makeOverridable (import ../os-specific/linux/kernel/linux-3.4.nix) {
Rename linuxManualConfig to buildLinux Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-22 02:05:55 +01:00
inherit fetchurl stdenv perl buildLinux;
Remove sec_perm patch that was needed by AUFS Now the kernel is unpatched by default on non-MIPS!
2014-03-21 09:36:15 +01:00
kernelPatches = lib.optionals ((platform.kernelArch or null) == "mips")
Adding two kernel patches for mips, that make the life easier on loongson2f (less sigill, less sigbus). Related to bad handling of FPU instructions. I apply them only to linux 3.4, although I think they can apply to many older kernels too. svn path=/nixpkgs/trunk/; revision=34522
2012-06-16 12:49:03 +02:00
[ kernelPatches.mips_fpureg_emu
kernelPatches.mips_fpu_sigill
Adding linux 3.4. svn path=/nixpkgs/trunk/; revision=34209
2012-05-22 17:29:51 +02:00
];
};
Adding linux-3.6-rpi I picked the change from https://github.com/aforemny/nixpkgs/commit/7b4d69eeff2eb10c395c8d1a52a0c1e246cddb45
2012-12-27 22:29:56 +01:00
linux_3_6_rpi = makeOverridable (import ../os-specific/linux/kernel/linux-rpi-3.6.nix) {
Rename linuxManualConfig to buildLinux Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-22 02:05:55 +01:00
inherit fetchurl stdenv perl buildLinux;
add kernel 3.8
2013-02-21 08:53:16 +01:00
};
Linux 3.10 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-01 02:55:21 +02:00
linux_3_10 = makeOverridable (import ../os-specific/linux/kernel/linux-3.10.nix) {
Rename linuxManualConfig to buildLinux Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-22 02:05:55 +01:00
inherit fetchurl stdenv perl buildLinux;
Remove sec_perm patch that was needed by AUFS Now the kernel is unpatched by default on non-MIPS!
2014-03-21 09:36:15 +01:00
kernelPatches = lib.optionals ((platform.kernelArch or null) == "mips")
Linux 3.10 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-01 02:55:21 +02:00
[ kernelPatches.mips_fpureg_emu
kernelPatches.mips_fpu_sigill
kernelPatches.mips_ext3_n32
];
};
kernel: add linux 3.12-rc2
2013-09-25 12:49:49 +02:00
linux_3_12 = makeOverridable (import ../os-specific/linux/kernel/linux-3.12.nix) {
Rename linuxManualConfig to buildLinux Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-22 02:05:55 +01:00
inherit fetchurl stdenv perl buildLinux;
Remove sec_perm patch that was needed by AUFS Now the kernel is unpatched by default on non-MIPS!
2014-03-21 09:36:15 +01:00
kernelPatches = lib.optionals ((platform.kernelArch or null) == "mips")
kernel: add linux 3.12-rc2
2013-09-25 12:49:49 +02:00
[ kernelPatches.mips_fpureg_emu
kernelPatches.mips_fpu_sigill
kernelPatches.mips_ext3_n32
];
};
Add linux 3.14
2014-04-01 02:54:47 +02:00
linux_3_14 = makeOverridable (import ../os-specific/linux/kernel/linux-3.14.nix) {
Rename linuxManualConfig to buildLinux Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-22 02:05:55 +01:00
inherit fetchurl stdenv perl buildLinux;
Remove sec_perm patch that was needed by AUFS Now the kernel is unpatched by default on non-MIPS!
2014-03-21 09:36:15 +01:00
kernelPatches = lib.optionals ((platform.kernelArch or null) == "mips")
Linux 3.13 Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-20 04:35:24 +01:00
[ kernelPatches.mips_fpureg_emu
kernelPatches.mips_fpu_sigill
kernelPatches.mips_ext3_n32
];
};
kernel: Add 3.15
2014-06-08 22:07:54 +02:00
linux_3_15 = makeOverridable (import ../os-specific/linux/kernel/linux-3.15.nix) {
Add linux 3.14
2014-04-01 02:54:47 +02:00
inherit fetchurl stdenv perl buildLinux;
kernelPatches = lib.optionals ((platform.kernelArch or null) == "mips")
[ kernelPatches.mips_fpureg_emu
kernelPatches.mips_fpu_sigill
kernelPatches.mips_ext3_n32
];
};
linux-kernel: Add new upstream version 3.16. Also set linux_latest to it as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-08-04 02:38:03 +02:00
linux_3_16 = makeOverridable (import ../os-specific/linux/kernel/linux-3.16.nix) {
kernel: Add 3.15
2014-06-08 22:07:54 +02:00
inherit fetchurl stdenv perl buildLinux;
kernelPatches = lib.optionals ((platform.kernelArch or null) == "mips")
[ kernelPatches.mips_fpureg_emu
kernelPatches.mips_fpu_sigill
kernelPatches.mips_ext3_n32
];
};
kernel/grsec: updates; add mainline package for brave souls Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-05 13:06:19 +02:00
linux_testing = makeOverridable (import ../os-specific/linux/kernel/linux-testing.nix) {
inherit fetchurl stdenv perl buildLinux;
kernelPatches = lib.optionals ((platform.kernelArch or null) == "mips")
[ kernelPatches.mips_fpureg_emu
kernelPatches.mips_fpu_sigill
kernelPatches.mips_ext3_n32
];
};
grsec: refactor grsecurity packages This now provides a handful of different grsecurity kernels for slightly different 'flavors' of packages. This doesn't change the grsecurity module to use them just yet, however. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-14 19:04:40 +02:00
/* grsec configuration
We build several flavors of 'default' grsec kernels. These are
built by default with Hydra. If the user selects a matching
'default' flavor, then the pre-canned package set can be
chosen. Typically, users will make very basic choices like
'security' + 'server' or 'performance' + 'desktop' with
virtualisation support. These will then be picked.
Note: Xen guest kernels are included for e.g. NixOps deployments
to EC2, where Xen is the Hypervisor.
*/
grFlavors = import ../build-support/grsecurity/flavors.nix;
mkGrsecurity = opts:
(import ../build-support/grsecurity {
grsecOptions = opts;
inherit pkgs lib;
});
grKernel = opts: (mkGrsecurity opts).grsecKernel;
grPackage = opts: recurseIntoAttrs (mkGrsecurity opts).grsecPackage;
# Stable kernels
linux_grsec_stable_desktop = grKernel grFlavors.linux_grsec_stable_desktop;
linux_grsec_stable_server = grKernel grFlavors.linux_grsec_stable_server;
linux_grsec_stable_server_xen = grKernel grFlavors.linux_grsec_stable_server_xen;
# Testing kernels
linux_grsec_testing_desktop = grKernel grFlavors.linux_grsec_testing_desktop;
linux_grsec_testing_server = grKernel grFlavors.linux_grsec_testing_server;
linux_grsec_testing_server_xen = grKernel grFlavors.linux_grsec_testing_server_xen;
kernel: add linux 3.12-rc2
2013-09-25 12:49:49 +02:00
Rename `kernel*' to `linux*'. svn path=/nixpkgs/branches/stdenv-updates/; revision=19068
2009-12-21 15:12:00 +01:00
/* Linux kernel modules are inherently tied to a specific kernel. So
* Put all packages that depend on a specific kernel (notably kernel modules) together in an attribute set returned by the function "kernelPackagesFor" that takes a kernel as argument. For instance, kernelPackages_2_6_23 is the result of calling this function with kernel_2_6_23. This is necessary in NixOS to make it easier to override the kernel: it's not enough to just specify a different kernel (via the boot.kernel option), but you also need matching nvidiaDriver, aufs, iwlwifi, etc. Having a single attribute set that contains all kernel-related packages makes this much easier. * The kernel now has a passthru attribute "features" that allows NixOS expressions to test whether a kernel has certain features. For instance, the externel "iwlwifi" kernel module package should only be built on kernels < 2.6.24, as kernels >= 2.6.24 have iwlwifi support integrated. So the NixOS expressions can do the test "kernel.features ? iwlwifi" to see if the iwlwifi package should be built. Kernel patches can declare additional features. E.g., the fbsplash patch adds a "fbSplash" feature. svn path=/nixpkgs/trunk/; revision=11881
2008-05-22 14:01:24 +02:00
rather than provide specific instances of those packages for a
specific kernel, we have a function that builds those packages
for a specific kernel. This function can then be called for
whatever kernel you're using. */
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
linuxPackagesFor = kernel: self: let callPackage = newScope self; in {
inherit kernel;
* Put all packages that depend on a specific kernel (notably kernel modules) together in an attribute set returned by the function "kernelPackagesFor" that takes a kernel as argument. For instance, kernelPackages_2_6_23 is the result of calling this function with kernel_2_6_23. This is necessary in NixOS to make it easier to override the kernel: it's not enough to just specify a different kernel (via the boot.kernel option), but you also need matching nvidiaDriver, aufs, iwlwifi, etc. Having a single attribute set that contains all kernel-related packages makes this much easier. * The kernel now has a passthru attribute "features" that allows NixOS expressions to test whether a kernel has certain features. For instance, the externel "iwlwifi" kernel module package should only be built on kernels < 2.6.24, as kernels >= 2.6.24 have iwlwifi support integrated. So the NixOS expressions can do the test "kernel.features ? iwlwifi" to see if the iwlwifi package should be built. Kernel patches can declare additional features. E.g., the fbsplash patch adds a "fbSplash" feature. svn path=/nixpkgs/trunk/; revision=11881
2008-05-22 14:01:24 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
acpi_call = callPackage ../os-specific/linux/acpi-call {};
Adding acpi-call svn path=/nixpkgs/trunk/; revision=24668
2010-11-11 23:00:57 +01:00
Adding batman-adv.
2013-05-28 22:58:25 +02:00
batman_adv = callPackage ../os-specific/linux/batman-adv {};
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
bbswitch = callPackage ../os-specific/linux/bbswitch {};
Added the 'bbswitch' module, which is a more conventient module for powering off/on nvidia graphics cards than possible via the acpi_call module. svn path=/nixpkgs/trunk/; revision=31840
2012-01-26 02:02:22 +01:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
ati_drivers_x11 = callPackage ../os-specific/linux/ati-drivers { };
adding ati-drivers There is still much to be done, see http://thread.gmane.org/gmane.linux.distributions.nixos/4145 svn path=/nixpkgs/trunk/; revision=21848
2010-05-18 21:36:55 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
blcr = callPackage ../os-specific/linux/blcr { };
Adding cryptodev-linux, and made openssl use it optionally. I'm trying to get the CESA of the sheevaplug available to openssl.
2012-09-23 20:50:24 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
cryptodev = callPackage ../os-specific/linux/cryptodev { };
os-specific/linux/e1000e: added recent a version of the e1000e kernel module That module is required to support modern Intel Gigabit Ethernet cards. svn path=/nixpkgs/trunk/; revision=29297
2011-09-15 17:18:45 +02:00
cpupower: Add package to replace cpufrequtils
2014-03-17 23:33:39 +01:00
cpupower = callPackage ../os-specific/linux/cpupower { };
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
e1000e = callPackage ../os-specific/linux/e1000e {};
all-packages.nix: drop trailing whitespace
2014-04-11 10:06:06 +02:00
v4l2loopback = callPackage ../os-specific/linux/v4l2loopback { };
Add Exmap, a Linux-specific tool to examine process memory usage. svn path=/nixpkgs/trunk/; revision=12857
2008-09-12 22:00:00 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
frandom = callPackage ../os-specific/linux/frandom { };
added iscsitarget svn path=/nixpkgs/trunk/; revision=23540
2010-08-30 11:15:27 +02:00
ktap: add v0.5-dev from git Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-02-19 12:00:45 +01:00
ktap = callPackage ../os-specific/linux/ktap { };
lttng: align attribute name with package name lttngModules => lttng-modules lttngTools => lttng-tools lttngUst => lttng-ust But keep the old attributes around for backward compatibility.
2014-07-31 15:48:06 +02:00
lttng-modules = callPackage ../os-specific/linux/lttng-modules { };
Packages changes, needed after recent kernel expression restructurisation svn path=/nixpkgs/trunk/; revision=11883
2008-05-22 21:29:23 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
broadcom_sta = callPackage ../os-specific/linux/broadcom-sta/default.nix { };
Have the kernel headers be a linuxPackage, use the current linuxPackage's headers svn path=/nixpkgs/branches/stdenv-updates/; revision=29546
2011-09-30 17:34:37 +02:00
Now properly add nvidiabl.
2014-03-07 16:08:38 +01:00
nvidiabl = callPackage ../os-specific/linux/nvidiabl { };
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
nvidia_x11 = callPackage ../os-specific/linux/nvidia-x11 { };
* Put all packages that depend on a specific kernel (notably kernel modules) together in an attribute set returned by the function "kernelPackagesFor" that takes a kernel as argument. For instance, kernelPackages_2_6_23 is the result of calling this function with kernel_2_6_23. This is necessary in NixOS to make it easier to override the kernel: it's not enough to just specify a different kernel (via the boot.kernel option), but you also need matching nvidiaDriver, aufs, iwlwifi, etc. Having a single attribute set that contains all kernel-related packages makes this much easier. * The kernel now has a passthru attribute "features" that allows NixOS expressions to test whether a kernel has certain features. For instance, the externel "iwlwifi" kernel module package should only be built on kernels < 2.6.24, as kernels >= 2.6.24 have iwlwifi support integrated. So the NixOS expressions can do the test "kernel.features ? iwlwifi" to see if the iwlwifi package should be built. Kernel patches can declare additional features. E.g., the fbsplash patch adds a "fbSplash" feature. svn path=/nixpkgs/trunk/; revision=11881
2008-05-22 14:01:24 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
nvidia_x11_legacy173 = callPackage ../os-specific/linux/nvidia-x11/legacy173.nix { };
nvidia_x11_legacy304 = callPackage ../os-specific/linux/nvidia-x11/legacy304.nix { };
Adding the nvidia legacy drivers (I still use a geForce 4 AGP) svn path=/nixpkgs/trunk/; revision=17284
2009-09-20 00:09:08 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
openafsClient = callPackage ../servers/openafs-client { };
Fix bugs and improve pkgs/servers/openafs-client svn path=/nixpkgs/trunk/; revision=19750
2010-02-01 17:27:35 +01:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
openiscsi = callPackage ../os-specific/linux/open-iscsi { };
Fix bugs and improve pkgs/servers/openafs-client svn path=/nixpkgs/trunk/; revision=19750
2010-02-01 17:27:35 +01:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
wis_go7007 = callPackage ../os-specific/linux/wis-go7007 { };
* Put all packages that depend on a specific kernel (notably kernel modules) together in an attribute set returned by the function "kernelPackagesFor" that takes a kernel as argument. For instance, kernelPackages_2_6_23 is the result of calling this function with kernel_2_6_23. This is necessary in NixOS to make it easier to override the kernel: it's not enough to just specify a different kernel (via the boot.kernel option), but you also need matching nvidiaDriver, aufs, iwlwifi, etc. Having a single attribute set that contains all kernel-related packages makes this much easier. * The kernel now has a passthru attribute "features" that allows NixOS expressions to test whether a kernel has certain features. For instance, the externel "iwlwifi" kernel module package should only be built on kernels < 2.6.24, as kernels >= 2.6.24 have iwlwifi support integrated. So the NixOS expressions can do the test "kernel.features ? iwlwifi" to see if the iwlwifi package should be built. Kernel patches can declare additional features. E.g., the fbsplash patch adds a "fbSplash" feature. svn path=/nixpkgs/trunk/; revision=11881
2008-05-22 14:01:24 +02:00
Update and fix kernel packages to new kernel build In most cases, this just meant changing kernelDev (now removed from linuxPackagesFor) to kernel.dev. Some packages needed more work (though whether that was because of my changes or because they were already broken, I'm not sure). Specifics: * psmouse-alps builds on 3.4 but not 3.10, as noted in the comments that were already there * blcr builds on 3.4 but not 3.10, as noted in comments that were already there * open-iscsi, ati-drivers, wis-go7007, and openafsClient don't build on 3.4 or 3.10 on this branch or on master, so they're marked broken * A version-specific kernelHeaders package was added The following packages were removed: * atheros/madwifi is superceded by official ath*k modules * aufs is no longer used by any of our kernels * broadcom-sta v6 (which was already packaged) replaces broadcom-sta * exmap has not been updated since 2011 and doesn't build * iscis-target has not been updated since 2010 and doesn't build * iwlwifi is part of mainline now and doesn't build * nivida-x11-legacy-96 hasn't been updated since 2008 and doesn't build Everything not specifically mentioned above builds successfully on 3.10. I haven't yet tested on 3.4, but will before opening a pull request. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-05 02:57:21 +01:00
kernelHeaders = callPackage ../os-specific/linux/kernel-headers { };
klibc = callPackage ../os-specific/linux/klibc { };
Enable building full klibc as a kernelPackage svn path=/nixpkgs/trunk/; revision=30009
2011-10-25 10:59:39 +02:00
klibcShrunk should be a kernelPackage Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-05 13:45:14 +01:00
klibcShrunk = lowPrio (callPackage ../os-specific/linux/klibc/shrunk.nix { });
Enable building full klibc as a kernelPackage svn path=/nixpkgs/trunk/; revision=30009
2011-10-25 10:59:39 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
/* compiles but has to be integrated into the kernel somehow
Let's have it uncommented and finish it..
*/
ndiswrapper = callPackage ../os-specific/linux/ndiswrapper { };
Uncommented ndiswrapper svn path=/nixpkgs/trunk/; revision=12096
2008-06-15 13:39:54 +02:00
Adding netatop module, for atop
2013-05-20 10:00:03 +02:00
netatop = callPackage ../os-specific/linux/netatop { };
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
perf = callPackage ../os-specific/linux/kernel/perf.nix { };
Adding linux 'perf' tool. svn path=/nixpkgs/trunk/; revision=31319
2012-01-05 22:24:51 +01:00
Adding psmouse-alps, a touchpad kernel driver. Some laptops use these new touchpads, and this driver is supposed to provide proper support for them.
2013-06-12 22:55:01 +02:00
psmouse_alps = callPackage ../os-specific/linux/psmouse-alps { };
spl, zfs: Add git versions, based on recent commits Upstream has not been tagging new versions for a long time, but we need compatibility with newer kernels. The 0.6.2 versions already have a bunch of backported compatibility patches, but 3.14 kernels need even more. Also, the git versions have fixed a bunch of crashes and other bugs, so perhaps we should just bite the bullet and just use recent git versions (as sometimes upstream recommends, when people run into bugs). This adds a new "boot.zfs.useGit" boolean option, so that a user can easily opt into using the git versions.
2014-03-22 18:27:23 +01:00
spl = callPackage ../os-specific/linux/spl { };
spl_git = callPackage ../os-specific/linux/spl/git.nix { };
- zfs 0.6.0-rc11, spl 0.6.0-rc11
2012-10-05 18:11:25 +02:00
Adding sysdig system call tracer for Linux
2014-04-13 18:49:26 +02:00
sysdig = callPackage ../os-specific/linux/sysdig {};
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
tp_smapi = callPackage ../os-specific/linux/tp_smapi { };
Adding tp_smapi. Patch by Rok Garbas, who also adds himself as a maintainer. svn path=/nixpkgs/trunk/; revision=33495
2012-03-31 15:40:34 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
v86d = callPackage ../os-specific/linux/v86d { };
v86d svn path=/nixpkgs/trunk/; revision=30011
2011-10-25 11:40:15 +02:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
virtualbox = callPackage ../applications/virtualization/virtualbox {
stdenv = stdenv_32bit;
inherit (gnome) libIDL;
Make it possible to enable vbox extension pack easily from nixpkgs config Signed-off-by: Shea Levy <shea@shealevy.com>
2013-04-29 19:54:22 +02:00
enableExtensionPack = config.virtualbox.enableExtensionPack or false;
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
};
pkgs/tools/typesetting/asciidoc: updated to version 8.5.1 New asciidoc versions do have a proper configure script. Using that simplifies the build instructions a bit. svn path=/nixpkgs/trunk/; revision=18076
2009-11-03 16:57:22 +01:00
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
virtualboxGuestAdditions = callPackage ../applications/virtualization/virtualbox/guest-additions { };
- zfs 0.6.0-rc11, spl 0.6.0-rc11
2012-10-05 18:11:25 +02:00
spl, zfs: Add git versions, based on recent commits Upstream has not been tagging new versions for a long time, but we need compatibility with newer kernels. The 0.6.2 versions already have a bunch of backported compatibility patches, but 3.14 kernels need even more. Also, the git versions have fixed a bunch of crashes and other bugs, so perhaps we should just bite the bullet and just use recent git versions (as sometimes upstream recommends, when people run into bugs). This adds a new "boot.zfs.useGit" boolean option, so that a user can easily opt into using the git versions.
2014-03-22 18:27:23 +01:00
zfs = callPackage ../os-specific/linux/zfs { };
zfs_git = callPackage ../os-specific/linux/zfs/git.nix { };
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
};
* Put all packages that depend on a specific kernel (notably kernel modules) together in an attribute set returned by the function "kernelPackagesFor" that takes a kernel as argument. For instance, kernelPackages_2_6_23 is the result of calling this function with kernel_2_6_23. This is necessary in NixOS to make it easier to override the kernel: it's not enough to just specify a different kernel (via the boot.kernel option), but you also need matching nvidiaDriver, aufs, iwlwifi, etc. Having a single attribute set that contains all kernel-related packages makes this much easier. * The kernel now has a passthru attribute "features" that allows NixOS expressions to test whether a kernel has certain features. For instance, the externel "iwlwifi" kernel module package should only be built on kernels < 2.6.24, as kernels >= 2.6.24 have iwlwifi support integrated. So the NixOS expressions can do the test "kernel.features ? iwlwifi" to see if the iwlwifi package should be built. Kernel patches can declare additional features. E.g., the fbsplash patch adds a "fbSplash" feature. svn path=/nixpkgs/trunk/; revision=11881
2008-05-22 14:01:24 +02:00
grsec: refactor grsecurity packages This now provides a handful of different grsecurity kernels for slightly different 'flavors' of packages. This doesn't change the grsecurity module to use them just yet, however. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-14 19:04:40 +02:00
# The current default kernel / kernel modules.
linux = linuxPackages.kernel;
linuxPackages = linuxPackages_3_12;
# Update this when adding the newest kernel major version!
linux-kernel: Add new upstream version 3.16. Also set linux_latest to it as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-08-04 02:38:03 +02:00
linux_latest = pkgs.linux_3_16;
linuxPackages_latest = pkgs.linuxPackages_3_16;
grsec: refactor grsecurity packages This now provides a handful of different grsecurity kernels for slightly different 'flavors' of packages. This doesn't change the grsecurity module to use them just yet, however. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-14 19:04:40 +02:00
* Put all packages that depend on a specific kernel (notably kernel modules) together in an attribute set returned by the function "kernelPackagesFor" that takes a kernel as argument. For instance, kernelPackages_2_6_23 is the result of calling this function with kernel_2_6_23. This is necessary in NixOS to make it easier to override the kernel: it's not enough to just specify a different kernel (via the boot.kernel option), but you also need matching nvidiaDriver, aufs, iwlwifi, etc. Having a single attribute set that contains all kernel-related packages makes this much easier. * The kernel now has a passthru attribute "features" that allows NixOS expressions to test whether a kernel has certain features. For instance, the externel "iwlwifi" kernel module package should only be built on kernels < 2.6.24, as kernels >= 2.6.24 have iwlwifi support integrated. So the NixOS expressions can do the test "kernel.features ? iwlwifi" to see if the iwlwifi package should be built. Kernel patches can declare additional features. E.g., the fbsplash patch adds a "fbSplash" feature. svn path=/nixpkgs/trunk/; revision=11881
2008-05-22 14:01:24 +02:00
# Build the kernel modules for the some of the kernels.
Partially revert my recent kernelPackages changes First, pass in `self' again so that overriding works properly (thanks for pointing that out, @edolstra) Second, instead of having linuxPackages*.kernel mean something different inside the set and out, add a new attribute linuxPackages*.kernelDev, which for the generic kernel is simply linuxPackages*.kernel but for the manual-config kernel is the `dev' output (which has the build tree, source tree, etc.) The second change required trivial modifications in a bunch of expressions, I verified that all of the linuxPackages* sets defined in all-packages.nix have the same drv paths before and after the change. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-03-24 12:45:00 +01:00
linuxPackages_3_2 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_3_2 linuxPackages_3_2);
linuxPackages_3_4 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_3_4 linuxPackages_3_4);
Don't build Linux 3.6-rpi packages on Hydra They're all broken.
2013-11-04 21:07:35 +01:00
linuxPackages_3_6_rpi = linuxPackagesFor pkgs.linux_3_6_rpi linuxPackages_3_6_rpi;
Linux 3.10 Signed-off-by: Shea Levy <shea@shealevy.com>
2013-07-01 02:55:21 +02:00
linuxPackages_3_10 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_3_10 linuxPackages_3_10);
TuxOnIce: Add a 3.10 linux kernel with the TuxOnIce hibernation patch
2013-11-19 21:36:55 +01:00
linuxPackages_3_10_tuxonice = linuxPackagesFor pkgs.linux_3_10_tuxonice linuxPackages_3_10_tuxonice;
kernel: add linux 3.12-rc2
2013-09-25 12:49:49 +02:00
linuxPackages_3_12 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_3_12 linuxPackages_3_12);
Add linux 3.14
2014-04-01 02:54:47 +02:00
linuxPackages_3_14 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_3_14 linuxPackages_3_14);
kernel: Add 3.15
2014-06-08 22:07:54 +02:00
linuxPackages_3_15 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_3_15 linuxPackages_3_15);
linux-kernel: Add new upstream version 3.16. Also set linux_latest to it as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-08-04 02:38:03 +02:00
linuxPackages_3_16 = recurseIntoAttrs (linuxPackagesFor pkgs.linux_3_16 linuxPackages_3_16);
kernel/grsec: updates; add mainline package for brave souls Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-05 13:06:19 +02:00
linuxPackages_testing = recurseIntoAttrs (linuxPackagesFor pkgs.linux_testing linuxPackages_testing);
Rename `kernel*' to `linux*'. svn path=/nixpkgs/branches/stdenv-updates/; revision=19068
2009-12-21 15:12:00 +01:00
grsec: refactor grsecurity packages This now provides a handful of different grsecurity kernels for slightly different 'flavors' of packages. This doesn't change the grsecurity module to use them just yet, however. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-14 19:04:40 +02:00
# grsecurity flavors
# Stable kernels
linuxPackages_grsec_stable_desktop = grPackage grFlavors.linux_grsec_stable_desktop;
linuxPackages_grsec_stable_server = grPackage grFlavors.linux_grsec_stable_server;
linuxPackages_grsec_stable_server_xen = grPackage grFlavors.linux_grsec_stable_server_xen;
# Testing kernels
linuxPackages_grsec_testing_desktop = grPackage grFlavors.linux_grsec_testing_desktop;
linuxPackages_grsec_testing_server = grPackage grFlavors.linux_grsec_testing_server;
linuxPackages_grsec_testing_server_xen = grPackage grFlavors.linux_grsec_testing_server_xen;
all-packages.nix changes for all previous commits.. svn path=/nixpkgs/trunk/; revision=11276
2008-03-24 20:40:15 +01:00
Add first attempt at linux/kernel/manual-config. The goal of this function is to make it possible to build a kernel with a user provided .config. As a secondary goal, it will extract NixOS-relevant features from the config automatically. As a tertiary goal, the build will aim to be simpler than the current generic kernel builder.sh. Unfortunately, that simplicity is offset by the complexity of the feature extraction, especially since nix segfaults when trying to split the file into lines (so an import from a derivation is used)
2012-07-29 07:23:51 +02:00
# A function to build a manually-configured kernel
Remove trace message to prevent spamming nix-env users
2014-01-31 13:08:23 +01:00
linuxManualConfig = pkgs.buildLinux;
Rename linuxManualConfig to buildLinux Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-22 02:05:55 +01:00
buildLinux = import ../os-specific/linux/kernel/manual-config.nix {
linux/manual-config: Cross-compiling support With this, I was able to successfully compile a defconfig kernel for the sheevaplug, though I didn't actually try to run it (not having a sheevaplug myself). For native compiles, the most significant difference is that the platform's kernel target is built directly rather than hoping the default make target will pull it in. Also some stylistic improvements along the way. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-01 04:38:06 +01:00
inherit (pkgs) stdenv runCommand nettools bc perl kmod writeTextFile ubootChooser;
Add first attempt at linux/kernel/manual-config. The goal of this function is to make it possible to build a kernel with a user provided .config. As a secondary goal, it will extract NixOS-relevant features from the config automatically. As a tertiary goal, the build will aim to be simpler than the current generic kernel builder.sh. Unfortunately, that simplicity is offset by the complexity of the feature extraction, especially since nix segfaults when trying to split the file into lines (so an import from a derivation is used)
2012-07-29 07:23:51 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
keyutils = callPackage ../os-specific/linux/keyutils { };
Adding ecryptfs, and one of its dependencies: keyutils. (I have not tried whether they work) svn path=/nixpkgs/trunk/; revision=19645
2010-01-25 11:34:47 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libselinux = callPackage ../os-specific/linux/libselinux { };
libraw1394 added svn path=/nixpkgs/trunk/; revision=10121
2008-01-12 02:26:04 +01:00
libsemanage: packaged svn path=/nixpkgs/trunk/; revision=26541
2011-03-27 06:46:12 +02:00
libsemanage = callPackage ../os-specific/linux/libsemanage { };
libraw: package 0.16.0
2014-02-13 03:22:39 +01:00
libraw = callPackage ../development/libraries/libraw { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libraw1394 = callPackage ../development/libraries/libraw1394 { };
libraw1394 added svn path=/nixpkgs/trunk/; revision=10121
2008-01-12 02:26:04 +01:00
Cleanup 'rec {' svn path=/nixpkgs/branches/x-updates/; revision=26065
2011-02-23 11:04:50 +01:00
libsexy = callPackage ../development/libraries/libsexy { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libsepol = callPackage ../os-specific/linux/libsepol { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libsmbios = callPackage ../os-specific/linux/libsmbios { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Doh. svn path=/nixpkgs/trunk/; revision=30998
2011-12-21 11:29:19 +01:00
lm_sensors = callPackage ../os-specific/linux/lm-sensors { };
* Doh. Forgot to commit. svn path=/nixpkgs/trunk/; revision=12863
2008-09-14 21:05:59 +02:00
lockdep: refactor into non-kernel package Lockdep doesn't *really* require the kernel package - just the kernel sources. It's really a user-space tool just compiled from some portable code within the kernel, nothing more. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-09 02:21:06 +02:00
lockdep = callPackage ../os-specific/linux/lockdep { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lsiutil = callPackage ../os-specific/linux/lsiutil { };
* Added lsiutil, a command-line utility for LSI controllers. svn path=/nixpkgs/trunk/; revision=22437
2010-07-01 15:18:09 +02:00
Add kmod, the replacement for the now-defunct module-init-tools The kmod tools appear to take a flag to name the location of the modules directory, so we may not need to migrate our module-init-tools patches svn path=/nixpkgs/trunk/; revision=33413
2012-03-25 22:05:36 +02:00
kmod = callPackage ../os-specific/linux/kmod { };
pull module blacklist from Ubuntu and use it by default People often have serious problems due to bogus modules like *fb.
2014-01-21 00:29:35 +01:00
kmod-blacklist-ubuntu = callPackage ../os-specific/linux/kmod-blacklist-ubuntu { };
* Remove KVM (obsolete -> qemu-kvm). svn path=/nixpkgs/trunk/; revision=22796
2010-07-28 17:39:39 +02:00
kvm = qemu_kvm;
Updating xchm. svn path=/nixpkgs/trunk/; revision=18310
2009-11-09 12:55:31 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libcap = callPackage ../os-specific/linux/libcap { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Split libcap package libcap can be splitted for free (just cd subdir; make install). So I've decided not to raise up disscussions "should we build cap_pam.so?" etc. svn path=/nixpkgs/branches/stdenv-updates/; revision=23967
2010-09-27 15:49:13 +02:00
libcap_progs = callPackage ../os-specific/linux/libcap/progs.nix { };
libcap_pam = callPackage ../os-specific/linux/libcap/pam.nix { };
libcap_manpages = callPackage ../os-specific/linux/libcap/man.nix { };
add libcap_ng
2013-02-24 11:19:35 +01:00
libcap_ng = callPackage ../os-specific/linux/libcap-ng { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libnscd = callPackage ../os-specific/linux/libnscd { };
* Added Valknut. svn path=/nixpkgs/trunk/; revision=3746
2005-08-30 09:39:38 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
libnotify = callPackage ../development/libraries/libnotify { };
Added Falling Sand Game and wxGTK without unicode for it. svn path=/nixpkgs/trunk/; revision=9543
2007-10-27 19:55:13 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
libvolume_id = callPackage ../os-specific/linux/libvolume_id { };
* Added wxGTK/wxPython 2.8. However this was quite pointless as Bittorrent is even more broken with wxPython 2.8. svn path=/nixpkgs/trunk/; revision=8812
2007-05-31 15:43:13 +02:00
Oops... Fix alphabetical order in all-packages.nix svn path=/nixpkgs/trunk/; revision=26064
2011-02-22 22:07:36 +01:00
lsscsi = callPackage ../os-specific/linux/lsscsi { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lvm2 = callPackage ../os-specific/linux/lvm2 { };
Added Falling Sand Game and wxGTK without unicode for it. svn path=/nixpkgs/trunk/; revision=9543
2007-10-27 19:55:13 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mdadm = callPackage ../os-specific/linux/mdadm { };
* Updated Sylpheed to 2.1.9 and added GPG support (through gpgme). svn path=/nixpkgs/trunk/; revision=4400
2005-12-19 11:34:01 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mingetty = callPackage ../os-specific/linux/mingetty { };
* Added the OpenAL sound library. * Enabled (optional) 3D support in SDL. svn path=/nixpkgs/trunk/; revision=4594
2006-01-26 15:01:08 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
module_init_tools = callPackage ../os-specific/linux/module-init-tools { };
* Added APR. svn path=/nixpkgs/trunk/; revision=6484
2006-09-11 10:45:01 +02:00
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
aggregateModules = modules:
Kernel module aggregator: Use kmod instead of module-init-tools
2013-08-09 17:55:45 +02:00
callPackage ../os-specific/linux/kmod/aggregator.nix {
inherit modules;
* Clean up indentation (expanded tabs etc.). svn path=/nixpkgs/trunk/; revision=11150
2008-03-17 10:41:28 +01:00
};
Added module_aggregator. Pass some directories with modules to it, and it will give you a directory to use instead of pkgs.kernel . addSbinPath in builderDefs to use sbin/ in addToEnv . Some catching up in xlaunch. svn path=/nixpkgs/trunk/; revision=10075
2008-01-04 18:02:12 +01:00
* Add the Linux multipath-tools. svn path=/nixpkgs/trunk/; revision=26719
2011-04-06 16:57:31 +02:00
multipath_tools = callPackage ../os-specific/linux/multipath-tools { };
musl: version 1.0.0 NB: This currently doesn't add a working musl-wrapper around musl-gcc to allow it to work properly (musl has its own dynamic linker as well as libc too which must be accounted for). But at the moment it builds fine, and I plan on working more on it in the future. So lets get it integrated and building on Hydra. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-24 06:29:30 +01:00
musl = callPackage ../os-specific/linux/musl { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nettools = callPackage ../os-specific/linux/net-tools { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
libpng15: use it by some packages to fix build
2013-02-16 18:07:37 +01:00
neverball = callPackage ../games/neverball {
libpng = libpng15;
};
Adding neverball 1.5.0, which comes with neverputt. Fun. svn path=/nixpkgs/trunk/; revision=14338
2009-03-04 18:28:25 +01:00
nftables: Add derivation
2014-08-24 01:16:06 +02:00
nftables = callPackage ../os-specific/linux/nftables { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
numactl = callPackage ../os-specific/linux/numactl { };
Add numactl/libnuma, Linux-specific NUMA support tools. svn path=/nixpkgs/trunk/; revision=11656
2008-04-18 16:38:27 +02:00
add gocode package
2014-06-23 11:49:58 +02:00
gocode = callPackage ../development/tools/gocode { };
gogoclient: ipv6 tunnel svn path=/nixpkgs/trunk/; revision=32668
2012-02-28 01:10:05 +01:00
gogoclient = callPackage ../os-specific/linux/gogoclient { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nss_ldap = callPackage ../os-specific/linux/nss_ldap { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
libxcrypt: Remove
2013-01-28 15:56:41 +01:00
pam = callPackage ../os-specific/linux/pam { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Add entries for pmount & pam_usb in all-packages.nix. svn path=/nixpkgs/trunk/; revision=19184
2010-01-03 12:13:05 +01:00
# pam_bioapi ( see http://www.thinkwiki.org/wiki/How_to_enable_the_fingerprint_reader )
Move all db4 packages to the default db5
2014-01-31 21:05:37 +01:00
pam_ccreds = callPackage ../os-specific/linux/pam_ccreds { };
pam_ccreds: to locally authenticate using an enterprise identity when the network is unavailable. svn path=/nixpkgs/trunk/; revision=22987
2010-08-06 10:50:58 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pam_console = callPackage ../os-specific/linux/pam_console {
* pam_console needs an old libtool. svn path=/nixpkgs/branches/stdenv-updates/; revision=14791
2009-03-30 17:31:47 +02:00
libtool = libtool_1_5;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pam_devperm = callPackage ../os-specific/linux/pam_devperm { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
pam_krb5: added version 2.3.11-1. svn path=/nixpkgs/trunk/; revision=22984
2010-08-06 10:49:05 +02:00
pam_krb5 = callPackage ../os-specific/linux/pam_krb5 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pam_ldap = callPackage ../os-specific/linux/pam_ldap { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pam_login = callPackage ../os-specific/linux/pam_login { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
* Added pam_ssh_agent_auth, a PAM module for authentication through the SSH agent. svn path=/nixpkgs/trunk/; revision=34462
2012-06-11 18:45:54 +02:00
pam_ssh_agent_auth = callPackage ../os-specific/linux/pam_ssh_agent_auth { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pam_usb = callPackage ../os-specific/linux/pam_usb { };
* Add entries for pmount & pam_usb in all-packages.nix. svn path=/nixpkgs/trunk/; revision=19184
2010-01-03 12:13:05 +01:00
grsecurity: add paxctl-0.7 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-02-17 15:24:20 +01:00
paxctl = callPackage ../os-specific/linux/paxctl { };
grsecurity: add pax-utils-0.7 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-02-17 15:24:43 +01:00
pax-utils = callPackage ../os-specific/linux/pax-utils { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pcmciaUtils = callPackage ../os-specific/linux/pcmciautils {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
firmware = config.pcmciaUtils.firmware or [];
config = config.pcmciaUtils.config or null;
Adding Specimen, an audio sampler and phat gtk+ widgets which Specimen uses svn path=/nixpkgs/trunk/; revision=26923
2011-04-22 23:42:38 +02:00
};
Plymouth: update to 0.9.0, fix build, sanitize, enable systemd-integration NOTE: I can start the daemon and ping it, but I haven't been able to get it to do more than that.
2014-05-26 19:29:53 +02:00
plymouth = callPackage ../os-specific/linux/plymouth {
automake = automake113x;
};
Add Plymouth: WIP
2013-04-12 01:58:38 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pmount = callPackage ../os-specific/linux/pmount { };
* Add entries for pmount & pam_usb in all-packages.nix. svn path=/nixpkgs/trunk/; revision=19184
2010-01-03 12:13:05 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pmutils = callPackage ../os-specific/linux/pm-utils { };
* Added pm-utils. svn path=/nixpkgs/trunk/; revision=17430
2009-09-25 23:43:25 +02:00
pmtools: add version 20071116
2012-09-13 20:00:08 +02:00
pmtools = callPackage ../os-specific/linux/pmtools { };
policycoreutils: packaged svn path=/nixpkgs/trunk/; revision=26542
2011-03-27 06:46:19 +02:00
policycoreutils = callPackage ../os-specific/linux/policycoreutils { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
powertop = callPackage ../os-specific/linux/powertop { };
moved vim_configurable to much more sensible place svn path=/nixpkgs/trunk/; revision=9931
2007-12-13 23:15:03 +01:00
Adding prayer. It builds on linux x86_64, but I've not tried to run it. svn path=/nixpkgs/trunk/; revision=30347
2011-11-08 22:07:57 +01:00
prayer = callPackage ../servers/prayer { };
procps-ng: make it the default procps (name and attr)
2014-03-13 23:52:59 +01:00
procps = procps-ng;
* Added apr-util. svn path=/nixpkgs/trunk/; revision=6485
2006-09-11 11:17:28 +02:00
procps-ng: make it the default procps (name and attr)
2014-03-13 23:52:59 +01:00
procps-old = lowPrio (callPackage ../os-specific/linux/procps { });
procps-ng = callPackage ../os-specific/linux/procps-ng { };
procps-ng: Add This will replace procps eventually.
2013-01-23 17:12:20 +01:00
Add a recipe for installing "watch" from procps (#2227)
2014-04-14 16:10:10 +02:00
watch = callPackage ../os-specific/linux/procps/watch.nix { };
qemu-kvm: Disambiguate
2013-07-31 14:50:42 +02:00
qemu_kvm = lowPrio (qemu.override { x86Only = true; });
* qemu-kvm is the upstream renaming of the kvm package. It no longer contains the kernel module, which we didn't build anyway. The kvm package can be deleted eventually. svn path=/nixpkgs/trunk/; revision=16582
2009-08-04 18:02:27 +02:00
Added firmware-linux-nonfree and directly also the free variant. Todo for later: take the files from the various .deb files instead of the source distribution. This version already improves upon my previous implementation, hence I commit it. svn path=/nixpkgs/trunk/; revision=31501
2012-01-12 18:16:11 +01:00
firmwareLinuxNonfree = callPackage ../os-specific/linux/firmware/firmware-linux-nonfree { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
radeontools = callPackage ../os-specific/linux/radeontools { };
Moved a number of Java libraries from the GW project to the Nix Package Collection. svn path=/nixpkgs/trunk/; revision=3803
2005-09-11 17:38:59 +02:00
Adding the firmware files for raspberrypi
2013-01-27 18:49:02 +01:00
raspberrypifw = callPackage ../os-specific/linux/firmware/raspberrypi {};
* Added regionset, a tool for changing the region code setting of DVD players. svn path=/nixpkgs/trunk/; revision=29952
2011-10-21 02:43:56 +02:00
regionset = callPackage ../os-specific/linux/regionset { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rfkill = callPackage ../os-specific/linux/rfkill { };
* Added rfkill, a tool for controlling the wireless kill switch on Linux. svn path=/nixpkgs/trunk/; revision=21199
2010-04-21 13:21:15 +02:00
rfkill udev package. svn path=/nixpkgs/trunk/; revision=32532
2012-02-24 02:35:59 +01:00
rfkill_udev = callPackage ../os-specific/linux/rfkill/udev.nix { };
* Added rtkit, a DBus system service for elevating the scheduling priority of user processes. svn path=/nixpkgs/branches/kde-4.7/; revision=27961
2011-07-26 16:12:33 +02:00
rtkit = callPackage ../os-specific/linux/rtkit { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sdparm = callPackage ../os-specific/linux/sdparm { };
Moved a number of Java libraries from the GW project to the Nix Package Collection. svn path=/nixpkgs/trunk/; revision=3803
2005-09-11 17:38:59 +02:00
SELinux fixes and updates to 2012-09-24
2013-02-24 13:25:53 +01:00
sepolgen = callPackage ../os-specific/linux/sepolgen { };
Upgrade selinux from 20100904 -> 20131030
2013-11-28 09:58:06 +01:00
setools = callPackage ../os-specific/linux/setools { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
shadow = callPackage ../os-specific/linux/shadow { };
Moved a number of Java libraries from the GW project to the Nix Package Collection. svn path=/nixpkgs/trunk/; revision=3803
2005-09-11 17:38:59 +02:00
* Audacious 2.4.0. svn path=/nixpkgs/trunk/; revision=23656
2010-09-06 09:29:18 +02:00
statifier = builderDefsPackage (import ../os-specific/linux/statifier) { };
Adding statifier, a tool to make pseudostatic binaries. Unfortunately, statified NixOS-built binaries segfault on Ubuntu.. svn path=/nixpkgs/trunk/; revision=16291
2009-07-09 23:34:29 +02:00
sysdig: support builds without the kernel module, add pkgs.sysdig attr
2014-05-09 09:06:56 +02:00
sysdig = callPackage ../os-specific/linux/sysdig {
kernel = null;
}; # pkgs.sysdig is a client, for a driver look at linuxPackagesFor
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sysfsutils = callPackage ../os-specific/linux/sysfsutils { };
Add sysfsutils. svn path=/nixpkgs/trunk/; revision=12431
2008-07-25 17:53:23 +02:00
Update and fix kernel packages to new kernel build In most cases, this just meant changing kernelDev (now removed from linuxPackagesFor) to kernel.dev. Some packages needed more work (though whether that was because of my changes or because they were already broken, I'm not sure). Specifics: * psmouse-alps builds on 3.4 but not 3.10, as noted in the comments that were already there * blcr builds on 3.4 but not 3.10, as noted in comments that were already there * open-iscsi, ati-drivers, wis-go7007, and openafsClient don't build on 3.4 or 3.10 on this branch or on master, so they're marked broken * A version-specific kernelHeaders package was added The following packages were removed: * atheros/madwifi is superceded by official ath*k modules * aufs is no longer used by any of our kernels * broadcom-sta v6 (which was already packaged) replaces broadcom-sta * exmap has not been updated since 2011 and doesn't build * iscis-target has not been updated since 2010 and doesn't build * iwlwifi is part of mainline now and doesn't build * nivida-x11-legacy-96 hasn't been updated since 2008 and doesn't build Everything not specifically mentioned above builds successfully on 3.10. I haven't yet tested on 3.4, but will before opening a pull request. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-05 02:57:21 +01:00
sysprof = callPackage ../development/tools/profiling/sysprof {
inherit (gnome) libglade;
};
Add sysfsutils. svn path=/nixpkgs/trunk/; revision=12431
2008-07-25 17:53:23 +02:00
# Provided with sysfsutils.
libsysfs = sysfsutils;
systool = sysfsutils;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sysklogd = callPackage ../os-specific/linux/sysklogd { };
Moved a number of Java libraries from the GW project to the Nix Package Collection. svn path=/nixpkgs/trunk/; revision=3803
2005-09-11 17:38:59 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
syslinux = callPackage ../os-specific/linux/syslinux { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sysstat = callPackage ../os-specific/linux/sysstat { };
add RPM. But: - untested - no Python bindings - experimental version (this is not the "stable" production branch) svn path=/nixpkgs/trunk/; revision=4403
2005-12-20 01:48:38 +01:00
systemd: Update to 212 Note that systemd no longer depends on dbus, so we're rid of the cyclic dependency problem between systemd and dbus. This commit incorporates from wkennington's systemd branch (203dcff45002a63f6be75c65f1017021318cc839, 1f842558a95947261ece66f707bfa24faf5a9d88).
2014-04-16 00:59:26 +02:00
systemd = callPackage ../os-specific/linux/systemd {
linuxHeaders = linuxHeaders_3_14;
};
* Added systemd. svn path=/nixpkgs/trunk/; revision=34200
2012-05-21 22:48:19 +02:00
systemtap: Remove from linuxPackagesFor It doesn't seem to depend on the kernel in any way. Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-02 06:03:49 +01:00
systemtap = callPackage ../development/tools/profiling/systemtap {
inherit (gnome) libglademm;
};
Making lvm2 install systemd stuff, and combine all in a single derivation.
2013-09-20 09:20:14 +02:00
# In nixos, you can set systemd.package = pkgs.systemd_with_lvm2 to get
# LVM2 working in systemd.
systemd_with_lvm2 = pkgs.lib.overrideDerivation pkgs.systemd (p: {
name = p.name + "-with-lvm2";
postInstall = p.postInstall + ''
all-packages.nix: avoid breaking syntax highlighting in Emacs
2013-10-03 16:35:50 +02:00
cp "${pkgs.lvm2}/lib/systemd/system-generators/"* $out/lib/systemd/system-generators
Making lvm2 install systemd stuff, and combine all in a single derivation.
2013-09-20 09:20:14 +02:00
'';
});
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sysvinit = callPackage ../os-specific/linux/sysvinit { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
sysvtools = callPackage ../os-specific/linux/sysvinit {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
withoutInitTools = true;
};
Add `tcp-wrapper'. svn path=/nixpkgs/trunk/; revision=11136
2008-03-15 23:41:31 +01:00
# FIXME: `tcp-wrapper' is actually not OS-specific.
Remove duplicate tcp-wrappers package
2012-11-29 15:14:16 +01:00
tcp_wrappers = callPackage ../os-specific/linux/tcp-wrappers { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
trackballs = callPackage ../games/trackballs {
Adding trackballs svn path=/nixpkgs/trunk/; revision=15625
2009-05-17 01:14:37 +02:00
debug = false;
Prepare for the Guile 2.0 switchover. svn path=/nixpkgs/trunk/; revision=25976
2011-02-15 14:14:29 +01:00
guile = guile_1_8;
Adding trackballs svn path=/nixpkgs/trunk/; revision=15625
2009-05-17 01:14:37 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tunctl = callPackage ../os-specific/linux/tunctl { };
Adding tunctl. I didn't know how to build the manpage, though. svn path=/nixpkgs/trunk/; revision=14290
2009-03-01 22:34:39 +01:00
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
ubootChooser = name : if name == "upstream" then ubootUpstream
else if name == "sheevaplug" then ubootSheevaplug
else if name == "guruplug" then ubootGuruplug
else if name == "nanonote" then ubootNanonote
Simplified much more the expressions for cross building and multiplatform. I introduce the new nixpkgs parameter "platform", defaulting to "pc", which was before defined as an attribute of nixpkgs. I made the crossSystem nixpkgs attribute set parameter contain its own 'platform'. This allows cross-building a kernel for a given crossSystem.platform in a non-PC platform. The actual native platform can be taken from stdenv.platform, and this way we also avoid the constant passing of 'platform' to packages for platform-dependant builds (kernel, initrd, ...). I will update nixos accordingly to these changes, for non-PC platforms to work. I think we are gaining on flexibility and clearness. I could cross build succesfully an ultrasparc kernel and a mipsel kernel on PC. But since this change, I should be able to do this also in non-PC. Before this change, there was no possibility of distinguishing the "target platform" or the "native build platform" when cross building, being the single "platform" attribute always interpreted as target platform. The platform is a quite relevant attribute set, as it determines the linuxHeaders used (in the case, by now the only one supported, of linux targets). The platform attributes are quite linux centric still. Let's hope for more generality to come. svn path=/nixpkgs/trunk/; revision=20273
2010-02-27 18:35:47 +01:00
else throw "Unknown uboot";
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ubootUpstream = callPackage ../misc/uboot { };
Porting changes from stdenv-updates into this branch. This comes from: svn diff ^/nixpkgs/trunk/@18255 ^/nixpkgs/branches/stdenv-updates/ > diff patch -p0 < diff and then adding into svn all files new from the patch. trunk@18255 comes from the last time I updated stdenv-updates from trunk. svn path=/nixpkgs/stdenv-updates2/; revision=18272
2009-11-08 01:32:12 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ubootSheevaplug = callPackage ../misc/uboot/sheevaplug.nix { };
Adding the mainline uboot. svn path=/nixpkgs/trunk/; revision=20078
2010-02-17 21:53:01 +01:00
Adding nanonote kernel and uboot svn path=/nixpkgs/branches/stdenv-updates/; revision=22943
2010-08-04 13:07:13 +02:00
ubootNanonote = callPackage ../misc/uboot/nanonote.nix { };
Add U-Boot for the GuruPlug. svn path=/nixpkgs/trunk/; revision=24060
2010-10-05 00:23:57 +02:00
ubootGuruplug = callPackage ../misc/uboot/guruplug.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
uclibc = callPackage ../os-specific/linux/uclibc { };
Porting changes from stdenv-updates into this branch. This comes from: svn diff ^/nixpkgs/trunk/@18255 ^/nixpkgs/branches/stdenv-updates/ > diff patch -p0 < diff and then adding into svn all files new from the patch. trunk@18255 comes from the last time I updated stdenv-updates from trunk. svn path=/nixpkgs/stdenv-updates2/; revision=18272
2009-11-08 01:32:12 +01:00
Mark some cross-compiled packages as low priority
2012-11-08 16:30:02 +01:00
uclibcCross = lowPrio (callPackage ../os-specific/linux/uclibc {
Trying to get coreutils cross-built with uclibc. This involved fixing some buildInputs/buildNativeInputs in acl/attr, and adding a libiconv in some places. svn path=/nixpkgs/branches/stdenv-updates/; revision=20510
2010-03-09 19:05:38 +01:00
inherit fetchurl stdenv libiconv;
Enabling cross-builds with uclibc again (I had that too much abandoned). Hydra now should even test it. svn path=/nixpkgs/trunk/; revision=20500
2010-03-09 16:48:25 +01:00
linuxHeaders = linuxHeadersCross;
gccCross = gccCrossStageStatic;
cross = assert crossSystem != null; crossSystem;
Mark some cross-compiled packages as low priority
2012-11-08 16:30:02 +01:00
});
Making the cross-builds work with uclibc. There is no easy way of switching between uclibc/glibc still. I started the renaming from glibc to libc regarding the cross-toolchain, but I still have to finish. svn path=/nixpkgs/branches/stdenv-updates/; revision=18801
2009-12-04 14:35:58 +01:00
Add udev145 svn path=/nixpkgs/trunk/; revision=27719
2011-07-11 16:00:17 +02:00
udev145 = callPackage ../os-specific/linux/udev/145.nix { };
Use systemd instead of udev, and don't use consolekit
2012-11-06 13:01:44 +01:00
udev = pkgs.systemd;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
udisks: split to udisks1 (stays default) and udisks2
2013-04-01 18:12:32 +02:00
udisks1 = callPackage ../os-specific/linux/udisks/1-default.nix { };
udisks2 = callPackage ../os-specific/linux/udisks/2-default.nix { };
udisks = udisks1;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Added udisks-glue, a tool to associate udisks-events to actions
2013-10-02 14:48:40 +02:00
udisks_glue = callPackage ../os-specific/linux/udisks-glue { };
synchronize with trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=29696
2011-10-06 15:16:47 +02:00
untie = callPackage ../os-specific/linux/untie { };
Adding untie - a tool for manipulating namespaces svn path=/nixpkgs/trunk/; revision=24819
2010-11-23 08:52:57 +01:00
upower: fix Xfce via --enable-deprecated Also drop older libusb1 version which is no longer needed with newer upower.
2013-11-12 09:59:58 +01:00
upower = callPackage ../os-specific/linux/upower { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28462
2011-08-10 17:51:20 +02:00
upower: add 0.99 version for gnome 3.12
2014-05-19 13:13:32 +02:00
upower_99 = callPackage ../os-specific/linux/upower/0.99.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
upstart = callPackage ../os-specific/linux/upstart { };
* Upstart 0.6.2. svn path=/nixpkgs/trunk/; revision=18056
2009-10-30 19:12:28 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
usbutils = callPackage ../os-specific/linux/usbutils { };
Added djview4 svn path=/nixpkgs/trunk/; revision=9642
2007-11-11 17:52:29 +01:00
usermount: New Package. A simple tool to automatically mount removable drives using UDisks2 and D-Bus. https://github.com/tom5760/usermount
2014-05-29 13:38:13 +02:00
usermount = callPackage ../os-specific/linux/usermount { };
* util-linux 2.20.1. svn path=/nixpkgs/branches/stdenv-updates/; revision=30860
2011-12-12 20:56:17 +01:00
utillinux = lowPrio (callPackage ../os-specific/linux/util-linux {
* Turn vim/default.nix into a regular package. We don't need two configurable VIMs. svn path=/nixpkgs/trunk/; revision=22784
2010-07-28 14:52:54 +02:00
ncurses = null;
util-linux-ng: prepare expression for the addition of perl as a buildInput The chkdupexe utility requires perl. We cannot change the expression, though, without triggering a re-build of almost all of stdenv, so for the time being I'm making Perl an optional build input that is disabled by default. svn path=/nixpkgs/trunk/; revision=27681
2011-07-09 01:11:38 +02:00
perl = null;
git: prefer 'utillinuxcurses' over 'utillinux' in user profiles Packages that need util-linux-ng as a build-time or run-time dependency typically refer to the attribute 'utillinux', which is the expression with the least possible set of features. Users, however, who run "nix-env -i util-linux", don't want that version, because it lacks support for perl and curses. In other words, users want utillinuxngCurses by default, which is what this change accomplishes. svn path=/nixpkgs/trunk/; revision=27749
2011-07-13 12:50:22 +02:00
});
* Added util-linux-ng, a fork of util-linux (which seems unmaintained). svn path=/nixpkgs/trunk/; revision=13712
2009-01-06 10:28:45 +01:00
* util-linux 2.20.1. svn path=/nixpkgs/branches/stdenv-updates/; revision=30860
2011-12-12 20:56:17 +01:00
utillinuxCurses = utillinux.override {
utillinuxngCurses: build this package with perl support enabled This means that chkdupexe will work correctly. svn path=/nixpkgs/trunk/; revision=27682
2011-07-09 01:11:41 +02:00
inherit ncurses perl;
Build e2fsprogs at last svn path=/nixpkgs/trunk/; revision=13719
2009-01-07 00:22:29 +01:00
};
Updating libv4l (part of v4l-utils). I moved v4l-utils to stdenv.mkDerivation style, and it's used to build either libv4l or the utils (with qt4). svn path=/nixpkgs/trunk/; revision=34208
2012-05-22 16:30:12 +02:00
v4l_utils = callPackage ../os-specific/linux/v4l-utils {
withQt4 = true;
};
Adding v4l-utils svn path=/nixpkgs/trunk/; revision=28529
2011-08-13 10:59:00 +02:00
Making wxGTK stay wxGTK even cross-built, so I remove the wxMSW code I added to test the crossbuilding with wxGTK. I added a new windows-specific package: wxMSW. svn path=/nixpkgs/trunk/; revision=21634
2010-05-06 21:19:22 +02:00
windows = rec {
os-specific/windows: Add new package cygwinSetup. This is primarily going to be used for vmTools.runInWindowsVM, but in theory, it could also work with Nix on CygWin which I haven't tested. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-03-03 22:47:05 +01:00
cygwinSetup = callPackage ../os-specific/windows/cygwin-setup { };
Adding windows jom; it does not build for me still, but it's close to it. I think it's better to share it though. I wrote a comment about the expression not building. svn path=/nixpkgs/trunk/; revision=34365
2012-06-05 23:24:27 +02:00
jom = callPackage ../os-specific/windows/jom { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
w32api = callPackage ../os-specific/windows/w32api {
Making wxGTK stay wxGTK even cross-built, so I remove the wxMSW code I added to test the crossbuilding with wxGTK. I added a new windows-specific package: wxMSW. svn path=/nixpkgs/trunk/; revision=21634
2010-05-06 21:19:22 +02:00
gccCross = gccCrossStageStatic;
* Fix eval-release.nix by testing whether all attributes of a derivation evaluate inside the tryEval. This catches cases such as aufs2-util, which fails due to an assertion in its dependency aufs2. * Explicitly blacklist "xbursttools" because it gives some evaluation error in cross-OpenSSL. No idea why, probably due to some pass-through attribute. svn path=/nixpkgs/trunk/; revision=23247
2010-08-19 14:37:10 +02:00
binutilsCross = binutilsCross;
};
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
Making wxGTK stay wxGTK even cross-built, so I remove the wxMSW code I added to test the crossbuilding with wxGTK. I added a new windows-specific package: wxMSW. svn path=/nixpkgs/trunk/; revision=21634
2010-05-06 21:19:22 +02:00
w32api_headers = w32api.override {
onlyHeaders = true;
};
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
mingw_runtime = callPackage ../os-specific/windows/mingwrt {
Making wxGTK stay wxGTK even cross-built, so I remove the wxMSW code I added to test the crossbuilding with wxGTK. I added a new windows-specific package: wxMSW. svn path=/nixpkgs/trunk/; revision=21634
2010-05-06 21:19:22 +02:00
gccCross = gccCrossMingw2;
binutilsCross = binutilsCross;
};
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
Making wxGTK stay wxGTK even cross-built, so I remove the wxMSW code I added to test the crossbuilding with wxGTK. I added a new windows-specific package: wxMSW. svn path=/nixpkgs/trunk/; revision=21634
2010-05-06 21:19:22 +02:00
mingw_runtime_headers = mingw_runtime.override {
onlyHeaders = true;
};
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
Making wxGTK stay wxGTK even cross-built, so I remove the wxMSW code I added to test the crossbuilding with wxGTK. I added a new windows-specific package: wxMSW. svn path=/nixpkgs/trunk/; revision=21634
2010-05-06 21:19:22 +02:00
mingw_headers1 = buildEnv {
name = "mingw-headers-1";
paths = [ w32api_headers mingw_runtime_headers ];
};
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
Making wxGTK stay wxGTK even cross-built, so I remove the wxMSW code I added to test the crossbuilding with wxGTK. I added a new windows-specific package: wxMSW. svn path=/nixpkgs/trunk/; revision=21634
2010-05-06 21:19:22 +02:00
mingw_headers2 = buildEnv {
name = "mingw-headers-2";
paths = [ w32api mingw_runtime_headers ];
};
mingw_headers3 = buildEnv {
name = "mingw-headers-3";
paths = [ w32api mingw_runtime ];
};
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
Trying to add a few bits of mingw-w64. To be tested. svn path=/nixpkgs/trunk/; revision=34228
2012-05-24 23:23:23 +02:00
mingw_w64 = callPackage ../os-specific/windows/mingw-w64 {
gccCross = gccCrossStageStatic;
binutilsCross = binutilsCross;
};
mingw_w64_headers = callPackage ../os-specific/windows/mingw-w64 {
onlyHeaders = true;
};
mingw-w64-pthreads: Create based on mingw-w64. The winpthreads library is part of the same source package, so let's just override the name and the source directory. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-02-24 04:44:43 +01:00
mingw_w64_pthreads = callPackage ../os-specific/windows/mingw-w64 {
onlyPthreads = true;
};
Add pthreads-w32. svn path=/nixpkgs/trunk/; revision=31927
2012-01-30 10:53:45 +01:00
pthreads = callPackage ../os-specific/windows/pthread-w32 {
pthread-win32: use `mingw_headers3', for consistency with `gccCrossStageFinal'
2013-03-29 21:34:53 +01:00
mingw_headers = mingw_headers3;
Add pthreads-w32. svn path=/nixpkgs/trunk/; revision=31927
2012-01-30 10:53:45 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wxMSW = callPackage ../os-specific/windows/wxMSW-2.8 { };
Making gcc-4.5 cross-build to mingw32 too (set by the proper config and libc = "msvcrt" in the crossSystem) svn path=/nixpkgs/trunk/; revision=21630
2010-05-06 20:22:51 +02:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
wesnoth = callPackage ../games/wesnoth {
wesnoth 1.8.5 (patch by Karn Kallio) svn path=/nixpkgs/trunk/; revision=24682
2010-11-13 12:50:43 +01:00
lua = lua5;
forgot to update all-packages.nix svn path=/nixpkgs/trunk/; revision=10530
2008-02-06 22:26:17 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wirelesstools = callPackage ../os-specific/linux/wireless-tools { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Use meta.platforms svn path=/nixpkgs/trunk/; revision=31909
2012-01-28 15:39:56 +01:00
wpa_supplicant = callPackage ../os-specific/linux/wpa_supplicant { };
* ion-3 and elinks added, missprint in qt-4 corrected svn path=/nixpkgs/trunk/; revision=8993
2007-07-17 21:29:53 +02:00
* Fix ugly wpa_supplicant expression. svn path=/nixpkgs/trunk/; revision=32427
2012-02-20 15:26:01 +01:00
wpa_supplicant_gui = callPackage ../os-specific/linux/wpa_supplicant/gui.nix { };
Added qt4 gui front-end package for WPA supplicant svn path=/nixpkgs/trunk/; revision=15578
2009-05-12 20:52:48 +02:00
xf86-input-multitouch seems to be abandoned, update it with the mtrack fork svn path=/nixpkgs/trunk/; revision=33283
2012-03-20 02:48:09 +01:00
xf86_input_mtrack = callPackage ../os-specific/linux/xf86-input-mtrack {
inherit (xorg) utilmacros xproto inputproto xorgserver;
};
Add xf86-input-multitouch svn path=/nixpkgs/trunk/; revision=28369
2011-08-08 03:20:29 +02:00
xf86_input_multitouch =
callPackage ../os-specific/linux/xf86-input-multitouch { };
Added qt4 gui front-end package for WPA supplicant svn path=/nixpkgs/trunk/; revision=15578
2009-05-12 20:52:48 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xf86_input_wacom = callPackage ../os-specific/linux/xf86-input-wacom { };
Initial xf86-input-wacom nix expression Builds here. Haven't tested whether it works with real hardware yet. svn path=/nixpkgs/trunk/; revision=21019
2010-04-12 00:42:28 +02:00
Add xf86-video-nested This does not yet compile. I had a working version from an obsolete github repo, but then found the upstream repo. Perhaps it needs a newer Xorg.
2012-07-16 21:15:54 +02:00
xf86_video_nested = callPackage ../os-specific/linux/xf86-video-nested {
Pin xf86-video-nested to a revision that works with Xorg 7.6
2012-07-17 02:11:59 +02:00
inherit (xorg) fontsproto renderproto utilmacros xorgserver;
Add xf86-video-nested This does not yet compile. I had a working version from an obsolete github repo, but then found the upstream repo. Perhaps it needs a newer Xorg.
2012-07-16 21:15:54 +02:00
};
xorg: move nouveau driver here, some updates of modules It seems that most of the modules is rarely used, but still. Some of the updated modules don't build, just as they didn't before.
2014-01-17 20:43:54 +01:00
xf86_video_nouveau = xorg.xf86videonouveau;
Add nouveau xorg video driver svn path=/nixpkgs/trunk/; revision=33300
2012-03-20 17:29:22 +01:00
Added Open Dynamics Engine svn path=/nixpkgs/trunk/; revision=13520
2008-11-30 17:50:05 +01:00
xmoto = builderDefsPackage (import ../games/xmoto) {
inherit chipmunk sqlite curl zlib bzip2 libjpeg libpng
freeglut mesa SDL SDL_mixer SDL_image SDL_net SDL_ttf
xmoto-0.5.9+libpng-1.5 patch svn path=/nixpkgs/trunk/; revision=31447
2012-01-09 00:31:31 +01:00
lua5 ode libxdg_basedir libxml2;
Added Open Dynamics Engine svn path=/nixpkgs/trunk/; revision=13520
2008-11-30 17:50:05 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xorg_sys_opengl = callPackage ../os-specific/linux/opengl/xorg-sys { };
* Emacs 22.1. This is the default now, but 21.4 is still around (as is the 23.0.0.1 alpha). svn path=/nixpkgs/trunk/; revision=9175
2007-08-20 15:48:56 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
zd1211fw = callPackage ../os-specific/linux/firmware/zd1211 { };
* Added Sylpheed 1.9.11 (beta for GTK 2). svn path=/nixpkgs/trunk/; revision=3149
2005-05-26 22:09:29 +02:00
Consistent whitespace
2013-06-13 15:18:16 +02:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### DATA
* Added Valknut. svn path=/nixpkgs/trunk/; revision=3746
2005-08-30 09:39:38 +02:00
Adding andagii font svn path=/nixpkgs/trunk/; revision=24610
2010-11-06 10:45:13 +01:00
andagii = callPackage ../data/fonts/andagii {};
Adding Anonymous Pro font svn path=/nixpkgs/trunk/; revision=24840
2010-11-24 12:51:50 +01:00
anonymousPro = callPackage ../data/fonts/anonymous-pro {};
Minor cleanup
2012-11-29 14:40:25 +01:00
arkpandora_ttf = builderDefsPackage (import ../data/fonts/arkpandora) { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
aurulent-sans: new expression
2014-06-18 02:12:10 +02:00
aurulent-sans = callPackage ../data/fonts/aurulent-sans { };
baekmuk-ttf: new package baekmuk-ttf: new package
2014-09-03 11:05:20 +02:00
baekmuk-ttf = callPackage ../data/fonts/baekmuk-ttf { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bakoma_ttf = callPackage ../data/fonts/bakoma-ttf { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cacert = callPackage ../data/misc/cacert { };
* Added a bundle of CA certificates, useful for e.g. curl. svn path=/nixpkgs/trunk/; revision=19571
2010-01-20 15:10:26 +01:00
Add cantarell-fonts, part of GNOME-3 svn path=/nixpkgs/trunk/; revision=31375
2012-01-06 21:10:23 +01:00
cantarell_fonts = callPackage ../data/fonts/cantarell-fonts { };
Add comic-neue font.
2014-08-19 15:03:21 +02:00
comic-neue = callPackage ../data/fonts/comic-neue { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
corefonts = callPackage ../data/fonts/corefonts { };
exrviewer added (needs ctl openexr openexr_ctl) fltk update ilmbase updated ndiswrapper does compile but has to be integrated into the kernel somehow svn path=/nixpkgs/trunk/; revision=9863
2007-12-05 22:25:47 +01:00
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
wrapFonts = paths : ((import ../data/fonts/fontWrap) {
Remove ttmkfdir reference svn path=/nixpkgs/trunk/; revision=24659
2010-11-11 13:27:39 +01:00
inherit fetchurl stdenv builderDefs paths;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
inherit (xorg) mkfontdir mkfontscale;
});
Added fbpanel - desktop panel. svn path=/nixpkgs/trunk/; revision=9774
2007-11-22 05:23:27 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
clearlyU = callPackage ../data/fonts/clearlyU { };
Added template to use deb-package wrapper. svn path=/nixpkgs/trunk/; revision=10911
2008-03-02 19:41:32 +01:00
Adding CM-Unicode fonts svn path=/nixpkgs/trunk/; revision=27311
2011-05-28 21:51:08 +02:00
cm_unicode = callPackage ../data/fonts/cm-unicode {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
dejavu_fonts = callPackage ../data/fonts/dejavu-fonts {
* Drop the "perl" prefix from Perl attribute names. It's redundant now that Perl packages are in their own namespace (perlPackages.<pkg>). svn path=/nixpkgs/trunk/; revision=15176
2009-04-20 14:49:35 +02:00
inherit (perlPackages) FontTTF;
Added template to use deb-package wrapper. svn path=/nixpkgs/trunk/; revision=10911
2008-03-02 19:41:32 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
docbook5 = callPackage ../data/sgml+xml/schemas/docbook-5.0 { };
Added fbpanel - desktop panel. svn path=/nixpkgs/trunk/; revision=9774
2007-11-22 05:23:27 +01:00
Adding the sgml dtd for docbook 3.1 Required by iputils manpages.
2013-03-18 15:05:08 +01:00
docbook_sgml_dtd_31 = callPackage ../data/sgml+xml/schemas/sgml-dtd/docbook/3.1.nix { };
* Added the Docbook 4.1 SGML DTDs. * Fixed the "docbook2man --sgml" command in docbook2x. * Fixed the module-init-tools manual pages. svn path=/nixpkgs/trunk/; revision=30165
2011-11-01 17:47:18 +01:00
docbook_sgml_dtd_41 = callPackage ../data/sgml+xml/schemas/sgml-dtd/docbook/4.1.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
docbook_xml_dtd_412 = callPackage ../data/sgml+xml/schemas/xml-dtd/docbook/4.1.2.nix { };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
docbook_xml_dtd_42 = callPackage ../data/sgml+xml/schemas/xml-dtd/docbook/4.2.nix { };
add the mozilla browser. The compilation process is nearly identical to firefox, but there are some differences: - don't source in $topsrcdir/browser/config/mozconfig (does not exist it seems) - different source tarball (different version that is) - leave out the postinstall phase svn path=/nixpkgs/trunk/; revision=4116
2005-10-22 13:51:30 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
docbook_xml_dtd_43 = callPackage ../data/sgml+xml/schemas/xml-dtd/docbook/4.3.nix { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
docbook_xml_dtd_45 = callPackage ../data/sgml+xml/schemas/xml-dtd/docbook/4.5.nix { };
pkgs/data/sgml+xml/schemas/xml-dtd/docbook/4.5.nix: added docbook 4.5 XML DTD The new asciidoc version generates docbook output for this version. svn path=/nixpkgs/trunk/; revision=18077
2009-11-03 16:57:27 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
docbook_xml_ebnf_dtd = callPackage ../data/sgml+xml/schemas/xml-dtd/docbook-ebnf { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
docbook_xml_xslt = docbook_xsl;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
docbook_xsl = callPackage ../data/sgml+xml/stylesheets/xslt/docbook-xsl { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* docbook-xsl / docbook-xsl-ns: match the upstream package name. Also updated docbook-xsl-ns. svn path=/nixpkgs/trunk/; revision=16356
2009-07-14 17:02:56 +02:00
docbook5_xsl = docbook_xsl_ns;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
docbook_xsl_ns = callPackage ../data/sgml+xml/stylesheets/xslt/docbook-xsl-ns { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Add fonts from the DOSEmu project. These are mainly fonts like the DOS standard VGA fonts.
2012-06-04 21:57:56 +02:00
dosemu_fonts = callPackage ../data/fonts/dosemu-fonts { };
Add eb-garamond font (close #2553) @vcunat added license, changed attribute name according to the [rules], and trivial refactoring. [rules]: http://nixos.org/nixpkgs/manual/#idm140333184443184 ("package naming")
2014-05-07 09:56:41 +02:00
eb-garamond = callPackage ../data/fonts/eb-garamond { };
Add Fira font. Fira is the font for FirefoxOS. - https://github.com/mozilla/Fira - http://www.carrois.com/fira-3-1/
2014-08-19 18:00:06 +02:00
fira = callPackage ../data/fonts/fira { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
freefont_ttf = callPackage ../data/fonts/freefont-ttf { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
freepats: new package freepats is a project to create a free and open set of instrument patches, in any format, that can be used with softsynths. I'm adding it because it is needed for WildMIDI, which is needed for MIDI support in Qmmp (audio player). I'll add WildMIDI and Qmmp in the next commit(s).
2013-05-18 20:03:03 +02:00
freepats = callPackage ../data/misc/freepats { };
Adding Gentium font svn path=/nixpkgs/trunk/; revision=27310
2011-05-28 21:01:59 +02:00
gentium = callPackage ../data/fonts/gentium {};
Move last piece o gnome3 to top-level Since there is no common release schedule, I'd prefer to avoid gnome3 set at all. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33203
2012-03-17 17:46:12 +01:00
gnome_user_docs = callPackage ../data/documentation/gnome-user-docs { };
update gsettings-desktop-schemas and make system-wide Conflicts: pkgs/data/misc/gsettings-desktop-schemas/default.nix pkgs/desktops/gnome-3/core/gsettings-desktop-schemas/default.nix
2013-02-21 20:42:28 +01:00
inherit (gnome3) gsettings_desktop_schemas;
Move gsettings-desktop-schemas to data/misc svn path=/nixpkgs/trunk/; revision=32929
2012-03-08 23:45:58 +01:00
hicolor-icon-theme: Move to data/icons
2013-08-15 16:53:40 +02:00
hicolor_icon_theme = callPackage ../data/icons/hicolor-icon-theme { };
pkgs/top-level/all-packages.nix: strip trailing whitenspace svn path=/nixpkgs/trunk/; revision=23118
2010-08-11 17:49:42 +02:00
Add inconsolata font svn path=/nixpkgs/trunk/; revision=24839
2010-11-24 12:19:38 +01:00
inconsolata = callPackage ../data/fonts/inconsolata {};
Added package for Japanese IPAFonts.
2014-06-15 18:02:41 +02:00
ipafont = callPackage ../data/fonts/ipafont {};
* Added pkgs/data/misc/hicolor-icon-theme, required by Xfce. svn path=/nixpkgs/trunk/; revision=23060
2010-08-09 20:00:08 +02:00
junicode = callPackage ../data/fonts/junicode { };
Moved kochi-mincho and kochi-gothic back into one package.
2014-06-12 06:18:05 +02:00
kochi-substitute = callPackage ../data/fonts/kochi-substitute {};
Added kochi-substitute entry in all-packages.nix.
2014-06-05 02:59:14 +02:00
Re-added the non-free kochi-substitute with naga10 glyphs.
2014-06-13 05:33:23 +02:00
kochi-substitute-naga10 = callPackage ../data/fonts/kochi-substitute-naga10 {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
liberation_ttf = callPackage ../data/fonts/redhat-liberation-fonts { };
Added template to use deb-package wrapper. svn path=/nixpkgs/trunk/; revision=10911
2008-03-02 19:41:32 +01:00
Update Libertine font svn path=/nixpkgs/trunk/; revision=27295
2011-05-24 17:13:54 +02:00
libertine = builderDefsPackage (import ../data/fonts/libertine) {
Libertine fonts: update and cleanup.
2013-01-10 22:34:05 +01:00
inherit fetchurl fontforge lib;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
Added font building support to builder-defs; made realCurl configurable; added Linux Libertine font; added ConTEXt svn path=/nixpkgs/trunk/; revision=11739
2008-04-28 12:10:44 +02:00
LMMath: add Latin Modern Math font
2012-07-19 07:07:57 +02:00
lmmath = callPackage ../data/fonts/lmodern/lmmath.nix {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lmodern = callPackage ../data/fonts/lmodern { };
all-packages.nix changes for two previous commits svn path=/nixpkgs/trunk/; revision=11728
2008-04-26 17:23:46 +02:00
add lohit-fonts-20140220
2014-05-25 21:17:23 +02:00
lohit-fonts = callPackage ../data/fonts/lohit-fonts { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
manpages = callPackage ../data/documentation/man-pages { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
miscfiles = callPackage ../data/misc/miscfiles { };
Adding bsdgames and miscfiles (this later, for 'words') I could not easily make some bsdgames build or install. Too much patching against the installer trying to write beyond the nix store. svn path=/nixpkgs/trunk/; revision=17971
2009-10-27 00:03:36 +01:00
Add mobile-broadband-provider-info svn path=/nixpkgs/trunk/; revision=31328
2012-01-06 00:25:28 +01:00
mobile_broadband_provider_info = callPackage ../data/misc/mobile-broadband-provider-info { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mph_2b_damase = callPackage ../data/fonts/mph-2b-damase { };
Added template to use deb-package wrapper. svn path=/nixpkgs/trunk/; revision=10911
2008-03-02 19:41:32 +01:00
Nafees font family (5 fonts)
2014-05-22 19:21:28 +02:00
nafees = callPackage ../data/fonts/nafees { };
Adding Old Standard font svn path=/nixpkgs/trunk/; revision=27307
2011-05-28 17:46:09 +02:00
oldstandard = callPackage ../data/fonts/oldstandard { };
opensans-ttf: Fix attribute name
2014-07-22 15:13:09 +02:00
opensans-ttf = callPackage ../data/fonts/opensans-ttf { };
Package for Open Sans fonts.
2014-07-15 19:35:22 +02:00
First attempt at data/fonts/poly
2014-05-06 09:48:04 +02:00
poly = callPackage ../data/fonts/poly { };
Revert "man-pages-posix: renamed attribute for consistency with other man page sets". svn path=/nixpkgs/trunk/; revision=26490
2011-03-24 13:05:34 +01:00
posix_man_pages = callPackage ../data/documentation/man-pages-posix { };
* Added man-pages-posix (contributed by Vladimír Čunát). svn path=/nixpkgs/trunk/; revision=26485
2011-03-24 12:44:43 +01:00
Add proggyfonts collection The Proggy Fonts are a font collection intended for fixed-width uses like programming languages. Signed-off-by: Josh Cartwright <joshc@eso.teric.us>
2014-09-03 03:44:36 +02:00
proggyfonts = callPackage ../data/fonts/proggyfonts { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pthreadmanpages = callPackage ../data/documentation/pthread-man-pages { };
Add pthread man pages from LinuxThreads. svn path=/nixpkgs/trunk/; revision=14837
2009-04-02 16:30:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
shared_mime_info = callPackage ../data/misc/shared-mime-info { };
pkgs/applications/editors/emacs-modes/magit: updated to version magit-0.7-94-gbf42bf8 Magit has seen plenty of development since version 0.7, but for some reason there haven't been any new releases. This version bump updates the expression to build a current version of Magit directly from the Git repository. This change adds buildInputs 'autoconf' and 'automake'. These tools are required only because we aren't building from a proper release tarball. Once version 0.8 comes out, these dependencies can be dropped again. svn path=/nixpkgs/trunk/; revision=20650
2010-03-16 13:13:40 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
shared_desktop_ontologies = callPackage ../data/misc/shared-desktop-ontologies { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
stdmanpages = callPackage ../data/documentation/std-man-pages { };
Adding C++ std man pages. svn path=/nixpkgs/trunk/; revision=14771
2009-03-30 10:14:19 +02:00
Add Symbola font
2014-02-28 18:55:07 +01:00
symbola = callPackage ../data/fonts/symbola { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iana_etc = callPackage ../data/misc/iana-etc { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Let poppler use ${POPPLER_DATADIR} Also upgrade poppler-data svn path=/nixpkgs/trunk/; revision=29342
2011-09-19 10:35:30 +02:00
poppler_data = callPackage ../data/misc/poppler-data { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
r3rs = callPackage ../data/documentation/rnrs/r3rs.nix { };
Add R[345]RS, revisions of the Report on the Algorithmic Language Scheme. svn path=/nixpkgs/trunk/; revision=11307
2008-03-27 15:40:08 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
r4rs = callPackage ../data/documentation/rnrs/r4rs.nix { };
Add R[345]RS, revisions of the Report on the Algorithmic Language Scheme. svn path=/nixpkgs/trunk/; revision=11307
2008-03-27 15:40:08 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
r5rs = callPackage ../data/documentation/rnrs/r5rs.nix { };
Add R[345]RS, revisions of the Report on the Algorithmic Language Scheme. svn path=/nixpkgs/trunk/; revision=11307
2008-03-27 15:40:08 +01:00
Rename SourceCodePro to source-code-pro
2014-07-08 22:54:17 +02:00
source-code-pro = callPackage ../data/fonts/source-code-pro {};
Source Code Pro font
2014-05-07 01:45:54 +02:00
Add source-sans-pro-1.050
2014-05-26 21:55:32 +02:00
source-sans-pro = callPackage ../data/fonts/source-sans-pro { };
Add source-serif-pro-1.014
2014-05-26 21:58:31 +02:00
source-serif-pro = callPackage ../data/fonts/source-serif-pro { };
Source Code Pro font
2014-05-07 01:45:54 +02:00
add source-han-sans-japanese, source-han-sans-korean, source-han-sans-simplified-chinese, source-han-sans-traditional-chinese: An open source Pan-CJK typeface
2014-07-16 15:41:32 +02:00
source-han-sans-japanese = callPackage ../data/fonts/source-han-sans/japanese.nix {};
source-han-sans-korean = callPackage ../data/fonts/source-han-sans/korean.nix {};
source-han-sans-simplified-chinese = callPackage ../data/fonts/source-han-sans/simplified-chinese.nix {};
source-han-sans-traditional-chinese = callPackage ../data/fonts/source-han-sans/traditional-chinese.nix {};
Source Code Pro font
2014-05-07 01:45:54 +02:00
tango-icon-theme: Add
2013-08-15 18:01:16 +02:00
tango-icon-theme = callPackage ../data/icons/tango-icon-theme { };
Copied Green theme declaration from NixOS source here svn path=/nixpkgs/trunk/; revision=13725
2009-01-08 23:21:32 +01:00
themes = name: import (../data/misc/themes + ("/" + name + ".nix")) {
inherit fetchurl;
};
Adding Theano font svn path=/nixpkgs/trunk/; revision=27308
2011-05-28 17:59:45 +02:00
theano = callPackage ../data/fonts/theano { };
Add Tempora-LGC font svn path=/nixpkgs/trunk/; revision=27309
2011-05-28 18:04:02 +02:00
tempora_lgc = callPackage ../data/fonts/tempora-lgc { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
terminus_font = callPackage ../data/fonts/terminus-font { };
data/fonts/terminus-font: New nixpkg. svn path=/nixpkgs/trunk/; revision=19855
2010-02-06 23:28:39 +01:00
TeXLive: update to 2012 snapshot from Debian
2012-07-13 16:18:52 +02:00
tipa = callPackage ../data/fonts/tipa { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ttf_bitstream_vera = callPackage ../data/fonts/ttf-bitstream-vera { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Add tzdata Glibc 2.16 no longer contains timezone data (yay!) so provide tzdata instead.
2012-09-18 19:14:22 +02:00
tzdata = callPackage ../data/misc/tzdata { };
Reordered alphabetically
2012-06-23 01:26:39 +02:00
ubuntu_font_family = callPackage ../data/fonts/ubuntu-font-family { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ucsFonts = callPackage ../data/fonts/ucs-fonts { };
Added UCS-fonts svn path=/nixpkgs/trunk/; revision=10915
2008-03-02 20:19:34 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
unifont = callPackage ../data/fonts/unifont { };
Added template to use deb-package wrapper. svn path=/nixpkgs/trunk/; revision=10911
2008-03-02 19:41:32 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vistafonts = callPackage ../data/fonts/vista-fonts { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Add wqy-microhei font
2014-02-08 15:37:40 +01:00
wqy_microhei = callPackage ../data/fonts/wqy-microhei { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wqy_zenhei = callPackage ../data/fonts/wqy-zenhei { };
Added template to use deb-package wrapper. svn path=/nixpkgs/trunk/; revision=10911
2008-03-02 19:41:32 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xhtml1 = callPackage ../data/sgml+xml/schemas/xml-dtd/xhtml1 { };
* XHTML 1.0 DTDs. svn path=/nixpkgs/trunk/; revision=17185
2009-09-16 14:25:22 +02:00
xorg xkeyboard-config: update, unify with the other expression
2014-01-30 13:46:02 +01:00
xkeyboard_config = xorg.xkeyboardconfig;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
### APPLICATIONS
Adding a2jmidid, a daemon for exposing legacy ALSA sequencer applications in JACK MIDI system svn path=/nixpkgs/trunk/; revision=33668
2012-04-08 02:28:37 +02:00
a2jmidid = callPackage ../applications/audio/a2jmidid { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage_i686 for i686-only packages. svn path=/nixpkgs/trunk/; revision=23113
2010-08-11 15:25:30 +02:00
aangifte2006 = callPackage_i686 ../applications/taxes/aangifte-2006 { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage_i686 for i686-only packages. svn path=/nixpkgs/trunk/; revision=23113
2010-08-11 15:25:30 +02:00
aangifte2007 = callPackage_i686 ../applications/taxes/aangifte-2007 { };
* Aangifte 2007. svn path=/nixpkgs/trunk/; revision=11134
2008-03-15 22:45:57 +01:00
* Use callPackage_i686 for i686-only packages. svn path=/nixpkgs/trunk/; revision=23113
2010-08-11 15:25:30 +02:00
aangifte2008 = callPackage_i686 ../applications/taxes/aangifte-2008 { };
* Added the Dutch Tax Return program for 2009. svn path=/nixpkgs/trunk/; revision=20828
2010-03-25 20:40:19 +01:00
* Use callPackage_i686 for i686-only packages. svn path=/nixpkgs/trunk/; revision=23113
2010-08-11 15:25:30 +02:00
aangifte2009 = callPackage_i686 ../applications/taxes/aangifte-2009 { };
* Aangifte 2007. svn path=/nixpkgs/trunk/; revision=11134
2008-03-15 22:45:57 +01:00
* Add Aangifte 2010. svn path=/nixpkgs/trunk/; revision=26473
2011-03-23 17:06:36 +01:00
aangifte2010 = callPackage_i686 ../applications/taxes/aangifte-2010 { };
* It's that time of year again. svn path=/nixpkgs/trunk/; revision=32976
2012-03-10 20:23:04 +01:00
aangifte2011 = callPackage_i686 ../applications/taxes/aangifte-2011 { };
add dutch tax application for 2012
2013-03-21 14:55:42 +01:00
aangifte2012 = callPackage_i686 ../applications/taxes/aangifte-2012 { };
Add aangifte-2013
2014-03-01 16:54:07 +01:00
aangifte2013 = callPackage_i686 ../applications/taxes/aangifte-2013 { };
Merge branch 'master' into stdenv-updates. Conflicts have been resolved in: pkgs/tools/misc/file/default.nix pkgs/top-level/all-packages.nix pkgs/top-level/python-packages.nix
2012-11-21 16:20:36 +01:00
abcde = callPackage ../applications/audio/abcde {
Updated version of abcde to 2.5.4 - Added support for MusicBrainz queries to abcde package - Added new dependencies to abcde: mkcue, eject, perl, MusicBrainz, MusicBrainzDiscID - libdiscid version in pkg-config was incorrect; patched libdiscid to fix - Added WebServices::MusicBrainz Perl module - Added MusicBrainz::DiscID Perl module - Commented out XSLoader Perl module since it was broken, no packages depend on it, and it has been incorporated into the Perl core
2012-10-28 00:13:56 +02:00
inherit (perlPackages) DigestSHA MusicBrainz MusicBrainzDiscID;
libcdio-0.82 for abcde libcdio-0.9x lacks cd-paranoia needed by abcde. Bring back 0.82 for abcde until we sort out where cd-paranoia went to.
2014-02-02 21:29:08 +01:00
libcdio = libcdio082;
Updated version of abcde to 2.5.4 - Added support for MusicBrainz queries to abcde package - Added new dependencies to abcde: mkcue, eject, perl, MusicBrainz, MusicBrainzDiscID - libdiscid version in pkg-config was incorrect; patched libdiscid to fix - Added WebServices::MusicBrainz Perl module - Added MusicBrainz::DiscID Perl module - Commented out XSLoader Perl module since it was broken, no packages depend on it, and it has been incorporated into the Perl core
2012-10-28 00:13:56 +02:00
};
Add abcde, a command-line CD encoder. svn path=/nixpkgs/trunk/; revision=11904
2008-05-26 22:54:34 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
abiword = callPackage ../applications/office/abiword {
update to 2.8.1 svn path=/nixpkgs/trunk/; revision=19113
2009-12-25 16:45:06 +01:00
inherit (gnome) libglade libgnomecanvas;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
Added abook 0.6.0pre2 Abook is a text-based addressbook program designed to use with mutt mail client.
2013-09-05 19:03:28 +02:00
abook = callPackage ../applications/misc/abook { };
adobe-reader: Update to 9.5.5
2013-11-04 18:42:28 +01:00
adobe-reader = callPackage_i686 ../applications/misc/adobe-reader { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
aewan: New package, version 1.0.01. This adds a small ASCII art drawing tool, which supports drawing with multiple layers. Might be especially helpful for larger "images", which become quite tedious to do using vim. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-09-14 23:11:07 +02:00
aewan = callPackage ../applications/editors/aewan { };
adding alchemy painting application
2013-05-22 19:03:49 +02:00
alchemy = callPackage ../applications/graphics/alchemy { };
add ams-lv2: An LV2 port of the internal modules found in Alsa Modular Synth
2014-03-09 22:13:51 +01:00
ams-lv2 = callPackage ../applications/audio/ams-lv2 { };
a change I missed for the amsn update. svn path=/nixpkgs/trunk/; revision=30421
2011-11-14 10:59:30 +01:00
amsn = callPackage ../applications/networking/instant-messengers/amsn { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
antiword: added version 0.37 svn path=/nixpkgs/trunk/; revision=28938
2011-08-31 13:55:51 +02:00
antiword = callPackage ../applications/office/antiword {};
ardour: make ardour3 the default and remove ardour 2, it doesn't build
2014-03-16 11:32:56 +01:00
ardour = ardour3;
adding ardour svn path=/nixpkgs/trunk/; revision=17327
2009-09-21 11:58:41 +02:00
ardour: make ardour3 the default and remove ardour 2, it doesn't build
2014-03-16 11:32:56 +01:00
ardour3 = lowPrio (callPackage ../applications/audio/ardour {
Adding Ardour3 alpha2, a digital audio workstation svn path=/nixpkgs/trunk/; revision=27075
2011-05-01 16:45:52 +02:00
inherit (gnome) libgnomecanvas libgnomecanvasmm;
});
Arora: packaged svn path=/nixpkgs/trunk/; revision=23877
2010-09-21 00:16:16 +02:00
arora = callPackage ../applications/networking/browsers/arora { };
Add github atom, a hackable text editor for the 21st Century
2014-06-07 12:45:33 +02:00
atom = callPackage ../applications/editors/atom {
gconf = gnome.GConf;
};
Use old giflib for packages which lack new versions/compatibility patches for giflib5
2013-12-08 11:36:46 +01:00
aseprite = callPackage ../applications/editors/aseprite {
giflib = giflib_4_1;
};
add aseprite 0.9.5
2013-09-28 16:57:14 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
audacious = callPackage ../applications/audio/audacious { };
* Added Audacious, a fork of beep-media-player (which doesn't seem to work very well after the Glibc update), plus its dependencies. TODO: make an audacious-wrapper that lets Audacious find its plugins automatically. Currently you have to install audacious-plugins and symlink ~/.nix-profile/lib/audacious/* in ~/.local/share/audacious/Plugins. svn path=/nixpkgs/trunk/; revision=10927
2008-03-03 11:55:20 +01:00
audacity: pin to ffmpeg 0.10
2013-12-23 10:50:56 +01:00
audacity = callPackage ../applications/audio/audacity {
ffmpeg = ffmpeg_0_10;
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Attempt at compiling MilkyTracker, but recent zlib version may have broken it. There's a zlib version included with milkytracker, but there's no makefiles for it. I've only included the header here, but it fails at link-time with several 'undefined reference' errors, which simply means it can't find the definitions, e.g. compiled zlib. There's bug reports on other package systems although unfortunately still unresolved. https://bugs.archlinux.org/task/31324 http://lists.freebsd.org/pipermail/freebsd-ports/2013-March/082180.html
2013-10-29 17:14:53 +01:00
milkytracker = callPackage ../applications/audio/milkytracker { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
aumix = callPackage ../applications/audio/aumix {
Add Aumix, an audio mixer. svn path=/nixpkgs/trunk/; revision=10627
2008-02-11 22:45:52 +01:00
gtkGUI = false;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
autopanosiftc = callPackage ../applications/graphics/autopanosiftc { };
Adding autopano-sift-C, a C implementation of autopano-sift, made by the hugin people. svn path=/nixpkgs/trunk/; revision=14916
2009-04-07 21:15:53 +02:00
Minor cleanup
2012-11-29 14:40:25 +01:00
avidemux = callPackage ../applications/video/avidemux { };
Adding avidemux. svn path=/nixpkgs/trunk/; revision=18584
2009-11-24 09:27:18 +01:00
Trying to fix avogadro -> kdeedu avogadro also wants eigen2.
2012-12-14 12:52:34 +01:00
avogadro = callPackage ../applications/science/chemistry/avogadro {
eigen = eigen2;
};
Add avogadro svn path=/nixpkgs/trunk/; revision=28596
2011-08-15 20:05:39 +02:00
avrdudess: new package AVRDUDESS is a GUI for AVRDUDE. In other words, it is a GUI for programming AVR microcontrollers.
2014-05-31 16:23:02 +02:00
avrdudess = callPackage ../applications/misc/avrdudess { };
Adding avxsynth. To add it, I also add ffms and log4cpp.
2013-04-10 15:12:02 +02:00
avxsynth = callPackage ../applications/video/avxsynth { };
awesome-3-5: add expression and nixos module
2013-11-13 03:34:49 +01:00
awesome-3-4 = callPackage ../applications/window-managers/awesome/3.4.nix {
Adding 'awesome' (and two packages it was depending on) svn path=/nixpkgs/trunk/; revision=20385
2010-03-04 15:44:56 +01:00
lua = lua5;
Explicit pkgs.prefix svn path=/nixpkgs/trunk/; revision=23329
2010-08-21 21:27:31 +02:00
cairo = cairo.override { xcbSupport = true; };
Adding 'awesome' (and two packages it was depending on) svn path=/nixpkgs/trunk/; revision=20385
2010-03-04 15:44:56 +01:00
};
awesome-3-5: add expression and nixos module
2013-11-13 03:34:49 +01:00
awesome-3-5 = callPackage ../applications/window-managers/awesome {
lua = lua5_1;
cairo = cairo.override { xcbSupport = true; };
};
awesome = awesome-3-5;
Adding 'awesome' (and two packages it was depending on) svn path=/nixpkgs/trunk/; revision=20385
2010-03-04 15:44:56 +01:00
baobab: new package Graphical application to analyse disk usage in any Gnome environment. https://wiki.gnome.org/Apps/Baobab
2014-02-15 22:21:06 +01:00
inherit (gnome3) baobab;
backintime: Definition improvement
2014-08-31 18:04:51 +02:00
backintime-common = callPackage ../applications/networking/sync/backintime/common.nix { };
backintime-gnome = callPackage ../applications/networking/sync/backintime/gnome.nix { };
backintime = backintime-gnome;
backintime: a simple backup tool
2014-08-30 17:33:04 +02:00
Add the bspwm window manager to Nix.
2014-08-09 23:31:05 +02:00
bar = callPackage ../applications/window-managers/bar { };
baresip: pin to ffmpeg 1
2013-12-16 14:38:07 +01:00
baresip = callPackage ../applications/networking/instant-messengers/baresip {
ffmpeg = ffmpeg_1;
};
Added BareSIP
2012-09-24 19:02:19 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
batik = callPackage ../applications/graphics/batik { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Bazaar: update to 2.3.1. svn path=/nixpkgs/branches/modular-python/; revision=26573
2011-03-28 17:47:50 +02:00
bazaar = callPackage ../applications/version-management/bazaar { };
* makeWrapper: new function that transparently takes care of creating a wrapper script. E.g. wrapProgram $out/bin/prog --set FOO bar will create a wrapper around "prog" so that the environment variable FOO is set to bar. The original program is renamed to $out/bin/.wrapped-prog. * Function makeSetupHook to convert a script into a setup hook which can be included in buildInputs. This makes it easier to use scripts like makeWrapper. * Added Bazaar, yet another distributed version management system. svn path=/nixpkgs/trunk/; revision=10211
2008-01-18 11:29:58 +01:00
Added bazaar tools (not installed globally, just copied to share, you have to symlink them to your ~/.bazaar/plugins). Also readline support for python. svn path=/nixpkgs/trunk/; revision=11893
2008-05-26 13:39:08 +02:00
bazaarTools = builderDefsPackage (import ../applications/version-management/bazaar/tools.nix) {
inherit bazaar;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
Added bazaar tools (not installed globally, just copied to share, you have to symlink them to your ~/.bazaar/plugins). Also readline support for python. svn path=/nixpkgs/trunk/; revision=11893
2008-05-26 13:39:08 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
beast = callPackage ../applications/audio/beast {
added beast Sound Engine svn path=/nixpkgs/trunk/; revision=12647
2008-08-18 12:50:16 +02:00
inherit (gnome) libgnomecanvas libart_lgpl;
Prepare for the Guile 2.0 switchover. svn path=/nixpkgs/trunk/; revision=25976
2011-02-15 14:14:29 +01:00
guile = guile_1_8;
added beast Sound Engine svn path=/nixpkgs/trunk/; revision=12647
2008-08-18 12:50:16 +02:00
};
Wrap kde-related packages in kdePackagesFor This lets hydra build kde packages for all available KDE releases. Will commit NixOS-fix in a few minutes. svn path=/nixpkgs/trunk/; revision=28833
2011-08-26 15:49:23 +02:00
bibletime = callPackage ../applications/misc/bibletime { };
Add Bitbee-OTR, an unofficial version of Bitlbee with OTR support. svn path=/nixpkgs/trunk/; revision=12925
2008-09-26 11:03:22 +02:00
bitcoin: add support for altcoins
2014-04-17 14:43:05 +02:00
bitcoin = callPackage ../applications/misc/bitcoin {};
bitcoind = callPackage ../applications/misc/bitcoin { gui = false; };
altcoins = recurseIntoAttrs (
dogecoin: autotools build factored out
2014-08-29 22:43:03 +02:00
(callPackage ../applications/misc/bitcoin/altcoins.nix {}) //
(callPackage ../applications/misc/bitcoin/dogecoin.nix {})
bitcoin: add support for altcoins
2014-04-17 14:43:05 +02:00
);
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
BitlBee: Use GnuTLS 2.x. svn path=/nixpkgs/trunk/; revision=29445
2011-09-22 21:46:39 +02:00
bitlbee = callPackage ../applications/networking/instant-messengers/bitlbee {
Fresh bitlbee builds with GNU TLS 3
2014-03-05 10:26:41 +01:00
gnutls = gnutls;
libotr: adding back libotr 3.2; bitlbee failed without it
2013-04-15 20:13:49 +02:00
libotr = libotr_3_2;
BitlBee: Use GnuTLS 2.x. svn path=/nixpkgs/trunk/; revision=29445
2011-09-22 21:46:39 +02:00
};
* Merged most of the stdenv-updates branch. Some stuff didn't merge cleanly right away (kde-4, kernel stuff) so it should be merged later. But the stdenv stuff is all there. svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10793
2008-02-21 00:02:41 +01:00
Updating blender to 2.67. Maybe this will build in stdenv-updates too. I remove the blender 2.49; I think I don't need it anymore. svn path=/nixpkgs/trunk/; revision=32599
2012-02-26 21:47:12 +01:00
blender = callPackage ../applications/misc/blender {
blender: Update to 2.71
2014-07-15 22:52:23 +02:00
python = python34;
Updating blender to 2.67. Maybe this will build in stdenv-updates too. I remove the blender 2.49; I think I don't need it anymore. svn path=/nixpkgs/trunk/; revision=32599
2012-02-26 21:47:12 +01:00
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Add Bristol: a range of synthesiser, electric piano and organ emulations
2012-11-22 00:08:28 +01:00
bristol = callPackage ../applications/audio/bristol { };
Add the bspwm window manager to Nix.
2014-08-09 23:31:05 +02:00
bspwm = callPackage ../applications/window-managers/bspwm { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bvi = callPackage ../applications/editors/bvi { };
svn path=/nixpkgs/trunk/; revision=10233
2008-01-20 23:47:08 +01:00
Adding lv2 support LV2 is a portable plugin standard for audio systems, similar in scope to LADSPA, VST, AU, and others. The Calf audio plugin pack uses LV2 and Ardour3 has also been updated to support LV2 Plugins
2012-07-05 23:29:45 +02:00
calf = callPackage ../applications/audio/calf {
inherit (gnome) libglade;
};
calibre: update from 1.48.0 to 2.0.0
2014-08-23 12:03:03 +02:00
calibre = callPackage ../applications/misc/calibre {
inherit (pythonPackages) pyqt5 sip_4_16;
};
Adding calibre. This involved also: - Adding podofo - Adding some new python packages - Making new pkgs attributes for python packages to build with python 2.6 - Updating some python packages expressions to allow python 2.6, and not only 2.5. svn path=/nixpkgs/trunk/; revision=19303
2010-01-07 23:47:30 +01:00
add camlistore package
2014-06-23 12:26:56 +02:00
camlistore = callPackage ../applications/misc/camlistore { };
* Removed selectVersion. There's no good reason to write `selectVersion ./foo "bar"' instead of `import ./foo/bar.nix'. * Replaced `with args' with formal function arguments in several packages. * Renamed several files to `default.nix'. As a general rule, version numbers should only be included in the filename when there is a reason to keep multiple versions of a package in Nixpkgs. Otherwise, it just makes it harder to update the package. svn path=/nixpkgs/trunk/; revision=18403
2009-11-18 10:39:59 +01:00
carrier = builderDefsPackage (import ../applications/networking/instant-messengers/carrier/2.5.0.nix) {
all-packages.nix changes for all those updates svn path=/nixpkgs/trunk/; revision=12119
2008-06-16 15:15:55 +02:00
inherit fetchurl stdenv pkgconfig perl perlXMLParser libxml2 openssl nss
gtkspell aspell gettext ncurses avahi dbus dbus_glib python
Make nixpkgs ready for gst_all attrset removal svn path=/nixpkgs/trunk/; revision=33092
2012-03-14 23:44:52 +01:00
libtool automake autoconf gstreamer;
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit gtk glib;
all-packages.nix changes for all those updates svn path=/nixpkgs/trunk/; revision=12119
2008-06-16 15:15:55 +02:00
inherit (gnome) startupnotification GConf ;
inherit (xlibs) libXScrnSaver scrnsaverproto libX11 xproto kbproto;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
all-packages.nix changes for all those updates svn path=/nixpkgs/trunk/; revision=12119
2008-06-16 15:15:55 +02:00
funpidgin = carrier;
Adding the Allied Technologies libdc1394 variant and the cc1394 viewer. svn path=/nixpkgs/trunk/; revision=34013
2012-05-08 11:50:58 +02:00
cc1394 = callPackage ../applications/video/cc1394 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cddiscid = callPackage ../applications/audio/cd-discid { };
Add cd-discid, a utility to retrieve a CD's CDDB ID. svn path=/nixpkgs/trunk/; revision=11903
2008-05-26 22:18:45 +02:00
- svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10823
2008-02-22 04:06:12 +01:00
cdparanoia = cdparanoiaIII;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cdparanoiaIII = callPackage ../applications/audio/cdparanoia { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cdrtools = callPackage ../applications/misc/cdrtools { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Adding centerim. svn path=/nixpkgs/trunk/; revision=31503
2012-01-12 19:55:08 +01:00
centerim = callPackage ../applications/networking/instant-messengers/centerim { };
cgit: new package cgit is a web frontend for git repositories - it is a CGI program to use with your favourite webserver. Add the latest version, 0.9.2.
2013-04-01 17:42:51 +02:00
cgit = callPackage ../applications/version-management/git-and-tools/cgit { };
Add cgminer: gpu, fpga and asic crypto currencies mining application
2013-06-16 23:38:12 +02:00
cgminer = callPackage ../applications/misc/cgminer {
amdappsdk = amdappsdk28;
};
chatzilla: Use latest firefox's xulrunner
2014-04-26 02:04:18 +02:00
chatzilla = callPackage ../applications/networking/irc/chatzilla { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
chromium: Remove all NSAPI browser wrappers. Chromium doesn't support NSAPI anymore, so it doesn't make sense to keep the wrappers, especially because some of them trigger bugs in more recent versions of Chromium. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-08-30 02:56:28 +02:00
chromium = callPackage ../applications/networking/browsers/chromium {
all-packages: Add chromiumBeta and chromiumDev. Now Hydra should pick up those versions as well, so users can easily switch between different chromium channels without the need to wait up to several hours in order to build Chromium (depending on hardware of course, nowadays it shouldn't take more than one hour, I guess). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-03 18:00:39 +01:00
channel = "stable";
chromium: Enable pulseaudio by default. If no config.pulseaudio is explicitely set to false, build with pulse support, because even if there is no pulse server available, chromium will fall back to using ALSA. And we definitely want to avoid that users have to build chromium for themselves just for the sake of having pulse support. Thanks to @devhell for actually helping me discovering this (I for myself do always rebuild Chromium, so I won't notice those kind of things). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-07-15 01:10:20 +02:00
pulseSupport = config.pulseaudio or true;
chromium: Allow config.chromium for PPAPI plugins. This should make it easier to enable proprietary pepper API plugins though nixpkgs config, so it can be easily installed using something like: nix-env -i chromium-stable With something like: { chromium.enablePepperFlash = true; } In ~/.nixpkgs/config.nix to enable pepper API based Flash and to avoid the browser wrapper from Firefox entirely. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-05-08 16:41:38 +02:00
enablePepperFlash = config.chromium.enablePepperFlash or false;
enablePepperPDF = config.chromium.enablePepperPDF or false;
chromium: Remove all NSAPI browser wrappers. Chromium doesn't support NSAPI anymore, so it doesn't make sense to keep the wrappers, especially because some of them trigger bugs in more recent versions of Chromium. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-08-30 02:56:28 +02:00
};
chrome 20565 svn path=/nixpkgs/trunk/; revision=18046
2009-10-30 09:45:58 +01:00
chromium: Mark beta and dev versions lowPrio. I'm still wondering why noone has reported this, but I found out about this while trying to introduce someone to NixOS, eventually wondering why it is going to install version 29 when using "nix-env -i chromium". So, in hope that everyone out there using the package is using the attribute, let's make _stable_ the default here. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-06-21 09:16:26 +02:00
chromiumBeta = lowPrio (chromium.override { channel = "beta"; });
all-packages: Add chromiumBeta and chromiumDev. Now Hydra should pick up those versions as well, so users can easily switch between different chromium channels without the need to wait up to several hours in order to build Chromium (depending on hardware of course, nowadays it shouldn't take more than one hour, I guess). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-03 18:00:39 +01:00
chromium: Mark beta and dev versions lowPrio. I'm still wondering why noone has reported this, but I found out about this while trying to introduce someone to NixOS, eventually wondering why it is going to install version 29 when using "nix-env -i chromium". So, in hope that everyone out there using the package is using the attribute, let's make _stable_ the default here. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-06-21 09:16:26 +02:00
chromiumDev = lowPrio (chromium.override { channel = "dev"; });
added chromeWrapper, like firefoxWrapper, to allow plugins to work, added previously undefined dependencies on flash plugin svn path=/nixpkgs/trunk/; revision=18050
2009-10-30 13:28:44 +01:00
cinelerra: drop esound support I'm going to remove esound from nixpkgs in a few minutes. svn path=/nixpkgs/trunk/; revision=32981
2012-03-11 15:07:19 +01:00
cinelerra = callPackage ../applications/video/cinelerra { };
added cinelerra (video editing application) svn path=/nixpkgs/trunk/; revision=13068
2008-10-14 16:01:50 +02:00
Add package for ClipIt, a lightweight GTK clipboard manager
2014-08-21 16:22:08 +02:00
clipit = callPackage ../applications/misc/clipit { };
cmus: packaged. Patch by Paul van der Walt <nix@denknerd.nl>. svn path=/nixpkgs/trunk/; revision=24739
2010-11-17 16:20:57 +01:00
cmus = callPackage ../applications/audio/cmus { };
all-packages.nix: strip trailing whitespace
2012-11-26 16:17:49 +01:00
compiz = callPackage ../applications/window-managers/compiz {
compiz: fix build and update
2013-02-23 15:10:01 +01:00
inherit (gnome) GConf ORBit2 metacity;
boost = boost149; # https://bugs.launchpad.net/compiz/+bug/1131864
Update Compiz
2012-11-25 20:58:04 +01:00
};
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
Adding coriander. I don't know how to make its gconf thing work, so it shows a warning at gui start. svn path=/nixpkgs/trunk/; revision=33976
2012-05-03 11:38:36 +02:00
coriander = callPackage ../applications/video/coriander {
inherit (gnome) libgnomeui GConf;
};
adding csound
2012-10-18 03:13:21 +02:00
csound = callPackage ../applications/audio/csound { };
cinepaint: updating, and making it build I wrote a little patch for the cmake files, or it didn't install. I also used the NIX_LDFLAGS trick; they are not doing proper linking somehow.
2012-07-02 22:27:18 +02:00
cinepaint = callPackage ../applications/graphics/cinepaint {
fltk = fltk13;
libpng = libpng12;
};
Adding cinepaint 0.22.1 and as a dependency, also fltk 1.1.9 svn path=/nixpkgs/trunk/; revision=14841
2009-04-02 17:20:19 +02:00
codeblocks: new package 13.12 (close #2533) @vcunat: minor refactoring.
2014-04-20 04:21:04 +02:00
codeblocks = callPackage ../applications/editors/codeblocks { };
codeblocksFull = callPackage ../applications/editors/codeblocks { contribPlugins = true; };
* Removed selectVersion. There's no good reason to write `selectVersion ./foo "bar"' instead of `import ./foo/bar.nix'. * Replaced `with args' with formal function arguments in several packages. * Renamed several files to `default.nix'. As a general rule, version numbers should only be included in the filename when there is a reason to keep multiple versions of a package in Nixpkgs. Otherwise, it just makes it harder to update the package. svn path=/nixpkgs/trunk/; revision=18403
2009-11-18 10:39:59 +01:00
codeville = builderDefsPackage (import ../applications/version-management/codeville/0.8.0.nix) {
Adding possibility to have rich Python installation for development but use only the base one for, say, OpenOffice (and be able to use buildfarm). Codeville and Bazaar use the rich variant - they do have some use for it.. svn path=/nixpkgs/trunk/; revision=13075
2008-10-15 22:01:39 +02:00
inherit makeWrapper;
python = pythonFull;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
Added codeville - a distributed revision control system with special efforts spent on merging. Heh, efforts into RCS availability seem to have side effects on Python side, too.. svn path=/nixpkgs/trunk/; revision=11891
2008-05-26 09:47:07 +02:00
comical: build with wxGTK28 svn path=/nixpkgs/trunk/; revision=29339
2011-09-19 07:16:32 +02:00
comical = callPackage ../applications/graphics/comical { };
Adding comical-0.8 svn path=/nixpkgs/trunk/; revision=14016
2009-02-09 21:44:26 +01:00
* Fix Chatzilla (it doesn't work with recent Xulrunners). * Get rid of xulrunnerWrapper. svn path=/nixpkgs/trunk/; revision=29706
2011-10-07 11:26:03 +02:00
conkeror = callPackage ../applications/networking/browsers/conkeror { };
firefoxWrapper: Fix the name
2014-03-10 15:18:48 +01:00
conkeror: provide a wrapper, so plugins work
2013-08-18 16:49:52 +02:00
conkerorWrapper = wrapFirefox {
browser = conkeror;
browserName = "conkeror";
desktopName = "Conkeror";
};
conkeror: New nixpkg. svn path=/nixpkgs/trunk/; revision=21296
2010-04-24 19:34:58 +02:00
Added Cuneiform OCR. Works somehow.. svn path=/nixpkgs/trunk/; revision=14015
2009-02-09 21:37:11 +01:00
cuneiform = builderDefsPackage (import ../tools/graphics/cuneiform) {
inherit cmake patchelf;
samba, imagemagick: Add missing meta info
2013-01-06 22:30:23 +01:00
imagemagick = imagemagick;
Added Cuneiform OCR. Works somehow.. svn path=/nixpkgs/trunk/; revision=14015
2009-02-09 21:37:11 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cvs = callPackage ../applications/version-management/cvs { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cvsps = callPackage ../applications/version-management/cvsps { };
Add CVSps, needed for instance by `git-cvsimport'. svn path=/nixpkgs/trunk/; revision=11094
2008-03-13 11:02:57 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cvs2svn = callPackage ../applications/version-management/cvs2svn { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
d4x = callPackage ../applications/misc/d4x { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
darcs updated to 2.8.5 tested to work with ghc 7.8.3
2014-08-26 00:51:10 +02:00
darcs = with haskellPackages_ghc783; callPackage ../applications/version-management/darcs {
Move 'cryptol' and 'darcs' from the generic Haskell package set into all-packages.nix. These packages need very a version of GHC to compile.
2014-08-20 11:57:38 +02:00
cabal = cabal.override {
Re-write the Haskell Platform out of haskell-defaults.nix. 1) Packages formerly called haskell-haskell-platform-ghcXYZ-VVVV.X.Y.Z are now called haskell-platform-VVVV.X.Y.Z. The latest version can be installed by running "nix-env -i haskell-platform". 2) The attributes haskellPackages_ghcXYZ.haskellPlatform no longer exist. Instead, we have attributes like haskellPlatformPackages."2012_4_0_0". (The last numeric bit must be quoted when used in a Nix file, but not on the command line to nix-env, nix-build, etc.) The latest Platform has a top-level alias called simply haskellPlatform. 3) The haskellPackages_ghcXYZ package sets offer the latest version of every library that GHC x.y.z can compile. For example, if 2.7 is the latest version of QuickCheck and if GHC 7.0.4 can compile that version, then haskellPackages_ghc704.QuickCheck refers to version 2.7. 4) All intermediate GHC releases were dropped from all-packages.nix to simplify our configuration. What remains is a haskellPackages_ghcXYZ set for the latest version of every major release branch, i.e. GHC 6.10.4, 6.12.3, 7.0.4, 7.2.2, 7.4.2, 7.6.3, 7.8.2, and 7.9.x (HEAD snapshot). 5) The ghcXYZPrefs functions in haskell-defaults.nix now inherit overrides from newer to older compilers, i.e. an override configured for GHC 7.0.4 will automatically apply to GHC 6.12.3 and 6.10.4, too. This change has reduced the redundancy in those configuration functions. The downside is that overriding an attribute for only one particular GHC version has become more difficult. In practice, this case doesn't occur much, though. 6) The 'cabal' builder has a brand-new argument called 'extension'. That function is "self : super : {}" by default and users can override it to mess with the attribute set passed to cabal.mkDerivation. An example use would be the definition of darcs in all-packages.nix: | darcs = haskellPackages.darcs.override { | cabal = haskellPackages.cabal.override { | extension = self : super : { | isLibrary = false; | configureFlags = "-f-library " + super.configureFlags or ""; | }; | }; | }; In this case, extension disables building the library part of the package to give us an executable-only version that has no dependencies on GHC or any other Haskell packages. The 'self' argument refers to the final version of the attribute set and 'super' refers to the original attribute set. Note that ... - Haskell Platform packages always provide the Haddock binary that came with the compiler. - Haskell Platform 2009.2.0.2 is broken because of build failures in cgi and cabal-install. - Haskell Platform 2010.1.0.0 is broken becasue of build failures in cgi.
2014-05-07 19:36:45 +02:00
extension = self : super : {
isLibrary = false;
configureFlags = "-f-library " + super.configureFlags or "";
};
};
all-packages.nix: provide a variant of Darcs that includes the executable, but not the library The reduced 'darcs' derivation is supposed to be run-time independent of the Haskell compiler. Unfortunately, this isn't quite true yet because the HTTP package bakes its own store path into the library. This causes Darcs -- which links the HTTP library statically -- to depend on 'HTTP', which in turn depends on lot of other Haskell stuff. Patching HTTP to get rid of that reference looks feasible, though.
2013-02-11 16:50:39 +01:00
};
added darcs-2.0.0pre svn path=/nixpkgs/trunk/; revision=10564
2008-02-09 14:52:41 +01:00
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
darktable = callPackage ../applications/graphics/darktable {
Make nixpkgs ready to gtkLibs attrset removal svn path=/nixpkgs/trunk/; revision=33091
2012-03-14 23:44:41 +01:00
inherit (gnome) GConf libglade;
Adding darktable photo editor. Patch by Cillian de Róiste ( goibhniu1 ) svn path=/nixpkgs/trunk/; revision=25462
2011-01-08 22:55:33 +01:00
};
Fix indentation
2014-05-08 13:49:17 +02:00
dd-agent = callPackage ../tools/networking/dd-agent { inherit (pythonPackages) tornado; };
First attempt at packaging dd-agent
2013-01-08 18:32:47 +01:00
Use fetchurl_gnome in dia +small style changes (though almost all string changed) svn path=/nixpkgs/trunk/; revision=29389
2011-09-20 08:31:37 +02:00
dia = callPackage ../applications/graphics/dia {
inherit (pkgs.gnome) libart_lgpl libgnomeui;
};
Digikam-1.4.0, move to all-packages.nix svn path=/nixpkgs/trunk/; revision=24089
2010-10-05 19:44:05 +02:00
diffuse: new package, close #731. Diffuse is a graphical diff and merge tool. http://diffuse.sourceforge.net/
2013-05-22 10:44:32 +02:00
diffuse = callPackage ../applications/version-management/diffuse { };
Add the Distrho collection of audio plugins
2012-10-07 13:51:39 +02:00
distrho = callPackage ../applications/audio/distrho {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
djvulibre = callPackage ../applications/misc/djvulibre { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
djvu2pdf: new expression
2014-06-25 20:14:53 +02:00
djvu2pdf = callPackage ../tools/typesetting/djvu2pdf { };
djview-4.8, fix build with qt-4.8 svn path=/nixpkgs/trunk/; revision=32171
2012-02-10 11:13:44 +01:00
djview = callPackage ../applications/graphics/djview { };
djview4 = pkgs.djview;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
dmenu: Add option config.dmenu.enableXft for enabling xft font support (turned off by default).
2012-11-07 16:03:37 +01:00
dmenu = callPackage ../applications/misc/dmenu {
enableXft = config.dmenu.enableXft or false;
};
Added: * dmenu * gftp * micropolis * byacc as a build-time dependency for micropolis contributed by baldo <baldo@quimby.lan> svn path=/nixpkgs/trunk/; revision=12526
2008-08-06 22:39:01 +02:00
Added DataMatrix (2D bar code) processing utilities svn path=/nixpkgs/trunk/; revision=13281
2008-11-13 14:31:10 +01:00
dmtx = builderDefsPackage (import ../tools/graphics/dmtx) {
subversion: updated to version 1.6.0 svn path=/nixpkgs/trunk/; revision=14682
2009-03-24 11:31:39 +01:00
inherit libpng libtiff libjpeg imagemagick librsvg
pkgs/applications/editors/emacs-modes/magit: updated to version magit-0.7-94-gbf42bf8 Magit has seen plenty of development since version 0.7, but for some reason there haven't been any new releases. This version bump updates the expression to build a current version of Magit directly from the Git repository. This change adds buildInputs 'autoconf' and 'automake'. These tools are required only because we aren't building from a proper release tarball. Once version 0.8 comes out, these dependencies can be dropped again. svn path=/nixpkgs/trunk/; revision=20650
2010-03-16 13:13:40 +01:00
pkgconfig bzip2 zlib libtool freetype fontconfig
Fix DMTX build svn path=/nixpkgs/trunk/; revision=27391
2011-06-08 10:11:24 +02:00
ghostscript jasper xz;
DataMatrix update svn path=/nixpkgs/trunk/; revision=14607
2009-03-19 14:59:00 +01:00
inherit (xlibs) libX11;
Added DataMatrix (2D bar code) processing utilities svn path=/nixpkgs/trunk/; revision=13281
2008-11-13 14:31:10 +01:00
};
Add docker
2014-01-24 14:39:43 +01:00
docker = callPackage ../applications/virtualization/docker { };
Adding doodle.
2013-04-22 18:14:29 +02:00
doodle = callPackage ../applications/search/doodle { };
Add dunst, a lightweight notification daemon. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-03-20 21:19:43 +01:00
dunst = callPackage ../applications/misc/dunst { };
added dvb-apps svn path=/nixpkgs/trunk/; revision=30787
2011-12-07 00:00:46 +01:00
dvb_apps = callPackage ../applications/video/dvb-apps { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dvdauthor = callPackage ../applications/video/dvdauthor { };
added dvdauthor svn path=/nixpkgs/trunk/; revision=13766
2009-01-14 17:23:06 +01:00
Fixed dwb startup issue
2014-06-30 14:30:45 +02:00
dwb = callPackage ../applications/networking/browsers/dwb { dconf = gnome3.dconf; };
Added dwb, a lightweight webbrowser written in C based on webkit and gtk.
2013-10-02 15:13:40 +02:00
dwb: add wrapper and use GTK2 for plugin support
2014-06-29 20:17:09 +02:00
dwbWrapper = wrapFirefox
{ browser = dwb; browserName = "dwb"; desktopName = "dwb";
};
Added dwb, a lightweight webbrowser written in C based on webkit and gtk.
2013-10-02 15:13:40 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
dwm = callPackage ../applications/window-managers/dwm {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
patches = config.dwm.patches or [];
maudeUnstable: updated full-maude to latest alpha release svn path=/nixpkgs/trunk/; revision=13017
2008-10-09 12:10:49 +02:00
};
add window-manager dwm contributed by viric svn path=/nixpkgs/trunk/; revision=12687
2008-08-21 22:44:08 +02:00
dzen2: new package "Dzen is a general purpose messaging, notification and menuing program for X11. It was designed to be fast, tiny and scriptable in any language." -- https://github.com/robm/dzen
2013-12-16 04:29:42 +01:00
dzen2 = callPackage ../applications/window-managers/dzen2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
eaglemode = callPackage ../applications/misc/eaglemode { };
eclipse-new expression (update of eclipse_classic_src) It supports now insntalling some plugins (however the eclipse path will be copied once) You can still just copy the whole store path to you home directory to install additional plugins using update sites svn path=/nixpkgs/trunk/; revision=13121
2008-10-26 18:45:14 +01:00
eclipse: use latest cairo/gtk Eclipse seems to work fine without this now (after x-updates merge).
2013-06-26 14:32:24 +02:00
eclipses = recurseIntoAttrs (callPackage ../applications/editors/eclipse { });
Enabled my eclipse package again, since I want to have eclipse installed when typing nix-env -i. BTW. the eclipse plugins can be installed this way either svn path=/nixpkgs/trunk/; revision=18074
2009-11-03 12:00:18 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ed = callPackage ../applications/editors/ed { };
Move GNU ed, add meta-information. svn path=/nixpkgs/trunk/; revision=11715
2008-04-25 18:13:36 +02:00
add ekho 5.8.2, a Chinese TTS software
2014-03-14 05:30:10 +01:00
ekho = callPackage ../applications/audio/ekho { };
electrum: initial expression Electrum is a Bitcoin thin-wallet. https://electrum.org
2014-03-23 16:22:57 +01:00
electrum = callPackage ../applications/misc/electrum { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
elinks = callPackage ../applications/networking/browsers/elinks { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
elvis = callPackage ../applications/editors/elvis { };
Adding elvis, although I can't see the characters in an xterm with black background svn path=/nixpkgs/trunk/; revision=15098
2009-04-16 21:28:42 +02:00
Updated Emacs default version from 23.3 to 24.1. Yay! svn path=/nixpkgs/trunk/; revision=34461
2012-06-11 18:41:31 +02:00
emacs = emacs24;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Updated Emacs default version from 23.3 to 24.1. Yay! svn path=/nixpkgs/trunk/; revision=34461
2012-06-11 18:41:31 +02:00
emacs24 = callPackage ../applications/editors/emacs-24 {
all-packages.nix: disable dependencies in Emacs 24 that we didn't have in Emacs 23 either It's unclear what adding these dependencies accomplishes. If you find that a feature you need doesn't work anymore, please feel free to re-enable the appropriate dependencies. svn path=/nixpkgs/trunk/; revision=34510
2012-06-14 21:44:34 +02:00
# use override to enable additional features
emacs: Allow non-GTK X11 builds (--with-x-toolkit=lucid).
2013-12-31 13:27:32 +01:00
libXaw = xlibs.libXaw;
emacs-24.0.92 svn path=/nixpkgs/trunk/; revision=31763
2012-01-21 19:28:57 +01:00
Xaw3d = null;
all-packages.nix: disable dependencies in Emacs 24 that we didn't have in Emacs 23 either It's unclear what adding these dependencies accomplishes. If you find that a feature you need doesn't work anymore, please feel free to re-enable the appropriate dependencies. svn path=/nixpkgs/trunk/; revision=34510
2012-06-14 21:44:34 +02:00
gconf = null;
librsvg = null;
alsaLib = null;
imagemagick = null;
Updated Emacs default version from 23.3 to 24.1. Yay! svn path=/nixpkgs/trunk/; revision=34461
2012-06-11 18:41:31 +02:00
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Don't prefer 'emacs24-nox' over the normal 'emacs24' attribute.
2013-08-24 12:19:56 +02:00
emacs24-nox = lowPrio (appendToName "nox" (emacs24.override {
Add emacs24-nox: emacs built without X (or GTK) libraries. This commit also fixes an issue where pkgconfig was only added as a dependency when gtk support was enabled. This made ./configure unable to find other libraries (libtiff, libxml2, gnutls, and others).
2013-08-14 15:02:07 +02:00
withX = false;
}));
emacs24Macport: Mark as lowPrio
2014-07-22 13:49:48 +02:00
emacs24Macport = lowPrio (callPackage ../applications/editors/emacs-24/macport.nix {
Many minor fixes to get things building after recent compiler changes
2014-08-11 06:18:57 +02:00
stdenv = pkgs.clangStdenv;
emacs24Macport: Mark as lowPrio
2014-07-22 13:49:48 +02:00
});
emacs24Macport: new expression This is "Mac port" addition to GNU Emacs 24. This provides a native GUI support for Mac OS X 10.4 - 10.9. Note that Emacs 23 and later already contain the official GUI support via the NS (Cocoa) port for Mac OS X 10.4 and later. So if it is good enough for you, then you don't need to try this.
2014-05-31 22:38:18 +02:00
svn path=/nixpkgs/trunk/; revision=22880
2010-08-02 18:01:55 +02:00
emacsPackages = emacs: self: let callPackage = newScope self; in rec {
emacsPackages should inherit emacs to add the correct version to the inner scope svn path=/nixpkgs/trunk/; revision=23159
2010-08-13 09:55:57 +02:00
inherit emacs;
emacs: add "auto-complete" mode
2012-08-10 08:22:43 +02:00
autoComplete = callPackage ../applications/editors/emacs-modes/auto-complete { };
all-packages.nix: remove redundant texinfo5 overrides Texinfo 5.x is the default version now.
2014-01-21 20:29:34 +01:00
bbdb = callPackage ../applications/editors/emacs-modes/bbdb { };
Rename `emacsUnicode' to `emacs23'. svn path=/nixpkgs/trunk/; revision=16073
2009-06-28 01:09:21 +02:00
bbdb3: New package.
2014-07-27 10:55:43 +02:00
bbdb3 = callPackage ../applications/editors/emacs-modes/bbdb/3.nix {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cedet = callPackage ../applications/editors/emacs-modes/cedet { };
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
emacs mode calfw-1.3 svn path=/nixpkgs/trunk/; revision=32118
2012-02-07 18:39:51 +01:00
calfw = callPackage ../applications/editors/emacs-modes/calfw { };
emacs: add "coffee-mode"
2012-08-10 08:22:27 +02:00
coffee = callPackage ../applications/editors/emacs-modes/coffee { };
emacs: add "color-theme"
2012-08-17 08:55:47 +02:00
colorTheme = callPackage ../applications/editors/emacs-modes/color-theme { };
add emacs color-theme solarized
2014-07-28 11:07:38 +02:00
colorThemeSolarized = callPackage ../applications/editors/emacs-modes/color-theme-solarized { };
emacsPackages: add cryptol-mode Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-15 01:23:40 +02:00
cryptol = callPackage ../applications/editors/emacs-modes/cryptol { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cua = callPackage ../applications/editors/emacs-modes/cua { };
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
Added darcsum, "a pcl-cvs like interface for managing darcs patches".
2014-01-18 21:23:59 +01:00
darcsum = callPackage ../applications/editors/emacs-modes/darcsum { };
Added tuareg emacs mode and fixed some other emacs mode. ecb emacs mode is commented out because it's dependency appears not to compile.
2013-06-08 12:28:49 +02:00
# ecb = callPackage ../applications/editors/emacs-modes/ecb { };
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jabber = callPackage ../applications/editors/emacs-modes/jabber { };
applications/editors/emacs-modes/jabber: New nixbuild. svn path=/nixpkgs/trunk/; revision=21806
2010-05-16 22:32:21 +02:00
emacs: add "auto-complete-clang-async" mode (aka emacs-clang-complete-async)
2013-02-18 14:05:08 +01:00
emacsClangCompleteAsync = callPackage ../applications/editors/emacs-modes/emacs-clang-complete-async { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
emacsSessionManagement = callPackage ../applications/editors/emacs-modes/session-management-for-emacs { };
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
all-packages.nix: remove redundant texinfo5 overrides Texinfo 5.x is the default version now.
2014-01-21 20:29:34 +01:00
emacsw3m = callPackage ../applications/editors/emacs-modes/emacs-w3m { };
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
all-packages.nix: remove redundant texinfo5 overrides Texinfo 5.x is the default version now.
2014-01-21 20:29:34 +01:00
emms = callPackage ../applications/editors/emacs-modes/emms { };
Add Emacs-w3m, an Emacs interface to the W3M web browser. svn path=/nixpkgs/trunk/; revision=16287
2009-07-09 17:56:40 +02:00
ess: add Emacs Speaks Statistics mode
2013-06-15 17:12:40 +02:00
ess = callPackage ../applications/editors/emacs-modes/ess { };
emacs: add "flymake-cursor"
2012-08-10 14:47:16 +02:00
flymakeCursor = callPackage ../applications/editors/emacs-modes/flymake-cursor { };
emacs: add gh (github) package
2012-08-05 02:15:34 +02:00
gh = callPackage ../applications/editors/emacs-modes/gh { };
graphviz-dot-mode: add version 0.3.3
2012-11-16 18:59:18 +01:00
graphvizDot = callPackage ../applications/editors/emacs-modes/graphviz-dot { };
emacs: add gist package
2012-08-05 02:15:48 +02:00
gist = callPackage ../applications/editors/emacs-modes/gist { };
add emacs/idris-mode
2014-01-06 12:19:13 +01:00
idris = callPackage ../applications/editors/emacs-modes/idris { };
emacs: add "jade-mode"
2012-08-13 16:17:31 +02:00
jade = callPackage ../applications/editors/emacs-modes/jade { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
jdee = callPackage ../applications/editors/emacs-modes/jdee {
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
# Requires Emacs 23, for `avl-tree'.
};
emacs js2-mode svn path=/nixpkgs/trunk/; revision=32122
2012-02-07 18:40:02 +01:00
js2 = callPackage ../applications/editors/emacs-modes/js2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
stratego = callPackage ../applications/editors/emacs-modes/stratego { };
* stratego-mode for emacs svn path=/nixpkgs/trunk/; revision=16910
2009-09-01 16:27:24 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
haskellMode = callPackage ../applications/editors/emacs-modes/haskell { };
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
ocaml-mode for emacs. There seem to exist multiple (very old) versions. I'm taking the one shipped with the ocaml compiler, which is hopefully the "most appropriate". svn path=/nixpkgs/trunk/; revision=32688
2012-02-29 13:53:13 +01:00
ocamlMode = callPackage ../applications/editors/emacs-modes/ocaml { };
Add structured-haskell-mode
2014-03-01 10:00:36 +01:00
structuredHaskellMode = callPackage ../applications/editors/emacs-modes/structured-haskell-mode {
inherit (haskellPackages) cabal haskellSrcExts;
};
Added tuareg emacs mode and fixed some other emacs mode. ecb emacs mode is commented out because it's dependency appears not to compile.
2013-06-08 12:28:49 +02:00
tuaregMode = callPackage ../applications/editors/emacs-modes/tuareg { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hol_light_mode = callPackage ../applications/editors/emacs-modes/hol_light { };
Add HOL Light and its dependencies. Add pkgs/applications/science/logic/hol_light and pkgs/applications/science/emacs-modes/hol_light Some functionalities of HOL Light requires the compiled sources of OCaml. For now we provide a new package ocaml_with_sources. After this shuold be merged with the current version of OCaml already present in nixpkgs. svn path=/nixpkgs/trunk/; revision=20008
2010-02-15 12:00:02 +01:00
Add Nix expression for Emacs mode htmlize. svn path=/nixpkgs/trunk/; revision=23382
2010-08-24 10:25:51 +02:00
htmlize = callPackage ../applications/editors/emacs-modes/htmlize { };
emacs: add logito package
2012-08-05 02:14:53 +02:00
logito = callPackage ../applications/editors/emacs-modes/logito { };
emacs: add lorem-ipsum package
2012-08-05 02:16:01 +02:00
loremIpsum = callPackage ../applications/editors/emacs-modes/lorem-ipsum { };
all-packages.nix: remove redundant texinfo5 overrides Texinfo 5.x is the default version now.
2014-01-21 20:29:34 +01:00
magit = callPackage ../applications/editors/emacs-modes/magit { };
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
maudeMode = callPackage ../applications/editors/emacs-modes/maude { };
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
add emacs-metaweblog
2014-06-05 15:42:39 +02:00
metaweblog = callPackage ../applications/editors/emacs-modes/metaweblog { };
Fix some name collisions
2013-07-30 12:31:31 +02:00
notmuch = lowPrio (callPackage ../applications/networking/mailreaders/notmuch { });
notmuch as emacsPackage and top-level without emacs support svn path=/nixpkgs/trunk/; revision=31768
2012-01-21 19:29:14 +01:00
emacs offlineimap mode added
2013-11-12 11:00:58 +01:00
offlineimap = callPackage ../applications/editors/emacs-modes/offlineimap {};
Give Org-Mode a high priority. svn path=/nixpkgs/trunk/; revision=22694
2010-07-22 10:59:46 +02:00
# This is usually a newer version of Org-Mode than that found in GNU Emacs, so
# we want it to have higher precedence.
Fix tarball Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-21 20:39:33 +01:00
org = hiPrio (callPackage ../applications/editors/emacs-modes/org { });
Add upstream Org-Mode. svn path=/nixpkgs/trunk/; revision=22693
2010-07-22 10:59:12 +02:00
emacs: add package "org2blog"
2012-09-09 19:32:27 +02:00
org2blog = callPackage ../applications/editors/emacs-modes/org2blog { };
emacs: add pcache package
2012-08-05 02:15:11 +02:00
pcache = callPackage ../applications/editors/emacs-modes/pcache { };
Emacs PHP mode: packaged. Patch by Karn Kallio. svn path=/nixpkgs/trunk/; revision=25216
2010-12-21 05:40:38 +01:00
phpMode = callPackage ../applications/editors/emacs-modes/php { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
prologMode = callPackage ../applications/editors/emacs-modes/prolog { };
Add expression for ProofGeneral svn path=/nixpkgs/trunk/; revision=18904
2009-12-11 17:18:27 +01:00
proofgeneral_4_3_pre: Add expression needed for current prooftree
2014-06-21 07:31:55 +02:00
proofgeneral_4_2 = callPackage ../applications/editors/emacs-modes/proofgeneral/4.2.nix {
proofgeneral: fix build with earlier version of texinfo.
2014-02-03 15:28:48 +01:00
texinfo = texinfo4 ;
ProofGeneral documentation does not build without cm-super fonts. svn path=/nixpkgs/trunk/; revision=31797
2012-01-23 20:03:41 +01:00
texLive = pkgs.texLiveAggregationFun {
nxml-mode: Remove This package is now part of Emacs itself.
2012-11-23 11:10:30 +01:00
paths = [ pkgs.texLive pkgs.texLiveCMSuper ];
};
ProofGeneral documentation does not build without cm-super fonts. svn path=/nixpkgs/trunk/; revision=31797
2012-01-23 20:03:41 +01:00
};
proofgeneral_4_3_pre: Add expression needed for current prooftree
2014-06-21 07:31:55 +02:00
proofgeneral_4_3_pre = callPackage ../applications/editors/emacs-modes/proofgeneral/4.3pre.nix {
texinfo = texinfo4 ;
texLive = pkgs.texLiveAggregationFun {
paths = [ pkgs.texLive pkgs.texLiveCMSuper ];
};
};
proofgeneral = self.proofgeneral_4_2;
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
quack = callPackage ../applications/editors/emacs-modes/quack { };
Add Emacs Scala-Mode. svn path=/nixpkgs/trunk/; revision=17904
2009-10-20 17:12:29 +02:00
emacs: add "rect-mark"
2012-08-21 10:33:06 +02:00
rectMark = callPackage ../applications/editors/emacs-modes/rect-mark { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
remember = callPackage ../applications/editors/emacs-modes/remember { };
pkgs/applications/editors/emacs-modes/rudel: added rudel 0.2-4 A collaborative editing environment for GNU Emacs. svn path=/nixpkgs/trunk/; revision=22733
2010-07-26 15:41:03 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rudel = callPackage ../applications/editors/emacs-modes/rudel { };
Add EMMS, the Emacs Multimedia System. svn path=/nixpkgs/trunk/; revision=12675
2008-08-21 10:58:51 +02:00
emacs-sbt-mode: add initial version
2014-06-05 13:01:33 +02:00
sbtMode = callPackage ../applications/editors/emacs-modes/sbt-mode { };
emacs-scala-mode: package version 2
2014-06-05 12:58:57 +02:00
scalaMode1 = callPackage ../applications/editors/emacs-modes/scala-mode/v1.nix { };
scalaMode2 = callPackage ../applications/editors/emacs-modes/scala-mode/v2.nix { };
emacs: add "sunrise commander"
2012-08-21 10:33:20 +02:00
sunriseCommander = callPackage ../applications/editors/emacs-modes/sunrise-commander { };
emacs: add package "xml-rpc"
2012-09-09 19:32:14 +02:00
Add emacs minor mode writegood
2014-02-04 15:47:03 +01:00
writeGood = callPackage ../applications/editors/emacs-modes/writegood { };
emacs: add package "xml-rpc"
2012-09-09 19:32:14 +02:00
xmlRpc = callPackage ../applications/editors/emacs-modes/xml-rpc { };
svn path=/nixpkgs/trunk/; revision=22880
2010-08-02 18:01:55 +02:00
};
Add EMMS, the Emacs Multimedia System. svn path=/nixpkgs/trunk/; revision=12675
2008-08-21 10:58:51 +02:00
emacs-24.0.92 svn path=/nixpkgs/trunk/; revision=31763
2012-01-21 19:28:57 +01:00
emacs24Packages = recurseIntoAttrs (emacsPackages emacs24 pkgs.emacs24Packages);
Group Emacs packages in an `emacsPackages' function. This avoids problem such as bytecode incompatibilies (e.g., between GNU Emacs 22 and 23), API changes. It would also allow packages to be built with different emacsen (S(X)Emacs, etc.). svn path=/nixpkgs/trunk/; revision=16324
2009-07-10 18:17:06 +02:00
empathy: new package Messaging program which supports text, voice, video chat, and file transfers over many different protocols https://wiki.gnome.org/Apps/Empathy
2014-02-20 22:38:26 +01:00
inherit (gnome3) empathy;
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
epdfview = callPackage ../applications/misc/epdfview { };
applications/misc/epdfview: New package. svn path=/nixpkgs/trunk/; revision=19498
2010-01-17 02:39:29 +01:00
epiphany: new package WebKit based web browser for GNOME https://wiki.gnome.org/Apps/Epiphany
2014-02-15 23:27:29 +01:00
inherit (gnome3) epiphany;
Adding espeak (and one of the libraries it needs, portaudio) svn path=/nixpkgs/trunk/; revision=23351
2010-08-22 14:08:55 +02:00
espeak = callPackage ../applications/audio/espeak { };
Adding espeakedit, phoneme editor for espeak. I've no idea how to use it still.
2012-08-27 19:42:05 +02:00
espeakedit = callPackage ../applications/audio/espeak/edit.nix { };
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
esniper = callPackage ../applications/networking/esniper { };
Adding etherape, although it wants those gconf things I think. svn path=/nixpkgs/trunk/; revision=29437
2011-09-22 11:19:33 +02:00
etherape = callPackage ../applications/networking/sniffers/etherape {
Make nixpkgs ready to gtkLibs attrset removal svn path=/nixpkgs/trunk/; revision=33091
2012-03-14 23:44:41 +01:00
inherit (gnome) gnomedocutils libgnome libglade libgnomeui scrollkeeper;
Adding etherape, although it wants those gconf things I think. svn path=/nixpkgs/trunk/; revision=29437
2011-09-22 11:19:33 +02:00
};
Add evilvte package.
2014-08-27 16:38:15 +02:00
evilvte = callPackage ../applications/misc/evilvte {
configH = config.evilvte.config or "";
};
Adding evopedia. Contributed by Joachim Schiele. svn path=/nixpkgs/trunk/; revision=25066
2010-12-11 23:04:13 +01:00
evopedia = callPackage ../applications/misc/evopedia { };
- added myself as maintainer - added a new package: keepassx (which was reviewed on the nix-dev ml) svn path=/nixpkgs/trunk/; revision=27401
2011-06-09 09:48:54 +02:00
keepassx = callPackage ../applications/misc/keepassx { };
Add keepassx 2.0alpha5, contributed by Thomas Tuegel.
2014-01-27 21:55:04 +01:00
keepassx2 = callPackage ../applications/misc/keepassx/2.0.nix { };
- added myself as maintainer - added a new package: keepassx (which was reviewed on the nix-dev ml) svn path=/nixpkgs/trunk/; revision=27401
2011-06-09 09:48:54 +02:00
update evince, seems to work now
2013-01-29 09:20:14 +01:00
inherit (gnome3) evince;
evolution-data-server: upgrade and move to gnome3 namespace
2014-01-20 16:40:38 +01:00
evolution_data_server = gnome3.evolution_data_server;
Added keepass password manager. Updated mono DLLMap to allow mono to run WinForms applications (keepass).
2013-06-09 23:17:09 +02:00
keepass = callPackage ../applications/misc/keepass { };
Adding Ekiga svn path=/nixpkgs/trunk/; revision=23653
2010-09-06 01:37:54 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
exrdisplay = callPackage ../applications/graphics/exrdisplay {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
fltk = fltk20;
};
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
fbpanel = callPackage ../applications/window-managers/fbpanel { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Add fbreader, an e-book reader for Linux
2013-09-29 02:42:50 +02:00
fbreader = callPackage ../applications/misc/fbreader { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
fetchmail = import ../applications/misc/fetchmail {
svn path=/nixpkgs/trunk/; revision=10828
2008-02-22 11:12:01 +01:00
inherit stdenv fetchurl openssl;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
Add fldigi package Signed-off-by: Ricky Elrod <ricky@elrod.me>
2014-05-11 23:11:10 +02:00
fldigi = callPackage ../applications/audio/fldigi { };
Adding Qsynth (GUI) and fluidsynth (CLI), Soundfont2 based synthesizer svn path=/nixpkgs/trunk/; revision=33504
2012-03-31 22:22:19 +02:00
fluidsynth = callPackage ../applications/audio/fluidsynth { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fossil = callPackage ../applications/version-management/fossil { };
Add package for Fossil svn path=/nixpkgs/trunk/; revision=21746
2010-05-12 15:17:19 +02:00
Adding FriBID browser plugin FriBID is an open source software for the Swedish e-id system called BankID. FriBID also supports processor architectures and Linux/BSD distributions that the official software doesn't support. https://fribid.se/index.en.html FriBID plugin is a firefoxWrapper plugin. Enabled by setting: nixpkgs.config.enableFriBIDPlugin = true
2013-09-04 21:29:37 +02:00
fribid = callPackage ../applications/networking/browsers/mozilla-plugins/fribid { };
add fvwm-2.6.5
2013-03-01 06:48:33 +01:00
fvwm = callPackage ../applications/window-managers/fvwm { };
Add geany-1.22 Geany is a small and lightweight Integrated Development Environment. It was developed to provide a small and fast IDE, which has only a few dependencies from other packages. Another goal was to be as independent as possible from a special Desktop Environment like KDE or GNOME. Geany only requires the GTK2 runtime libraries. Some basic features of Geany: - Syntax highlighting - Code folding - Symbol name auto-completion - Construct completion/snippets - Auto-closing of XML and HTML tags - Call tips - Many supported filetypes including C, Java, PHP, HTML, Python, Perl, Pascal (full list) - Symbol lists - Code navigation - Build system to compile and execute your code - Simple project management - Plugin interface Signed-off-by: Baptist BENOIST <return_0@live.com>
2012-10-16 17:30:08 +02:00
geany = callPackage ../applications/editors/geany { };
New packages: libgksu, gksu
2014-08-05 23:28:12 +02:00
gksu = callPackage ../applications/misc/gksu { };
gnuradio: new package Add GNU Radio, the free & open-source software development toolkit that provides signal processing blocks to implement software radios.
2013-05-02 12:44:36 +02:00
gnuradio = callPackage ../applications/misc/gnuradio {
inherit (pythonPackages) lxml numpy scipy matplotlib pyopengl;
fftw = fftwFloat;
};
Add geany-1.22 Geany is a small and lightweight Integrated Development Environment. It was developed to provide a small and fast IDE, which has only a few dependencies from other packages. Another goal was to be as independent as possible from a special Desktop Environment like KDE or GNOME. Geany only requires the GTK2 runtime libraries. Some basic features of Geany: - Syntax highlighting - Code folding - Symbol name auto-completion - Construct completion/snippets - Auto-closing of XML and HTML tags - Call tips - Many supported filetypes including C, Java, PHP, HTML, Python, Perl, Pascal (full list) - Symbol lists - Code navigation - Build system to compile and execute your code - Simple project management - Plugin interface Signed-off-by: Baptist BENOIST <return_0@live.com>
2012-10-16 17:30:08 +02:00
gnuradio-osmosdr: new package This is a Gnuradio block for OsmoSDR and rtl-sdr. http://sdr.osmocom.org/trac/wiki/GrOsmoSDR
2014-03-08 18:13:29 +01:00
gnuradio-osmosdr = callPackage ../applications/misc/gnuradio-osmosdr { };
applications/misc/goldendict: New nixpkg. svn path=/nixpkgs/trunk/; revision=32045
2012-02-05 22:02:27 +01:00
goldendict = callPackage ../applications/misc/goldendict { };
googleMusicmanager: add expression close #1056
2013-10-10 05:36:43 +02:00
google-musicmanager = callPackage ../applications/audio/google-musicmanager { };
gpicview: add expression 0.2.4 close #1123.
2013-10-27 00:25:42 +02:00
gpicview = callPackage ../applications/graphics/gpicview { };
gqrx: new package Gqrx is a software defined radio receiver powered by GNU Radio and the Qt GUI toolkit. It can process I/Q data from many types of input devices, including Funcube Dongle Pro/Pro+, rtl-sdr, HackRF, and Universal Software Radio Peripheral (USRP) devices. http://gqrx.dk/
2014-03-08 18:16:10 +01:00
gqrx = callPackage ../applications/misc/gqrx { };
adding gis system grass (graphviz 3d is not supported yet) svn path=/nixpkgs/trunk/; revision=22131
2010-06-03 17:19:59 +02:00
grass = import ../applications/misc/grass {
inherit (xlibs) libXmu libXext libXp libX11 libXt libSM libICE libXpm
libXaw libXrender;
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
inherit config composableDerivation stdenv fetchurl
adding gis system grass (graphviz 3d is not supported yet) svn path=/nixpkgs/trunk/; revision=22131
2010-06-03 17:19:59 +02:00
lib flex bison cairo fontconfig
gdal zlib ncurses gdbm proj pkgconfig swig
blas liblapack libjpeg libpng mysql unixODBC mesa postgresql python
grass: pin to ffmpeg 0.10
2013-12-16 14:40:04 +01:00
readline sqlite tcl tk libtiff freetype makeWrapper wxGTK;
adding gis system grass (graphviz 3d is not supported yet) svn path=/nixpkgs/trunk/; revision=22131
2010-06-03 17:19:59 +02:00
fftw = fftwSinglePrec;
grass: pin to ffmpeg 0.10
2013-12-16 14:40:04 +01:00
ffmpeg = ffmpeg_0_10;
adding gis system grass (graphviz 3d is not supported yet) svn path=/nixpkgs/trunk/; revision=22131
2010-06-03 17:19:59 +02:00
motif = lesstif;
opendwg = libdwg;
wxPython = wxPython28;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
grip = callPackage ../applications/misc/grip {
adding grip, a gui rip application (segfaults on amd64 ?) svn path=/nixpkgs/trunk/; revision=17305
2009-09-20 19:01:31 +02:00
inherit (gnome) libgnome libgnomeui vte;
};
gtimelog: New expression
2013-06-24 17:38:16 +02:00
gtimelog = pythonPackages.gtimelog;
gucharmap: new package GNOME Character Map, based on the Unicode Character Database https://wiki.gnome.org/Apps/Gucharmap
2014-02-17 12:20:01 +01:00
inherit (gnome3) gucharmap;
all-packages.nix: strip trailing whitespace
2014-02-28 11:02:46 +01:00
applications/audio/guitarix: New nixpkg.
2013-02-03 17:36:32 +01:00
guitarix = callPackage ../applications/audio/guitarix {
fftw = fftwSinglePrec;
};
photivo: Add photivo photo processor / RAW development laboratory.
2013-05-22 18:25:30 +02:00
photivo = callPackage ../applications/graphics/photivo { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wavesurfer = callPackage ../applications/misc/audio/wavesurfer { };
added wavesurfer (sound analysis tool) and its dependency snack (tcl /python sound tool library) svn path=/nixpkgs/trunk/; revision=12904
2008-09-24 02:42:06 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
wireshark = callPackage ../applications/networking/sniffers/wireshark { };
pkgs/top-level/all-packages.nix: strip trailing white space svn path=/nixpkgs/trunk/; revision=21416
2010-04-29 10:54:02 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wvdial = callPackage ../os-specific/linux/wvdial { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* fbida: fix a segfault in exiftran. svn path=/nixpkgs/trunk/; revision=25588
2011-01-16 17:28:08 +01:00
fbida = callPackage ../applications/graphics/fbida { };
Adding fbida, framebuffer image viewer svn path=/nixpkgs/trunk/; revision=16571
2009-08-04 09:14:43 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
fdupes = callPackage ../tools/misc/fdupes { };
added fdupes-1.40 (utility to find duplicate files) provided by Marco Maggesi svn path=/nixpkgs/trunk/; revision=13134
2008-10-28 12:56:43 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
feh = callPackage ../applications/graphics/feh { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Added FileZilla-3.6.0.2.
2012-12-31 11:59:08 +01:00
filezilla = callPackage ../applications/networking/ftp/filezilla { };
* Firefox 13.0. It's not stable yet though - it seems to hang the first time a Flash control is loaded, with the following message on stderr: /nix/store/c5ma4l7nlzcwdkjzrflni58aacqrfs1y-xulrunner-13.0/lib/xulrunner-13.0/plugin-container: symbol lookup error: /nix/store/c5ma4l7nlzcwdkjzrflni58aacqrfs1y-xulrunner-13.0/lib/xulrunner-13.0/plugin-container: undefined symbol: malloc_message Need to investigate where malloc_message is defined. svn path=/nixpkgs/trunk/; revision=34368
2012-06-06 16:35:56 +02:00
firefox13Pkgs = callPackage ../applications/networking/browsers/firefox/13.0.nix {
* Firefox 12.0. svn path=/nixpkgs/trunk/; revision=33931
2012-04-26 15:25:20 +02:00
inherit (gnome) libIDL;
};
firefoxWrapper: Fix the name
2014-03-10 15:18:48 +01:00
firefox13Wrapper = wrapFirefox { browser = firefox13Pkgs.firefox; };
* Firefox 12.0. svn path=/nixpkgs/trunk/; revision=33931
2012-04-26 15:25:20 +02:00
firefox: bring back version 30.0 for zotero
2014-08-04 18:13:48 +02:00
firefox30Pkgs = callPackage ../applications/networking/browsers/firefox/30.nix {
inherit (gnome) libIDL;
inherit (pythonPackages) pysqlite;
libpng = libpng_apng;
};
firefox: Build without xulrunner Fixes #2950.
2014-07-23 15:31:49 +02:00
firefox = callPackage ../applications/networking/browsers/firefox {
firefox: Update to 20.0
2013-04-09 18:00:26 +02:00
inherit (gnome) libIDL;
inherit (pythonPackages) pysqlite;
};
firefox: Build without xulrunner Fixes #2950.
2014-07-23 15:31:49 +02:00
firefoxWrapper = wrapFirefox { browser = pkgs.firefox; };
firefox: Update to 20.0
2013-04-09 18:00:26 +02:00
add firefox-bin: the binary package for Firefox web browser
2014-06-23 15:03:11 +02:00
firefox-bin = callPackage ../applications/networking/browsers/firefox-bin {
gconf = pkgs.gnome.GConf;
inherit (pkgs.gnome) libgnome libgnomeui;
inherit (pkgs.xlibs) libX11 libXScrnSaver libXext
libXinerama libXrender libXt;
};
firefox: Update to 20.0
2013-04-09 18:00:26 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
flac = callPackage ../applications/audio/flac { };
* Added Adobe Flash Player 10. svn path=/nixpkgs/trunk/; revision=13085
2008-10-16 15:36:27 +02:00
Remove obsolete versions of Flash
2012-10-05 03:18:44 +02:00
flashplayer = callPackage ../applications/networking/browsers/mozilla-plugins/flashplayer-11 {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
debug = config.flashplayer.debug or false;
Adding flashplayer11. It builds fine for me on x86_64. Patch by Eduard Carreras. svn path=/nixpkgs/trunk/; revision=30712
2011-12-03 16:16:17 +01:00
};
Fluxbox: new package (1.3.5)
2014-08-18 15:08:18 +02:00
fluxbox = callPackage ../applications/window-managers/fluxbox { };
FME: New Package #3695
2014-09-03 09:47:47 +02:00
fme = callPackage ../applications/misc/fme {
inherit (gnome) libglademm;
inherit pkgconfig autoconf automake gettext;
};
Making freecad install; it still does not find all shared objects though. Either eigen changed the hash of the tarball, or I did not commit its latest hash. I add boost 1.46 apart, because 1.44 does not work easily for freecad. svn path=/nixpkgs/trunk/; revision=26151
2011-03-04 10:48:24 +01:00
freecad = callPackage ../applications/graphics/freecad {
Setting opencascade 6.5 to freecad for it to build.
2013-05-30 19:25:01 +02:00
opencascade = opencascade_6_5;
freecad: add matplotlib and pycollada dependencies When FreeCAD is started it prints that it's missing matplotlib and pycollada: $ FreeCAD [...] matplotlib not found, Plot module will be disabled pycollada not found, collada support will be disabled. The closure size of freecad is currently at 1.9 GiB. Adding these two deps increase it to 2.0 GiB. Reflow the expression function argument list.
2013-12-14 11:35:43 +01:00
inherit (pythonPackages) matplotlib pycollada;
Making freecad install; it still does not find all shared objects though. Either eigen changed the hash of the tarball, or I did not commit its latest hash. I add boost 1.46 apart, because 1.44 does not work easily for freecad. svn path=/nixpkgs/trunk/; revision=26151
2011-03-04 10:48:24 +01:00
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
freemind = callPackage ../applications/misc/freemind {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
jdk = jdk;
jre = jdk;
};
Adding freenet I don't build freenet_ext or bcprov, I just take the jar. Freenet irc people told me that freenet_ext barely changes and it's a hell to build.
2013-04-13 15:00:02 +02:00
freenet = callPackage ../applications/networking/p2p/freenet { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
freepv = callPackage ../applications/graphics/freepv { };
Adding freepv, without its mozilla plug-in. svn path=/nixpkgs/trunk/; revision=14954
2009-04-08 22:05:59 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xfontsel = callPackage ../applications/misc/xfontsel { };
xlsfonts = callPackage ../applications/misc/xlsfonts { };
Adding xfontsel. A bit hacky (to work well, it requires copying its app-defaults to $HOME) As app-defaults should be installed with the libXt (maybe it's libXt which loads them), and stracing that is the place where the code looks for app-defaults (the libXt store path), I don't know of any better solution in nixpkgs by now. svn path=/nixpkgs/trunk/; revision=19092
2009-12-24 15:48:36 +01:00
freerdp: pin to ffmpeg 1
2013-12-23 10:51:07 +01:00
freerdp = callPackage ../applications/networking/remote/freerdp {
ffmpeg = ffmpeg_1;
};
Add freerdp svn path=/nixpkgs/trunk/; revision=29068
2011-09-07 01:32:01 +02:00
Add unstable version of freerdp svn path=/nixpkgs/trunk/; revision=29070
2011-09-07 05:41:18 +02:00
freerdpUnstable = callPackage ../applications/networking/remote/freerdp/unstable.nix { };
freicoin: use default db4 now db48 is default
2013-12-16 14:37:21 +01:00
freicoin = callPackage ../applications/misc/freicoin { };
Adding freicoin 0.0.1
2012-12-29 10:46:54 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
fspot = callPackage ../applications/graphics/f-spot {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
inherit (gnome) libgnome libgnomeui;
gtksharp = gtksharp1;
};
Add Fuze for Linux 1.0.5
2013-11-18 20:39:17 +01:00
fuze = callPackage ../applications/networking/instant-messengers/fuze {};
Added gcolor2
2014-08-05 09:22:41 +02:00
gcolor2 = callPackage ../applications/graphics/gcolor2 { };
add get_iplayer 2.80 svn path=/nixpkgs/trunk/; revision=28912
2011-08-30 02:14:16 +02:00
get_iplayer = callPackage ../applications/misc/get_iplayer {};
gimp 2.8 - rename package from gimp_2_8_0 to gimp_2_8 as discussed on mailing list[1] - remove babl_0_1_10 and gegl_0_2_0 and use them as default versions [1] http://article.gmane.org/gmane.linux.distributions.nixos/8708 svn path=/nixpkgs/trunk/; revision=34444
2012-06-11 09:17:39 +02:00
gimp_2_8 = callPackage ../applications/graphics/gimp/2.8.nix {
Applying the patch from Rok Garbas to add GIMP 2.8.0 svn path=/nixpkgs/trunk/; revision=34352
2012-06-04 19:38:47 +02:00
inherit (gnome) libart_lgpl;
gimp-2.8: Fix build http://hydra.nixos.org/build/4126152
2013-02-19 13:19:31 +01:00
webkit = null;
keep lcms versioning in all-packages.nix
2013-06-29 16:07:15 +02:00
lcms = lcms2;
gimp: wrap plugins with PYTHONPATH, fix #223
2014-01-31 07:05:53 +01:00
wrapPython = pythonPackages.wrapPython;
Applying the patch from Rok Garbas to add GIMP 2.8.0 svn path=/nixpkgs/trunk/; revision=34352
2012-06-04 19:38:47 +02:00
};
gimp: change default from 2.6 to 2.8
2013-11-10 17:21:49 +01:00
gimp = gimp_2_8;
gimp: revert broken gimp-2.6 dependencies
2012-08-22 22:13:43 +02:00
Adding the GAP gimp plugin, and making nix-env recurse into the gimp plugins attribute set. svn path=/nixpkgs/trunk/; revision=19936
2010-02-11 16:08:05 +01:00
gimpPlugins = recurseIntoAttrs (import ../applications/graphics/gimp/plugins {
inherit pkgs gimp;
});
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
adding gitAttr now containing qgit, stgit, topGit, hg2git updating gitGit (git dev version), adding qgit-git (dev version) svn path=/nixpkgs/trunk/; revision=13816
2009-01-20 23:15:42 +01:00
gitAndTools = recurseIntoAttrs (import ../applications/version-management/git-and-tools {
inherit pkgs;
});
git = gitAndTools.git;
Add `gitFull'. svn path=/nixpkgs/trunk/; revision=19525
2010-01-18 17:07:44 +01:00
gitFull = gitAndTools.gitFull;
all-packages.nix: added low-priority 'gitSVN' expression, a variant of git with SVN support (but no GUI) svn path=/nixpkgs/trunk/; revision=26827
2011-04-13 19:53:26 +02:00
gitSVN = gitAndTools.gitSVN;
new: qgit is a qt-based graphical front-end for git svn path=/nixpkgs/trunk/; revision=12299
2008-07-07 13:48:24 +02:00
git-repo-1.19
2013-12-26 00:44:16 +01:00
gitRepo = callPackage ../applications/version-management/git-repo {
python = python27;
};
gitolite: 3.6.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-26 04:50:16 +02:00
gitolite = callPackage ../applications/version-management/gitolite { };
Add gitg: Gnome GUI for git
2014-01-10 16:15:21 +01:00
inherit (gnome3) gitg;
Adding giv. svn path=/nixpkgs/trunk/; revision=26709
2011-04-06 12:00:48 +02:00
giv = callPackage ../applications/graphics/giv {
Giv wants the pcre with unicode support. svn path=/nixpkgs/trunk/; revision=26722
2011-04-06 17:18:14 +02:00
pcre = pcre.override { unicodeSupport = true; };
Adding giv. svn path=/nixpkgs/trunk/; revision=26709
2011-04-06 12:00:48 +02:00
};
new: qgit is a qt-based graphical front-end for git svn path=/nixpkgs/trunk/; revision=12299
2008-07-07 13:48:24 +02:00
Add gmrun-0.9.2 Signed-off-by: Baptist BENOIST <return_0@live.com>
2012-10-16 17:31:06 +02:00
gmrun = callPackage ../applications/misc/gmrun {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gnucash = callPackage ../applications/office/gnucash {
gnucash: fix for new intltool
2013-02-16 15:35:14 +01:00
inherit (gnome2) libgnomeui libgtkhtml gtkhtml libbonoboui libgnomeprint libglade libart_lgpl;
gconf = gnome2.GConf;
Prepare for the Guile 2.0 switchover. svn path=/nixpkgs/trunk/; revision=25976
2011-02-15 14:14:29 +01:00
guile = guile_1_8;
all-packages.nix: Changed gnucash expression to override the 'scheme' argument in slibGuile so that the library is built with the same version of guile as gnucash is. svn path=/nixpkgs/trunk/; revision=27685
2011-07-09 14:11:41 +02:00
slibGuile = slibGuile.override { scheme = guile_1_8; };
gnumeric: add schemas and icons, refactor Also move goffice under gnome3, as it's released in the same way.
2013-12-28 15:34:08 +01:00
goffice = goffice_0_8;
Add GnuCash. svn path=/nixpkgs/trunk/; revision=17551
2009-09-30 15:11:17 +02:00
};
all-packages.nix: cosmetic
2014-01-15 17:22:20 +01:00
Fix goffice_0_8 after gnome-3 directory renaming
2014-05-20 16:03:11 +02:00
goffice_0_8 = callPackage ../desktops/gnome-3/3.10/misc/goffice/0.8.nix {
gnumeric: add schemas and icons, refactor Also move goffice under gnome3, as it's released in the same way.
2013-12-28 15:34:08 +01:00
inherit (gnome2) libglade libgnomeui;
gconf = gnome2.GConf;
libart = gnome2.libart_lgpl;
}; # latest version: gnome3.goffice
Add GnuCash. svn path=/nixpkgs/trunk/; revision=17551
2009-09-30 15:11:17 +02:00
Packaging PyCharm IDE
2014-07-06 22:44:10 +02:00
ideas = recurseIntoAttrs ( (callPackage ../applications/editors/idea { })
// (callPackage ../applications/editors/idea/pycharm.nix { }));
Add GnuCash. svn path=/nixpkgs/trunk/; revision=17551
2009-09-30 15:11:17 +02:00
Add quvi Patch submitted by mornfall svn path=/nixpkgs/trunk/; revision=30720
2011-12-03 23:21:00 +01:00
libquvi = callPackage ../applications/video/quvi/library.nix { };
Add mi2ly MIDI to lilypond converter
2013-07-18 06:50:59 +02:00
mi2ly = callPackage ../applications/audio/mi2ly {};
Adding praat.
2012-08-27 20:25:54 +02:00
praat = callPackage ../applications/audio/praat { };
Add quvi Patch submitted by mornfall svn path=/nixpkgs/trunk/; revision=30720
2011-12-03 23:21:00 +01:00
quvi = callPackage ../applications/video/quvi/tool.nix { };
quvi_scripts = callPackage ../applications/video/quvi/scripts.nix { };
Cleanup svn path=/nixpkgs/trunk/; revision=24224
2010-10-11 21:59:22 +02:00
qjackctl = callPackage ../applications/audio/qjackctl { };
added qjackctl svn path=/nixpkgs/trunk/; revision=12650
2008-08-18 18:03:21 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
gkrellm = callPackage ../applications/misc/gkrellm { };
Add GKrellM, a graphical system monitor. svn path=/nixpkgs/trunk/; revision=10660
2008-02-13 17:38:33 +01:00
Adding GMU, a music player for small portable devices, written in SDL. svn path=/nixpkgs/trunk/; revision=26266
2011-03-10 23:20:35 +01:00
gmu = callPackage ../applications/audio/gmu { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gnash = callPackage ../applications/video/gnash {
GNU Gnash 0.8.8. svn path=/nixpkgs/trunk/; revision=23365
2010-08-23 16:52:48 +02:00
inherit (gnome) gtkglext;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gnome_mplayer = callPackage ../applications/video/gnome-mplayer {
* Added gecko-mediaplayer, a browser plugin that uses gnome-mplayer to play video. Seems to be more stable than mplayerplug-in. svn path=/nixpkgs/trunk/; revision=16379
2009-07-15 22:34:08 +02:00
inherit (gnome) GConf;
};
Added gnumeric. svn path=/nixpkgs/trunk/; revision=34272
2012-05-29 14:21:33 +02:00
gnumeric = callPackage ../applications/office/gnumeric {
gnumeric: add schemas and icons, refactor Also move goffice under gnome3, as it's released in the same way.
2013-12-28 15:34:08 +01:00
inherit (gnome3) goffice gnome_icon_theme;
Added gnumeric. svn path=/nixpkgs/trunk/; revision=34272
2012-05-29 14:21:33 +02:00
};
Updating gnunet to 0.10.0.
2014-01-14 09:41:14 +01:00
gnunet = callPackage ../applications/networking/p2p/gnunet {
libgcrypt = libgcrypt_1_6;
};
Adding the gnunet 0.9 (svn), which works incompatible with the latest gnunet released. I updated some libs to get it built. svn path=/nixpkgs/trunk/; revision=29313
2011-09-16 22:50:24 +02:00
Adding gnunet-svn and libgcrypt-git. gnunet-svn can't interoperate with gnunet.
2013-05-27 23:33:51 +02:00
gnunet_svn = lowPrio (callPackage ../applications/networking/p2p/gnunet/svn.nix {
add libgcrypt-1.6
2013-12-20 23:56:26 +01:00
libgcrypt = libgcrypt_1_6;
Adding gnunet-svn and libgcrypt-git. gnunet-svn can't interoperate with gnunet.
2013-05-27 23:33:51 +02:00
});
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gocr = callPackage ../applications/graphics/gocr { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Gobby: rename to gobby5 because it's apparently still considered very new and incompatible with stable gobby4 svn path=/nixpkgs/trunk/; revision=24043
2010-10-04 06:15:55 +02:00
gobby5 = callPackage ../applications/editors/gobby {
Packaged Gobby svn path=/nixpkgs/trunk/; revision=24040
2010-10-04 06:15:23 +02:00
inherit (gnome) gtksourceview;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gphoto2 = callPackage ../applications/misc/gphoto2 { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Adding Gphoto2FS - filesystem for attached cameras svn path=/nixpkgs/trunk/; revision=16841
2009-08-24 23:35:45 +02:00
gphoto2fs = builderDefsPackage ../applications/misc/gphoto2/gphotofs.nix {
gphoto*: update for changed libgphoto version
2013-04-20 12:44:05 +02:00
inherit libgphoto2 fuse pkgconfig glib libtool;
Adding Gphoto2FS - filesystem for attached cameras svn path=/nixpkgs/trunk/; revision=16841
2009-08-24 23:35:45 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
graphicsmagick = callPackage ../applications/graphics/graphicsmagick { };
photivo: Add photivo photo processor / RAW development laboratory.
2013-05-22 18:25:30 +02:00
graphicsmagick_q16 = callPackage ../applications/graphics/graphicsmagick { quantumdepth = 16; };
Adding GraphicsMagick svn path=/nixpkgs/trunk/; revision=20383
2010-03-04 15:44:47 +01:00
graphicsmagick137: fix by using older libpng ToDo: is this still needed by someone?
2013-02-28 15:54:15 +01:00
graphicsmagick137 = callPackage ../applications/graphics/graphicsmagick/1.3.7.nix {
libpng = libpng12;
};
Adding graphicsmagick 1.3.7 for octave imread() and alike to work. svn path=/nixpkgs/trunk/; revision=20390
2010-03-04 17:41:14 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gtkpod = callPackage ../applications/audio/gtkpod {
Adding gtkpod, and fixing libgpod meta info. svn path=/nixpkgs/trunk/; revision=15016
2009-04-13 17:41:10 +02:00
inherit (gnome) libglade;
};
jbidwatcher: generalized java support so that the package can be built on Darwin, too svn path=/nixpkgs/trunk/; revision=27923
2011-07-24 22:26:28 +02:00
jbidwatcher = callPackage ../applications/misc/jbidwatcher {
java = if stdenv.isLinux then jre else jdk;
};
all-packages.nix: added jbidwatcher, a tool to monitor and snipe ebay auctions svn path=/nixpkgs/trunk/; revision=27881
2011-07-21 19:01:31 +02:00
Added qrencode and qrdecode - tools for QR code. Qrdecode behaves strangely (Debian package does the same, so probably upstream bug) svn path=/nixpkgs/trunk/; revision=13304
2008-11-15 18:54:09 +01:00
qrdecode = builderDefsPackage (import ../tools/graphics/qrdecode) {
More 'libpng = libpng12' svn path=/nixpkgs/branches/libpng15/; revision=31889
2012-01-27 18:55:41 +01:00
libpng = libpng12;
Fixing libdecodeqr build by using previous OpenCV svn path=/nixpkgs/trunk/; revision=28169
2011-08-05 18:13:20 +02:00
opencv = opencv_2_1;
Added qrencode and qrdecode - tools for QR code. Qrdecode behaves strangely (Debian package does the same, so probably upstream bug) svn path=/nixpkgs/trunk/; revision=13304
2008-11-15 18:54:09 +01:00
};
qrencode-3.2.0 Remove builderDefs magic, add meta Cherry-pick r31382 from branches/libpng15 svn path=/nixpkgs/trunk/; revision=31385
2012-01-07 00:05:11 +01:00
qrencode = callPackage ../tools/graphics/qrencode { };
Added qrencode and qrdecode - tools for QR code. Qrdecode behaves strangely (Debian package does the same, so probably upstream bug) svn path=/nixpkgs/trunk/; revision=13304
2008-11-15 18:54:09 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
gecko_mediaplayer = callPackage ../applications/networking/browsers/mozilla-plugins/gecko-mediaplayer {
* Added gecko-mediaplayer, a browser plugin that uses gnome-mplayer to play video. Seems to be more stable than mplayerplug-in. svn path=/nixpkgs/trunk/; revision=16379
2009-07-15 22:34:08 +02:00
inherit (gnome) GConf;
* Fix evaluation problems. svn path=/nixpkgs/branches/x-updates/; revision=22668
2010-07-20 00:24:26 +02:00
browser = firefox;
* Added gecko-mediaplayer, a browser plugin that uses gnome-mplayer to play video. Seems to be more stable than mplayerplug-in. svn path=/nixpkgs/trunk/; revision=16379
2009-07-15 22:34:08 +02:00
};
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
geeqie = callPackage ../applications/graphics/geeqie { };
Add Geeqie, a GQview fork. svn path=/nixpkgs/trunk/; revision=18613
2009-11-25 09:58:42 +01:00
Adding LinuxSampler and dependencies, using SVN version for SFZ support svn path=/nixpkgs/trunk/; revision=33865
2012-04-20 22:39:42 +02:00
gigedit = callPackage ../applications/audio/gigedit { };
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
gqview = callPackage ../applications/graphics/gqview { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
gmpc 11.8.16: New package, a GTK MPD (Music Player Daemon) client
2013-04-04 17:42:17 +02:00
gmpc = callPackage ../applications/audio/gmpc { };
gecko-mediaplayer: updated to version 1.0.5 I hoped this update would fix the build errors, but in fact it didn't. :-( svn path=/nixpkgs/trunk/; revision=32518
2012-02-23 19:32:42 +01:00
gmtk = callPackage ../applications/networking/browsers/mozilla-plugins/gmtk {
inherit (gnome) GConf;
};
* Use callPackage_i686 for i686-only packages. svn path=/nixpkgs/trunk/; revision=23113
2010-08-11 15:25:30 +02:00
googleearth = callPackage_i686 ../applications/misc/googleearth { };
Adding google earth. svn path=/nixpkgs/trunk/; revision=15014
2009-04-13 17:40:51 +02:00
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
google_talk_plugin = callPackage ../applications/networking/browsers/mozilla-plugins/google-talk-plugin {
libpng = libpng12;
};
* Added the Google Talk plugin. Doesn't work yet (says ‘ABORT: X_GLXCreateContext: BadValue’). svn path=/nixpkgs/trunk/; revision=27825
2011-07-18 16:44:28 +02:00
A top-level entry for gosmore svn path=/nixpkgs/trunk/; revision=22227
2010-06-12 00:37:47 +02:00
gosmore = builderDefsPackage ../applications/misc/gosmore {
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit fetchsvn curl pkgconfig libxml2 gtk;
* Don't set `platforms' on Google Earth because we don't want Hydra to build it. svn path=/nixpkgs/trunk/; revision=19839
2010-02-05 20:22:26 +01:00
};
Adding google earth. svn path=/nixpkgs/trunk/; revision=15014
2009-04-13 17:40:51 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gpsbabel = callPackage ../applications/misc/gpsbabel { };
Add `gpscorrelate', a GPS photo correlation tool. svn path=/nixpkgs/trunk/; revision=15814
2009-06-02 00:43:36 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
gpscorrelate = callPackage ../applications/misc/gpscorrelate { };
Add `gpscorrelate', a GPS photo correlation tool. svn path=/nixpkgs/trunk/; revision=15814
2009-06-02 00:43:36 +02:00
* wrapPythonPrograms: rewrite the common "#! .../env python" idiom to "#! .../python". svn path=/nixpkgs/branches/modular-python/; revision=26583
2011-03-28 19:19:27 +02:00
gpsd = callPackage ../servers/gpsd { };
Add `gpsd', a GPS service daemon. svn path=/nixpkgs/trunk/; revision=15809
2009-05-31 13:29:42 +02:00
Update guitone
2014-08-31 22:37:57 +02:00
guitone = callPackage ../applications/version-management/guitone {
graphviz = graphviz_2_32;
};
Add guitone. It compiles. Haven't checked whether it works. svn path=/nixpkgs/trunk/; revision=24566
2010-11-02 13:23:01 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gv = callPackage ../applications/misc/gv { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
add guvcview package
2014-02-06 23:00:59 +01:00
guvcview = callPackage ../os-specific/linux/guvcview { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hello = callPackage ../applications/misc/hello/ex-2 { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
add herbstluftwm 0.5.2
2013-07-17 18:02:53 +02:00
herbstluftwm = callPackage ../applications/window-managers/herbstluftwm { };
Added hexchat
2014-03-07 19:42:29 +01:00
hexchat = callPackage ../applications/networking/irc/hexchat { };
hexedit: New package, version 1.2.12. A typical three-pane style hex editor, which is somewhat similar than bvi, but smaller and without vi-like keybindings. (Don't ask me why I use both, I just can't tell why I'm sometimes in bvi and sometimes in hexedit mood... there simply is no rational explanation) Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-09-14 22:41:41 +02:00
hexedit = callPackage ../applications/editors/hexedit { };
hipchat: Update to 2.2.1107
2014-05-27 00:48:30 +02:00
hipchat = callPackage ../applications/networking/instant-messengers/hipchat { };
Add hipchat messaging client Signed-off-by: Shea Levy <shea@shealevy.com>
2013-04-11 20:42:32 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
homebank = callPackage ../applications/office/homebank { };
Adding homebank, personal finance software. svn path=/nixpkgs/trunk/; revision=19698
2010-01-26 23:22:11 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
htmldoc = callPackage ../applications/misc/htmldoc {
fltk-1.3.0 svn path=/nixpkgs/trunk/; revision=31223
2012-01-03 11:02:33 +01:00
fltk = fltk13;
Adding htmldoc. I had to update fltk 1.1 for it to build. svn path=/nixpkgs/trunk/; revision=22096
2010-06-01 23:15:40 +02:00
};
hugin-2011.4.0 svn path=/nixpkgs/trunk/; revision=32170
2012-02-10 11:13:39 +01:00
hugin = callPackage ../applications/graphics/hugin { };
Adding enblend-fuse, libxmi and hugin. Maybe hugin doesn't run well enough still. svn path=/nixpkgs/trunk/; revision=14894
2009-04-05 23:41:38 +02:00
Adding Hydrogen: drum machine svn path=/nixpkgs/trunk/; revision=26866
2011-04-17 16:23:33 +02:00
hydrogen = callPackage ../applications/audio/hydrogen { };
Added i3wm. Added newer version of file. (this time tested, I screwed up a patch by garbas) svn path=/nixpkgs/trunk/; revision=33952
2012-04-30 16:34:57 +02:00
i3 = callPackage ../applications/window-managers/i3 { };
i3lock = callPackage ../applications/window-managers/i3/lock.nix {
i3lock: updating to 2.5
2013-07-08 01:18:12 +02:00
inherit (xorg) libxkbfile;
Added i3wm. Added newer version of file. (this time tested, I screwed up a patch by garbas) svn path=/nixpkgs/trunk/; revision=33952
2012-04-30 16:34:57 +02:00
cairo = cairo.override { xcbSupport = true; };
};
all-packages.nix: strip trailing whitespace
2014-02-28 11:02:46 +01:00
Add i3minator: i3 project manager similar to tmuxinator
2014-02-12 12:04:34 +01:00
i3minator = callPackage ../tools/misc/i3minator { };
Added i3wm. Added newer version of file. (this time tested, I screwed up a patch by garbas) svn path=/nixpkgs/trunk/; revision=33952
2012-04-30 16:34:57 +02:00
i3status = callPackage ../applications/window-managers/i3/status.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
i810switch = callPackage ../os-specific/linux/i810switch { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
icewm-1.3.7 svn path=/nixpkgs/trunk/; revision=31890
2012-01-27 19:56:31 +01:00
icewm = callPackage ../applications/window-managers/icewm { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Allowing abcde to make mp3. I had to add id3v2, and fix the id3lib build. svn path=/nixpkgs/trunk/; revision=23513
2010-08-29 17:53:42 +02:00
id3v2 = callPackage ../applications/audio/id3v2 { };
ifenslave: Add new package
2013-12-31 16:13:31 +01:00
ifenslave = callPackage ../os-specific/linux/ifenslave { };
Adding 'ii', irc it.
2012-07-26 09:25:52 +02:00
ii = callPackage ../applications/networking/irc/ii { };
move ike to applications/networking folder
2014-09-03 22:31:26 +02:00
ike = callPackage ../applications/networking/ike { };
add ike: IPSec client
2013-10-18 18:50:21 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
ikiwiki = callPackage ../applications/misc/ikiwiki {
pkgs/tools/typesetting/asciidoc: updated to version 8.5.1 New asciidoc versions do have a proper configure script. Using that simplifies the build instructions a bit. svn path=/nixpkgs/trunk/; revision=18076
2009-11-03 16:57:22 +01:00
inherit (perlPackages) TextMarkdown URI HTMLParser HTMLScrubber
pkgs/top-level/all-packages.nix: added RPC-XML support to ikiwiki This is required for the 'rst' plugin and for non-perl plugin support in general. svn path=/nixpkgs/trunk/; revision=21421
2010-04-29 11:35:20 +02:00
HTMLTemplate TimeDate CGISession DBFile CGIFormBuilder LocaleGettext
ikiwiki: enable pass phrase authentication support
2012-07-29 21:39:49 +02:00
RpcXML XMLSimple PerlMagick YAML YAMLLibYAML HTMLTree Filechdir
ikiwiki: support OpenID via HTTPS Also enable Perl LWPxParanoidAgent for "additional security".
2012-08-10 18:57:57 +02:00
AuthenPassphrase NetOpenIDConsumer LWPxParanoidAgent CryptSSLeay;
Adding the basics for 'ikiwiki'. I did not try how it serves the pages, but at least "ikiwiki --setup ikiwikipath/etc/auto.setup" works for me with git. svn path=/nixpkgs/trunk/; revision=17808
2009-10-14 23:00:54 +02:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
imagemagick = callPackage ../applications/graphics/ImageMagick {
* More cleanup. svn path=/nixpkgs/trunk/; revision=22795
2010-07-28 17:35:01 +02:00
tetex = null;
librsvg = null;
* ImageMagick: don't need to keep old versions I guess. * texFunctions.simpleTexToPNG: purity (use our own ImageMagick). svn path=/nixpkgs/trunk/; revision=11836
2008-05-16 13:26:23 +02:00
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
imagemagickBig = lowPrio (callPackage ../applications/graphics/ImageMagick { });
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Add Impressive (formerly known as `KeyJNote'). svn path=/nixpkgs/trunk/; revision=14618
2009-03-19 17:40:28 +01:00
# Impressive, formerly known as "KeyJNote".
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
impressive = callPackage ../applications/office/impressive {
Add Impressive (formerly known as `KeyJNote'). svn path=/nixpkgs/trunk/; revision=14618
2009-03-19 17:40:28 +01:00
# XXX These are the PyOpenGL dependencies, which we need here.
* Inkscape updated to 0.48.1. svn path=/nixpkgs/trunk/; revision=27555
2011-06-28 15:51:55 +02:00
inherit (pythonPackages) pyopengl;
};
Add Impressive (formerly known as `KeyJNote'). svn path=/nixpkgs/trunk/; revision=14618
2009-03-19 17:40:28 +01:00
Add inferno, a distributed cross-platform hosted OS
2014-06-25 01:52:53 +02:00
inferno = callPackage_i686 ../applications/inferno { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
inkscape = callPackage ../applications/graphics/inkscape {
adding python package lxml to make scripts in inkscape work svn path=/nixpkgs/trunk/; revision=17858
2009-10-18 06:43:40 +02:00
inherit (pythonPackages) lxml;
upgrade some packages to lcms2
2013-06-29 16:08:14 +02:00
lcms = lcms2;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
ion3 = callPackage ../applications/window-managers/ion-3 {
* Clean up indentation (expanded tabs etc.). svn path=/nixpkgs/trunk/; revision=11150
2008-03-17 10:41:28 +01:00
lua = lua5;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
vlada/ipe Adding the ipe editor. Signed-off-by: Vladimír Čunát <vcunat@gmail.com>
2013-01-03 16:13:55 +01:00
ipe = callPackage ../applications/graphics/ipe { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
iptraf = callPackage ../applications/networking/iptraf { };
Adding iptraf 3.0.0 (the last iptraf I found, last updated in 2005) It runs without complains if you "mkdir -p /var/run/iptraf /var/local/iptraf" svn path=/nixpkgs/trunk/; revision=17752
2009-10-12 12:52:47 +02:00
irssi: fix build on darwin * use `gccApple` (so we can cope with `-no-cpp-precompile`) * add `libintlOrEmpty`
2013-06-20 01:25:54 +02:00
irssi = callPackage ../applications/networking/irc/irssi {
# compile with gccApple on darwin to support the -no-cpp-precompile flag
stdenv = if stdenv.isDarwin
then stdenvAdapters.overrideGCC stdenv gccApple
else stdenv;
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
Adding fish (blowfish over irc) for irssi.
2013-04-13 01:35:16 +02:00
irssi_fish = callPackage ../applications/networking/irc/irssi/fish { };
Adding irssi-otr.
2013-04-13 17:09:27 +02:00
irssi_otr = callPackage ../applications/networking/irc/irssi/otr { };
Added the irc proxy "bip". svn path=/nixpkgs/trunk/; revision=32529
2012-02-24 00:47:26 +01:00
bip = callPackage ../applications/networking/irc/bip { };
Adding jack_capture: A program for recording soundfiles with jack
2012-08-25 01:57:24 +02:00
jack_capture = callPackage ../applications/audio/jack-capture { };
Add jack_oscrolloscope: a waveform viewer for JACK
2013-03-03 17:43:15 +01:00
jack_oscrolloscope = callPackage ../applications/audio/jack-oscrolloscope { };
applications/audio/jack-rack: New nixpkg.
2013-03-09 15:02:35 +01:00
jack_rack = callPackage ../applications/audio/jack-rack { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jackmeter = callPackage ../applications/audio/jackmeter { };
adding jackmeter svn path=/nixpkgs/trunk/; revision=17324
2009-09-21 11:58:33 +02:00
Add Jalv: an LV2 host for Jack This allows LV2 audio plugins to be connected to Jack applications
2013-03-01 01:33:08 +01:00
jalv = callPackage ../applications/audio/jalv { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jedit = callPackage ../applications/editors/jedit { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
jigdo = callPackage ../applications/misc/jigdo { };
adding jigdo-lite svn path=/nixpkgs/trunk/; revision=17020
2009-09-10 18:57:31 +02:00
Added jitsi
2014-03-04 13:17:57 +01:00
jitsi = callPackage ../applications/networking/instant-messengers/jitsi { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
joe = callPackage ../applications/editors/joe { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
add jbrout, a photo manager using IPTC keywords/EXIF svn path=/nixpkgs/trunk/; revision=28759
2011-08-22 22:26:11 +02:00
jbrout = callPackage ../applications/graphics/jbrout {
inherit (pythonPackages) lxml;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
jwm = callPackage ../applications/window-managers/jwm { };
added jwm expression provided by tachermourir (mailinglist) svn path=/nixpkgs/trunk/; revision=11281
2008-03-25 10:50:54 +01:00
Get rid of most references to gtkLibs svn path=/nixpkgs/trunk/; revision=33088
2012-03-14 22:57:32 +01:00
k3d = callPackage ../applications/graphics/k3d {
Fix K3D gtlglext handling
2013-03-21 10:45:12 +01:00
inherit (pkgs.gnome2) gtkglext;
Get rid of most references to gtkLibs svn path=/nixpkgs/trunk/; revision=33088
2012-03-14 22:57:32 +01:00
};
Add K3D 3D editor svn path=/nixpkgs/trunk/; revision=31850
2012-01-26 14:12:36 +01:00
Adding keepnote svn path=/nixpkgs/trunk/; revision=24695
2010-11-15 20:44:53 +01:00
keepnote = callPackage ../applications/office/keepnote {
pygtk = pyGtkGlade;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
kermit = callPackage ../tools/misc/kermit { };
Adding kermit. svn path=/nixpkgs/trunk/; revision=17114
2009-09-14 20:50:17 +02:00
Add key-mon a utility to show live keyboard and mouse status for teaching and screencasts
2012-11-11 18:13:04 +01:00
keymon = callPackage ../applications/video/key-mon { };
Updated kino to version 1.3.4 (and did some code standard fixes) svn path=/nixpkgs/trunk/; revision=27558
2011-06-29 18:21:02 +02:00
kino = callPackage ../applications/video/kino {
inherit (gnome) libglade;
kino (compiling but neither finding libX11 nor libghtread) and libiec61883 (dependency) added svn path=/nixpkgs/trunk/; revision=10133
2008-01-13 16:21:21 +01:00
};
koji: factor python module into an standalone app
2014-08-30 21:08:49 +02:00
koji = callPackage ../tools/package-management/koji { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lame = callPackage ../applications/audio/lame { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
larswm = callPackage ../applications/window-managers/larswm { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
lash = callPackage ../applications/audio/lash { };
Adding lash, session management system for GNU/Linux audio applications svn path=/nixpkgs/trunk/; revision=26926
2011-04-23 02:22:40 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ladspaH = callPackage ../applications/audio/ladspa-plugins/ladspah.nix { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
ladspaPlugins = callPackage ../applications/audio/ladspa-plugins {
Fix FFTW argument to Ladspa Plugins svn path=/nixpkgs/trunk/; revision=22414
2010-06-25 20:21:19 +02:00
fftw = fftwSinglePrec;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
applications/audio/caps: New nixpkg.
2013-03-09 14:54:03 +01:00
caps = callPackage ../applications/audio/caps { };
lastwatch: New package, version 0.4.1. This is actually one of my own programs I've written some years ago, but as I'm still using it on several systems, I'm adding it to nixpkgs. As it is an (at the moment, fanotify looks like it's more suitable) inotify based scrobbler, it of course requires the inotify feature to be enabled in the kernel. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-09-05 03:56:24 +02:00
lastwatch = callPackage ../applications/audio/lastwatch { };
add lastfmsubmitd
2014-01-02 11:57:08 +01:00
lastfmsubmitd = callPackage ../applications/audio/lastfmsubmitd { };
Modif lbdb package. Following the remarks after the 1st commit. * add in all-packages.nix sorted alphabetically * add platforms and license in default.nix
2013-08-27 11:08:11 +02:00
lbdb = callPackage ../tools/misc/lbdb { };
Adding LCI lambda calculus interpreter svn path=/nixpkgs/trunk/; revision=33962
2012-05-01 07:07:39 +02:00
lci = callPackage ../applications/science/logic/lci {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
ldcpp = callPackage ../applications/networking/p2p/ldcpp {
Added LinuxDC++. Claimed to support newer protocol - claim is by valknut team.. svn path=/nixpkgs/trunk/; revision=11132
2008-03-15 07:11:45 +01:00
inherit (gnome) libglade;
};
Adding a preliminary package for librecad. It fails to install still. svn path=/nixpkgs/trunk/; revision=31255
2012-01-03 22:14:14 +01:00
librecad = callPackage ../applications/misc/librecad { };
librecad: adding its 2.0 beta version too
2012-12-10 09:47:55 +01:00
librecad2 = callPackage ../applications/misc/librecad/2.0.nix { };
Rename openoffice directory to libreoffice
2013-01-29 12:36:01 +01:00
libreoffice = callPackage ../applications/office/libreoffice {
Adding what I have for today of libreoffice. It still does not build. svn path=/nixpkgs/trunk/; revision=31839
2012-01-26 00:04:34 +01:00
inherit (perlPackages) ArchiveZip CompressZlib;
I try to package libreoffice 3.5, as there was a weird segfault in 3.4, and they changed the build system in 3.5. It still does not build either... hopefully by more reachable troubles. svn path=/nixpkgs/trunk/; revision=33022
2012-03-12 21:15:08 +01:00
inherit (gnome) GConf ORBit2 gnome_vfs;
Giving the zip without NLS to libreoffice; I think this may fix a permission denid error at perl Archive/Zip. svn path=/nixpkgs/trunk/; revision=33098
2012-03-15 09:06:45 +01:00
zip = zip.override { enableNLS = false; };
Libreoffice update: not succesful yet
2014-06-27 14:25:19 +02:00
boost = boost155;
libreoffice: trying to make it build with openjdk
2012-08-24 09:20:27 +02:00
jdk = openjdk;
Making libreoffice have a configured fontconfig. I hope this will make some cppunit tests work, and thus we would not need to disable them. I update the patch that disables tests with one more test disabled, but I don't use it because I hope the build with fonts.conf will work fine. If that is the case, I'll remove the patch file later. If the fonts.conf trick does not work, I may want to extend the patch to disable all failing cases. svn path=/nixpkgs/trunk/; revision=33062
2012-03-14 10:40:26 +01:00
fontsConf = makeFontsConf {
fontDirectories = [
freefont_ttf xorg.fontmiscmisc xorg.fontbhttf
];
};
clucene_core: upgrade some packages to clucene_core_2 on my systems, I can now override "clucene_core = clucene_core_2" globally in nixpkgs. so perhaps we can soon drop v1?
2013-06-29 11:49:46 +02:00
clucene_core = clucene_core_2;
keep lcms versioning in all-packages.nix
2013-06-29 16:07:15 +02:00
lcms = lcms2;
Libreoffice update: not succesful yet
2014-06-27 14:25:19 +02:00
harfbuzz = harfbuzz.override {
withIcu = true; withGraphite2 = true;
};
Adding what I have for today of libreoffice. It still does not build. svn path=/nixpkgs/trunk/; revision=31839
2012-01-26 00:04:34 +01:00
};
liferea: add -- A GTK-based news feed reader
2013-06-27 20:43:05 +02:00
liferea = callPackage ../applications/networking/newsreaders/liferea { };
Adding lingot, a guitar tuner. svn path=/nixpkgs/trunk/; revision=27176
2011-05-07 19:52:57 +02:00
lingot = callPackage ../applications/audio/lingot {
inherit (gnome) libglade;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
links = callPackage ../applications/networking/browsers/links { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
ledger: renamed 2.6.3 version's nix file for consistency svn path=/nixpkgs/trunk/; revision=31780
2012-01-21 20:25:41 +01:00
ledger = callPackage ../applications/office/ledger/2.6.3.nix { };
ledger: update 3.x version to the latest Git snapshot
2013-04-21 20:37:53 +02:00
ledger3 = callPackage ../applications/office/ledger/3.0.nix { };
Add package ledger svn path=/nixpkgs/trunk/; revision=18316
2009-11-10 12:02:45 +01:00
Add Light Table editor.
2014-07-16 23:10:08 +02:00
lighttable = callPackage ../applications/editors/lighttable {};
Merge two nix exprs for links2, upgrade to 2.5 svn path=/nixpkgs/trunk/; revision=31962
2012-02-01 23:33:35 +01:00
links2 = callPackage ../applications/networking/browsers/links2 { };
Adding a stdenv version of links2, to be able to cross-build it. This can be removed once builderDefs can be made to support the stdenvCross adapter svn path=/nixpkgs/branches/stdenv-updates/; revision=24927
2010-11-29 19:03:03 +01:00
Fixing linphone crossed lib versions on libosip.
2013-06-29 16:55:35 +02:00
linphone = callPackage ../applications/networking/instant-messengers/linphone rec {
Latest exosip and linphone svn path=/nixpkgs/trunk/; revision=32172
2012-02-10 11:13:48 +01:00
inherit (gnome) libglade;
Linphone 3.6.1 Lots of updates and new/old libs to get the latest linphone It segfaults on running.
2013-06-29 16:50:56 +02:00
libexosip = libexosip_3;
Fixing linphone crossed lib versions on libosip.
2013-06-29 16:55:35 +02:00
libosip = libosip_3;
Adding linphone svn path=/nixpkgs/trunk/; revision=25545
2011-01-13 21:49:58 +01:00
};
linuxsampler: fix the build by using bison2
2014-02-19 23:50:24 +01:00
linuxsampler = callPackage ../applications/audio/linuxsampler {
bison = bison2;
};
Adding LinuxSampler and dependencies, using SVN version for SFZ support svn path=/nixpkgs/trunk/; revision=33865
2012-04-20 22:39:42 +02:00
Added llpp, a mupdf based pdf pager written in ocaml. Updated lablgl to 1.05 and mupdf to 1.4. Added myself as maintainer for lablgl.
2014-05-26 20:31:53 +02:00
llpp = callPackage ../applications/misc/llpp { inherit (ocamlPackages) lablgl; };
Adding lmms: Linux MultiMedia Studio svn path=/nixpkgs/trunk/; revision=26925
2011-04-23 01:00:55 +02:00
lmms = callPackage ../applications/audio/lmms { };
lrzsz: Add derivation [Bjørn Forsman: remove "a unix" from beginning of meta.description and capitalize first word]
2014-07-22 23:46:58 +02:00
lrzsz = callPackage ../tools/misc/lrzsz { };
luminanceHDR: add version 2.4.0 fixes #3229
2014-07-10 13:29:36 +02:00
luminanceHDR = callPackage ../applications/graphics/luminance-hdr { };
Adding lxdvdrip (it builds, but I still don't know how to make it work) svn path=/nixpkgs/trunk/; revision=23858
2010-09-18 18:29:07 +02:00
lxdvdrip = callPackage ../applications/video/lxdvdrip { };
Add Handbrake 0.9.9: DVD ripper This packaging splices off the unfree faac library and forces handbrake to use the (more recent/patched) versions of libraries in Nixpkgs. Produces the CLI HandbrakeCLI and optionally the GTK+ version ghb.
2014-05-04 01:55:36 +02:00
handbrake = callPackage ../applications/video/handbrake { };
Lilyterm: New Package (version 0.9.9.4) LilyTerm is a terminal emulator based off of libvte that aims to be fast and lightweight.
2014-08-27 15:06:59 +02:00
lilyterm = callPackage ../applications/misc/lilyterm {
inherit (gnome) vte;
gtk = gtk2;
};
extreme-tux-racer: update to 0.6.0
2014-08-29 13:09:05 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
lynx = callPackage ../applications/networking/browsers/lynx { };
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
LyX: add support for spell checking via enchant. Also comment on testing of other config options.
2012-08-07 14:45:18 +02:00
lyx = callPackage ../applications/misc/lyx { };
add game 'tcl2048'
2014-08-31 10:48:51 +02:00
new makeself: 2.1.5 svn path=/nixpkgs/trunk/; revision=25743
2011-02-02 00:24:13 +01:00
makeself = callPackage ../applications/misc/makeself { };
Adding the matchbox window manager svn path=/nixpkgs/trunk/; revision=23076
2010-08-10 00:40:51 +02:00
matchbox = callPackage ../applications/window-managers/matchbox { };
mcpp: Add package
2014-01-31 02:52:12 +01:00
mcpp = callPackage ../development/compilers/mcpp { };
Add mda-lv2 audio plugins
2013-02-24 11:26:32 +01:00
mda_lv2 = callPackage ../applications/audio/mda-lv2 { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
meld = callPackage ../applications/version-management/meld {
Adding 'meld' svn path=/nixpkgs/trunk/; revision=20963
2010-04-06 21:39:29 +02:00
inherit (gnome) scrollkeeper;
pygtk = pyGtkGlade;
};
mcomix: added version 0.98 Patch submitted by Jan Malakhovski <oxij@oxij.org>.
2012-07-02 16:20:43 +02:00
mcomix = callPackage ../applications/graphics/mcomix { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
mercurial = callPackage ../applications/version-management/mercurial {
Pass docutils from pythonPackages to mercurial
2012-07-18 12:42:33 +02:00
inherit (pythonPackages) curses docutils;
Minor cleanup
2012-11-29 14:40:25 +01:00
guiSupport = false; # use mercurialFull to get hgk GUI
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
};
Make appendToName do the right thing I.e. append a suffix *before* the version, rather than after. So we get "sqlite-interactive-3.8.0.2" instead of "sqlite-3.8.0.2-interactive". The latter is broken since nix-env just sees it the suffix as part of the version, so "nix-env -u" will happily upgrade "sqlite-3.8.0.2-interactive" to "sqlite-3.9".
2014-03-10 15:01:56 +01:00
mercurialFull = appendToName "full" (pkgs.mercurial.override { guiSupport = true; });
all-packages.nix: provide mercurialFull package that comes with GUI front-end This version preferred in user profiles, but not by packages that refer to mercurial by attribute name. svn path=/nixpkgs/trunk/; revision=31777
2012-01-21 20:08:56 +01:00
merkaartor: 0.17.2 svn path=/nixpkgs/trunk/; revision=27180
2011-05-08 11:35:37 +02:00
merkaartor = callPackage ../applications/misc/merkaartor { };
Adding merkaartor (a qt-based openstreetmap editor) svn path=/nixpkgs/trunk/; revision=22244
2010-06-13 21:32:04 +02:00
meshlab: fix forgotten qt47
2013-02-13 17:45:27 +01:00
meshlab = callPackage ../applications/graphics/meshlab { };
Adding muparser and meshlab. svn path=/nixpkgs/trunk/; revision=15585
2009-05-13 12:21:29 +02:00
Adding mhwaveedit, a sample editor svn path=/nixpkgs/trunk/; revision=33397
2012-03-24 19:59:26 +01:00
mhwaveedit = callPackage ../applications/audio/mhwaveedit {};
Add mid2key: a tool which maps midi notes to keystrokes
2013-04-05 01:24:36 +02:00
mid2key = callPackage ../applications/audio/mid2key { };
midori: update from 0.4.4 to 0.5.6 (close #1411)
2013-12-26 06:48:17 +01:00
midori = callPackage ../applications/networking/browsers/midori { };
Added Midori - a light, WebKit-based GTK browser. svn path=/nixpkgs/trunk/; revision=12818
2008-09-07 14:58:56 +02:00
Adding wrapFirefox for midori and vimprobable2, so they can enjoy the flash plugin. OTH, I'd prefer naming the attributes like "midoriWrapped" instead of "midoriWrapper". But I chose the 2nd to follow the example of those already in all-packages. svn path=/nixpkgs/trunk/; revision=33406
2012-03-25 15:59:17 +02:00
midoriWrapper = wrapFirefox
{ browser = midori; browserName = "midori"; desktopName = "Midori";
icon = "${midori}/share/icons/hicolor/22x22/apps/midori.png";
};
libmikmod and mikmod: update the former to 3.2.0, and add mikmod.
2012-07-04 23:43:25 +02:00
mikmod = callPackage ../applications/audio/mikmod { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
minicom = callPackage ../tools/misc/minicom { };
all-packages.nix changes for all the previous commits svn path=/nixpkgs/trunk/; revision=11564
2008-04-11 11:32:27 +02:00
Add minimodem package Signed-off-by: Ricky Elrod <ricky@elrod.me>
2014-05-12 00:44:38 +02:00
minimodem = callPackage ../applications/audio/minimodem { };
Adding minidjvu svn path=/nixpkgs/trunk/; revision=26957
2011-04-24 22:10:43 +02:00
minidjvu = callPackage ../applications/graphics/minidjvu { };
mirage: add version 0.9.5.2 Patch submitted by Jan Malakhovski <oxij@oxij.org>.
2012-07-02 16:27:41 +02:00
mirage = callPackage ../applications/graphics/mirage {};
mixxx: New package in version 1.11.0. Compiles fine on linux i686 and amd64. Adding myself as maintainer, even though I'm not using the package by myself, but a friend is using it for DJing from a NixOS live system I'm maintaining. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-10-28 03:16:32 +01:00
mixxx = callPackage ../applications/audio/mixxx {
inherit (vamp) vampSDK;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mmex = callPackage ../applications/office/mmex { };
Adding some kind of build expression for money manager ex. It expects to find its resource files in '.', and it also wants to write at '.'. I think this has to be fixed upstream. svn path=/nixpkgs/trunk/; revision=19655
2010-01-25 22:40:52 +01:00
Add moc music player
2013-12-14 22:16:18 +01:00
moc = callPackage ../applications/audio/moc { };
Add monkey's audio (.ape) lossless encoder/decoder. @vcunat: include version in the name, as is our custom
2012-10-27 19:33:47 +02:00
monkeysAudio = callPackage ../applications/audio/monkeys-audio { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
monodevelop = callPackage ../applications/editors/monodevelop {
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit (gnome) gnome_vfs libbonobo libglade libgnome GConf;
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
mozilla = firefox;
gtksharp = gtksharp2;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
monodoc = callPackage ../applications/editors/monodoc {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
gtksharp = gtksharp1;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
monotone = callPackage ../applications/version-management/monotone {
Moved monotone packages to a more appropriate position within all-packages.nix svn path=/nixpkgs/trunk/; revision=19144
2009-12-29 12:57:27 +01:00
lua = lua5;
Current Monotone needs older Boost
2013-02-10 22:18:23 +01:00
boost = boost149;
Moved monotone packages to a more appropriate position within all-packages.nix svn path=/nixpkgs/trunk/; revision=19144
2009-12-29 12:57:27 +01:00
};
monotoneViz = builderDefsPackage (import ../applications/version-management/monotone-viz/mtn-head.nix) {
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit ocaml graphviz pkgconfig autoconf automake libtool glib gtk;
* Update lablgtk2 (and enable hydra build) svn path=/nixpkgs/trunk/; revision=25213
2010-12-20 15:58:56 +01:00
inherit (ocamlPackages) lablgtk;
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit (gnome) libgnomecanvas;
Moved monotone packages to a more appropriate position within all-packages.nix svn path=/nixpkgs/trunk/; revision=19144
2009-12-29 12:57:27 +01:00
};
Add mopidy, a music server supporting spotify and the mpd protocol
2013-02-26 19:42:04 +01:00
mopidy = callPackage ../applications/audio/mopidy { };
mopidy: Update from 0.15.0 to 0.18.3 Also add the mopidy-spotify extension.
2014-07-12 09:33:53 +02:00
mopidy-spotify = callPackage ../applications/audio/mopidy-spotify { };
New package: mopidy-moped, a web client for the mopidy music player daemon
2014-07-28 19:51:08 +02:00
mopidy-moped = callPackage ../applications/audio/mopidy-moped { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
mozilla = callPackage ../applications/networking/browsers/mozilla {
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
inherit (gnome) libIDL;
};
Added mozplugger - an universal launching plugin for Mozilla programs svn path=/nixpkgs/trunk/; revision=14009
2009-02-08 18:23:22 +01:00
mozplugger = builderDefsPackage (import ../applications/networking/browsers/mozilla-plugins/mozplugger) {
Bumped boost libraries to version 1.38.0. svn path=/nixpkgs/trunk/; revision=14031
2009-02-11 11:02:10 +01:00
inherit firefox;
Added mozplugger - an universal launching plugin for Mozilla programs svn path=/nixpkgs/trunk/; revision=14009
2009-02-08 18:23:22 +01:00
inherit (xlibs) libX11 xproto;
};
* Added "easytag", a GUI for organizing id3tags in mp3s. * Updated some ocaml packages. * Updated coccinelle. svn path=/nixpkgs/trunk/; revision=33674
2012-04-09 11:42:20 +02:00
easytag = callPackage ../applications/audio/easytag { };
Add MP3Info, an MP3 tag editor. svn path=/nixpkgs/trunk/; revision=24363
2010-10-19 15:19:59 +02:00
mp3info = callPackage ../applications/audio/mp3info { };
Add mp3splt
2014-07-07 20:38:14 +02:00
mp3splt = callPackage ../applications/audio/mp3splt { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mpc123 = callPackage ../applications/audio/mpc123 { };
Add mpc123, a Musepack command-line player. svn path=/nixpkgs/trunk/; revision=19722
2010-01-28 23:34:27 +01:00
Adding mpg123 (it even cross-builds fine for the nanonote) svn path=/nixpkgs/branches/stdenv-updates/; revision=23313
2010-08-21 18:54:02 +02:00
mpg123 = callPackage ../applications/audio/mpg123 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mpg321 = callPackage ../applications/audio/mpg321 { };
all-packages.nix: strip trailing whitespace
2013-10-03 16:20:09 +02:00
add the mpc (mpd cli client) package
2013-09-23 15:41:04 +02:00
mpc_cli = callPackage ../applications/audio/mpc { };
Add mpg321, libao and libid3tag; upgrade libmad. svn path=/nixpkgs/trunk/; revision=10626
2008-02-11 22:02:38 +01:00
ncmcp: New expression
2014-03-25 15:45:24 +01:00
ncmpc = callPackage ../applications/audio/ncmpc { };
Add ncmpcpp Patch by mornfall svn path=/nixpkgs/trunk/; revision=30730
2011-12-05 02:32:25 +01:00
ncmpcpp = callPackage ../applications/audio/ncmpcpp { };
normalize 0.7.7: New package, an audio file normalizer
2013-04-04 17:06:49 +02:00
normalize = callPackage ../applications/audio/normalize { };
mplayer: Change directory name / attribute name from MPlayer to mplayer
2013-01-14 13:10:16 +01:00
mplayer = callPackage ../applications/video/mplayer {
mplayer: Take config.pulseaudio into account. Packages like libao or skype already honor config.pulseaudio, so let's assure that mplayer does so as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-11-22 02:30:34 +01:00
pulseSupport = config.pulseaudio or false;
mplayer: add option config.mplayer.vdpauSupport
2014-03-23 17:27:55 +01:00
vdpauSupport = config.mplayer.vdpauSupport or false;
mplayer: Take config.pulseaudio into account. Packages like libao or skype already honor config.pulseaudio, so let's assure that mplayer does so as well. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-11-22 02:30:34 +01:00
};
* Fix indentation mess-up in r9931. svn path=/nixpkgs/trunk/; revision=9973
2007-12-30 23:02:04 +01:00
mplayer2: switch to libav to fix build CC @viric. If someone has a better suggestion, do it. IMHO the main problem is the lack of maintenance from the side of mplayer2, e.g. latest release >3 years ago.
2014-07-21 09:57:48 +02:00
mplayer2 = callPackage ../applications/video/mplayer2 {
ffmpeg = libav_9; # see https://trac.macports.org/ticket/44386
};
Adding mplayer2, a mplayer fork. It can play files very well with "vdpau". It has a reworked vdpau pipeline compared to mplayer1. Mplayer1 fails to play well in my computer.
2013-01-31 00:26:30 +01:00
* Build Firefox 3 on top of xulrunner. This significantly reduces the build time and makes Firefox itself only 3 megabytes or so large. * Fixed building the mplayerplug-in on Firefox 3. Since the latter now uses xulrunner, we no longer need the firefox3Xul hack. TODO: do this for Icecat as well. svn path=/nixpkgs/trunk/; revision=13160
2008-10-30 14:00:50 +01:00
MPlayerPlugin = browser:
Add GNU IceCat 3, GNU's free variant of Mozilla Firefox 3. Currently, MPlayerPlugin can't be built with IceCat 3. svn path=/nixpkgs/trunk/; revision=12437
2008-07-28 17:55:11 +02:00
import ../applications/networking/browsers/mozilla-plugins/mplayerplug-in {
* Build Firefox 3 on top of xulrunner. This significantly reduces the build time and makes Firefox itself only 3 megabytes or so large. * Fixed building the mplayerplug-in on Firefox 3. Since the latter now uses xulrunner, we no longer need the firefox3Xul hack. TODO: do this for Icecat as well. svn path=/nixpkgs/trunk/; revision=13160
2008-10-30 14:00:50 +01:00
inherit browser;
Add GNU IceCat 3, GNU's free variant of Mozilla Firefox 3. Currently, MPlayerPlugin can't be built with IceCat 3. svn path=/nixpkgs/trunk/; revision=12437
2008-07-28 17:55:11 +02:00
inherit fetchurl stdenv pkgconfig gettext;
inherit (xlibs) libXpm;
# !!! should depend on MPlayer
};
* Browser plugin for MPlayer. svn path=/nixpkgs/trunk/; revision=498
2003-11-13 14:11:38 +01:00
It is a first try to an expression for MPV video player. It certainly needs a bit of improvement and testing, but it works nicely - so it's a good time to put it to the great public!
2013-12-09 02:25:32 +01:00
mpv = callPackage ../applications/video/mpv {
mpv: minor updates and cleanup E.g. parameterize lua.
2014-04-19 20:16:00 +02:00
lua = lua5_1;
MPV: update to 0.5.0 Many thanks matejc for the commit!
2014-08-11 02:14:41 +02:00
bs2bSupport = config.mpv.bs2bSupport or true;
quviSupport = config.mpv.quviSupport or false;
cacaSupport = config.mpv.cacaSupport or true;
vaapiSupport = config.mpv.vaapiSupport or false;
It is a first try to an expression for MPV video player. It certainly needs a bit of improvement and testing, but it works nicely - so it's a good time to put it to the great public!
2013-12-09 02:25:32 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mrxvt = callPackage ../applications/misc/mrxvt { };
mrxvt terminal emulator supporting bg images added svn path=/nixpkgs/trunk/; revision=9255
2007-09-04 22:06:18 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
multisync = callPackage ../applications/misc/multisync {
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit (gnome) ORBit2 libbonobo libgnomeui GConf;
added multisync - plugins are not yet shown ? svn path=/nixpkgs/trunk/; revision=13539
2008-12-02 13:25:56 +01:00
};
Trying to add mumble. It still does not build. svn path=/nixpkgs/trunk/; revision=25890
2011-02-10 20:23:27 +01:00
mumble = callPackage ../applications/networking/mumble {
avahi = avahi.override {
all-packages.nix: fixed evaluation error in the 'mumble' attribute svn path=/nixpkgs/trunk/; revision=29364
2011-09-19 22:20:17 +02:00
withLibdnssdCompat = true;
Trying to add mumble. It still does not build. svn path=/nixpkgs/trunk/; revision=25890
2011-02-10 20:23:27 +01:00
};
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
jackSupport = config.mumble.jackSupport or false;
mumble: Small Fixups and add support for disabling speechd This patch adds a collection of changes to clean up the mumble expression as well as add support for disabling the external speech dispatcher from being compiled in.
2014-01-31 02:01:22 +01:00
speechdSupport = config.mumble.speechdSupport or false;
Trying to add mumble. It still does not build. svn path=/nixpkgs/trunk/; revision=25890
2011-02-10 20:23:27 +01:00
};
all-packages.nix: strip trailing whitespace
2013-12-09 16:09:43 +01:00
murmur = callPackage ../applications/networking/mumble/murmur.nix {
Add Build Script for Murmur
2013-11-21 11:22:35 +01:00
avahi = avahi.override {
withLibdnssdCompat = true;
};
murmur: Add ice support and small fixes This patch adds optional ICE support to murmur which is enabled by default. Additionally, it cleans up some of the expression similar to the fixes added the mumble.
2014-01-31 05:34:21 +01:00
iceSupport = config.murmur.iceSupport or true;
Add Build Script for Murmur
2013-11-21 11:22:35 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mutt = callPackage ../applications/networking/mailreaders/mutt { };
* mutt was incorrectly listed under tools, not applications svn path=/nixpkgs/trunk/; revision=9058
2007-08-06 17:09:38 +02:00
Add namecoin cryptocurrency
2014-06-30 02:08:34 +02:00
namecoin = callPackage ../applications/misc/namecoin { };
namecoinqt = callPackage ../applications/misc/namecoin/qt.nix { };
Add pcmanfm-1.2.0
2014-03-01 19:37:39 +01:00
pcmanfm = callPackage ../applications/misc/pcmanfm { };
sup: separate dependencies create separate expressions for gems requiring native extensions to be built: * gpgme * ncursesw_sup * xapian_full_alaveteli
2013-06-12 04:24:04 +02:00
ruby_gpgme = callPackage ../development/libraries/ruby_gpgme {
ruby = ruby19;
hoe = rubyLibs.hoe;
};
ruby_ncursesw_sup = callPackage ../development/libraries/ruby_ncursesw_sup { };
Add Shotcut: A free, open source, cross-platform video editor Includes a patch which has already been applied upstream: mltframework/shotcut#31
2014-07-27 12:50:01 +02:00
shotcut = callPackage ../applications/video/shotcut { mlt = mlt-qt5; };
add smplayer 0.8.5
2013-06-23 11:48:21 +02:00
smplayer = callPackage ../applications/video/smplayer { };
sup: update to latest version
2013-10-13 00:38:52 +02:00
sup = with rubyLibs; callPackage ../applications/networking/mailreaders/sup {
ruby = ruby19.override {
cursesSupport = true;
};
fix eval
2014-08-23 19:28:25 +02:00
inherit gettext highline iconv locale lockfile
text trollop xapian_ruby which;
rmail_sup = ""; # missing
unicode = "";
sup: add missing dependencies * rubygems `locale` and `text` were missing from the sup expression
2013-06-15 13:02:57 +02:00
sup: update to 0.18.0
2014-05-05 02:21:16 +02:00
# See https://github.com/NixOS/nixpkgs/issues/1804 and
# https://github.com/NixOS/nixpkgs/issues/2146
bundler = pkgs.lib.overrideDerivation pkgs.rubyLibs.bundler (
oldAttrs: {
dontPatchShebangs = 1;
}
);
fix eval
2014-08-23 19:28:25 +02:00
chronic = chronic;
sup: update to latest version
2013-10-13 00:38:52 +02:00
gpgme = ruby_gpgme;
fix eval
2014-08-23 19:28:25 +02:00
mime_types = mime_types;
sup: separate dependencies create separate expressions for gems requiring native extensions to be built: * gpgme * ncursesw_sup * xapian_full_alaveteli
2013-06-12 04:24:04 +02:00
ncursesw_sup = ruby_ncursesw_sup;
fix eval
2014-08-23 19:28:25 +02:00
rake = rake;
Add sup expression
2013-05-26 10:07:28 +02:00
};
synfigstudio: fix chroot build / hydra The error message was: Fontconfig error: Cannot load default config file make[2]: *** [128x128/synfig_icon.png] Segmentation fault (cherry picked from commit 759980c4fe9b07932f671d2e657189068d117405) Conflicts: pkgs/top-level/all-packages.nix
2014-08-25 22:58:22 +02:00
synfigstudio = callPackage ../applications/graphics/synfigstudio {
fontsConf = makeFontsConf { fontDirectories = [ freefont_ttf ]; };
};
all-packages.nix: strip trailing whitespace
2014-08-20 11:57:56 +02:00
Add the bspwm window manager to Nix.
2014-08-09 23:31:05 +02:00
sxhkd = callPackage ../applications/window-managers/sxhkd { };
Add synfig: A 2D animation program
2014-03-13 01:14:05 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
msmtp = callPackage ../applications/networking/msmtp { };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
all-packages.nix: drop trailing whitespace
2013-06-06 10:48:49 +02:00
imapfilter = callPackage ../applications/networking/mailreaders/imapfilter.nix {
Added imapfilter
2013-05-31 20:18:42 +02:00
lua = lua5;
};
Remove a bunch of unreferenced files Plus a small number of obsolete packages (like old versions of qemu).
2012-11-29 13:43:37 +01:00
mupdf = callPackage ../applications/misc/mupdf { };
Adding 'mupdf', a lightweight PDF 1.7 viewer As a side effect, I add openjpeg and jbig2dec. svn path=/nixpkgs/trunk/; revision=23069
2010-08-09 22:59:38 +02:00
Add MyPaint: A graphics application for digital painters
2013-03-06 23:08:30 +01:00
mypaint = callPackage ../applications/graphics/mypaint { };
State qt version (3/4) in packages, not in all-packages.nix svn path=/nixpkgs/trunk/; revision=31406
2012-01-07 18:06:49 +01:00
mythtv = callPackage ../applications/video/mythtv { };
* Added Xine. svn path=/nixpkgs/trunk/; revision=1850
2004-12-11 00:16:23 +01:00
tvtime is now on nixos, thanks to the patches taken from the portage team! svn path=/nixpkgs/trunk/; revision=32962
2012-03-09 19:21:10 +01:00
tvtime = callPackage ../applications/video/tvtime {
kernel = linux;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nano = callPackage ../applications/editors/nano { };
add xawtv here svn path=/nixpkgs/trunk/; revision=4579
2006-01-20 12:30:24 +01:00
nanoblogger: adding version 3.5-rc1
2014-08-30 09:14:19 +02:00
nanoblogger = callPackage ../applications/misc/nanoblogger { };
Remove a bunch of unreferenced files Plus a small number of obsolete packages (like old versions of qemu).
2012-11-29 13:43:37 +01:00
navipowm = callPackage ../applications/misc/navipowm { };
Adding NaviPOWM (I don't know how to use it though) svn path=/nixpkgs/trunk/; revision=23348
2010-08-22 14:04:03 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
navit = callPackage ../applications/misc/navit { };
Adding 'navit' (it still does not build because it wants to download maps) svn path=/nixpkgs/trunk/; revision=23346
2010-08-22 13:33:57 +02:00
Added package for netbeans IDE
2012-10-09 11:40:06 +02:00
netbeans = callPackage ../applications/editors/netbeans { };
ncdu: New package, starting at version 1.8. `ncdu` is a little ncurses tool to browse the filesystem tree sorted by disk usage.
2012-08-22 09:59:01 +02:00
ncdu = callPackage ../tools/misc/ncdu { };
ncdc: initial expression http://dev.yorhel.nl/ncdc
2014-03-23 02:21:24 +01:00
ncdc = callPackage ../applications/networking/p2p/ncdc { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
nedit = callPackage ../applications/editors/nedit {
Remove a bunch of unreferenced files Plus a small number of obsolete packages (like old versions of qemu).
2012-11-29 13:43:37 +01:00
motif = lesstif;
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
};
* Added `zapping', a TV viewer application. It depends on Gnome, so lots of packages are needed. svn path=/nixpkgs/trunk/; revision=681
2004-01-21 10:34:19 +01:00
adding netsurf browser. No JavaScript yet svn path=/nixpkgs/trunk/; revision=17077
2009-09-13 10:54:47 +02:00
netsurfBrowser = netsurf.browser;
finally fixing netsurf svn path=/nixpkgs/trunk/; revision=17328
2009-09-21 12:09:20 +02:00
netsurf = recurseIntoAttrs (import ../applications/networking/browsers/netsurf { inherit pkgs; });
adding netsurf browser. No JavaScript yet svn path=/nixpkgs/trunk/; revision=17077
2009-09-13 10:54:47 +02:00
notmuch as emacsPackage and top-level without emacs support svn path=/nixpkgs/trunk/; revision=31768
2012-01-21 19:29:14 +01:00
notmuch = callPackage ../applications/networking/mailreaders/notmuch {
Remove a bunch of unreferenced files Plus a small number of obsolete packages (like old versions of qemu).
2012-11-29 13:43:37 +01:00
# use emacsPackages.notmuch if you want emacs support
emacs = null;
notmuch as emacsPackage and top-level without emacs support svn path=/nixpkgs/trunk/; revision=31768
2012-01-21 19:29:14 +01:00
};
notmuch -- The mail indexer configure fails so far: Checking for Xapian development files... Yes (1.0.23). Checking for GMime development files... No. Checking for talloc development files... No. Checking for valgrind development files... No (but that's fine). Checking if emacs is available... Yes. svn path=/nixpkgs/trunk/; revision=25930
2011-02-13 02:34:49 +01:00
* openstack-compute -> nova (upstream doesn't know what to call it either). svn path=/nixpkgs/branches/modular-python/; revision=26610
2011-03-30 17:00:53 +02:00
nova = callPackage ../applications/virtualization/nova { };
* Added novaclient. svn path=/nixpkgs/trunk/; revision=27407
2011-06-09 17:06:21 +02:00
novaclient = callPackage ../applications/virtualization/nova/client.nix { };
Add nspluginwrapper, a tool to execute browser plugins out-of-process
2012-11-08 08:38:34 +01:00
nspluginwrapper = callPackage ../applications/networking/browsers/mozilla-plugins/nspluginwrapper {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
nvi = callPackage ../applications/editors/nvi { };
Adding nvi, another small vi clone. svn path=/nixpkgs/trunk/; revision=15099
2009-04-16 21:28:57 +02:00
Add nvpy, a Simplenote syncing note-taking application
2013-07-13 01:09:53 +02:00
nvpy = callPackage ../applications/editors/nvpy { };
obconf: Added obconf - A gui configuration tool for openbox
2014-08-08 00:58:18 +02:00
obconf = callPackage ../tools/X11/obconf {
inherit (gnome) libglade;
};
Add GNU Ocrad. svn path=/nixpkgs/trunk/; revision=25572
2011-01-14 22:44:43 +01:00
ocrad = callPackage ../applications/graphics/ocrad { };
Adding offrss svn path=/nixpkgs/trunk/; revision=25672
2011-01-23 17:40:25 +01:00
offrss = callPackage ../applications/networking/offrss { };
ogmtools: new package
2012-06-28 11:38:49 +02:00
ogmtools = callPackage ../applications/video/ogmtools { };
Remove gcc 4.7 There is really no reason to keep it around, given that it was never the default in Nixpkgs.
2014-01-07 10:36:15 +01:00
omxplayer = callPackage ../applications/video/omxplayer { };
Making omxplayer build with gcc47
2013-03-29 21:49:31 +01:00
Adding OneTeam XMPP client svn path=/nixpkgs/trunk/; revision=27553
2011-06-28 11:45:09 +02:00
oneteam = callPackage ../applications/networking/instant-messengers/oneteam {};
openbox: packaged. Patch by rixed@happyleptic.org. svn path=/nixpkgs/trunk/; revision=24902
2010-11-28 11:07:49 +01:00
openbox = callPackage ../applications/window-managers/openbox { };
Rename oiio to openimageio (more explicit) and add opencolorio
2013-03-28 00:47:47 +01:00
openimageio = callPackage ../applications/graphics/openimageio { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
openjump = callPackage ../applications/misc/openjump { };
adding GIS application OpenJUMP svn path=/nixpkgs/trunk/; revision=21735
2010-05-12 00:19:37 +02:00
Adding OpenSCAD - a 3D geometry interpreter svn path=/nixpkgs/trunk/; revision=31869
2012-01-26 20:01:38 +01:00
openscad = callPackage ../applications/graphics/openscad {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
opera = callPackage ../applications/networking/browsers/opera {
synchronize with trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=29531
2011-09-28 21:26:00 +02:00
inherit (pkgs.kde4) kdelibs;
Tried to add kuickshow (a pretty fast image viewer that used to be distributed by default in KDE). Unfortunately it doesn't work, because of some strange problems with mime types. But well, it compiles. The libraries are useful anyway: - arts (kde) - imlib (gnome) - libungif (aka libgif) svn path=/nixpkgs/trunk/; revision=6111
2006-08-13 11:46:54 +02:00
};
opusfile: new package
2013-12-07 20:09:08 +01:00
opusfile = callPackage ../applications/audio/opusfile { };
Adding opus-tools. At least a program that uses libopus.
2012-09-25 20:08:01 +02:00
opusTools = callPackage ../applications/audio/opus-tools { };
Adding pamixer.
2014-04-18 16:09:34 +02:00
pamixer = callPackage ../applications/audio/pamixer { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pan = callPackage ../applications/networking/newsreaders/pan {
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
spellChecking = false;
Added libraries: - gtkmm: C++ bindings for gtk - glibmm: C++ bindings for glib - libsigc++ (C++) Added applications: - Batik: SVG rasterizer (and more) - Inkscape: vector graphics drawing application Upgraded: - boehm-gc svn path=/nixpkgs/trunk/; revision=3792
2005-09-07 16:57:30 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
panotools = callPackage ../applications/graphics/panotools { };
all-packages.nix: commented out package 'vice' error: getting status of `/usr/local/src/nix-pkgs-current/pkgs/misc/emulators/vice': No such file or directory svn path=/nixpkgs/trunk/; revision=15646
2009-05-18 15:53:01 +02:00
pavucontrol 2.0
2013-07-27 17:43:17 +02:00
pavucontrol = callPackage ../applications/audio/pavucontrol { };
Add Pavucontrol (untested). svn path=/nixpkgs/branches/stdenv-updates/; revision=14864
2009-04-03 17:58:18 +02:00
Drop soqt and paraview/Qt-4.7 Hydra built these packages with qt-4.8. svn path=/nixpkgs/trunk/; revision=32474
2012-02-22 16:02:21 +01:00
paraview = callPackage ../applications/graphics/paraview { };
Let hydra build paraview with qt-4.7 and qt-4.8 svn path=/nixpkgs/trunk/; revision=32452
2012-02-21 13:57:23 +01:00
pencil: new package Pencil is a GUI prototyping/mockup tool. Homepage: http://pencil.evolus.vn/
2013-11-30 16:27:42 +01:00
pencil = callPackage ../applications/graphics/pencil { };
Adding Petri-Foo, a fork of the Specimen sampler project svn path=/nixpkgs/trunk/; revision=33395
2012-03-24 14:22:14 +01:00
petrifoo = callPackage ../applications/audio/petrifoo {
inherit (gnome) libgnomecanvas;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pdftk = callPackage ../tools/typesetting/pdftk { };
pdfgrep: added a nice util to search in pdf files
2014-08-13 20:03:04 +02:00
pdfgrep = callPackage ../tools/typesetting/pdfgrep { };
Adding pdftk for roconnor. svn path=/nixpkgs/trunk/; revision=22097
2010-06-02 10:21:49 +02:00
Add pianobar, a command-line Pandora client
2013-06-08 03:50:41 +02:00
pianobar = callPackage ../applications/audio/pianobar { };
Adding Piano Booster, a MIDI file player that teaches you how to play the piano. svn path=/nixpkgs/trunk/; revision=33880
2012-04-22 18:55:12 +02:00
pianobooster = callPackage ../applications/audio/pianobooster { };
picard: New package, version 1.1. Picard is the official MusicBrainz audio tagger which is able to use audio fingerprinting to tag your files. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-09-05 01:15:23 +02:00
picard = callPackage ../applications/audio/picard { };
picocom: adding picocom, 1.7
2012-09-24 00:26:46 +02:00
picocom = callPackage ../tools/misc/picocom { };
pidgin 2.9.0 svn path=/nixpkgs/trunk/; revision=28425
2011-08-09 14:35:55 +02:00
pidgin = callPackage ../applications/networking/instant-messengers/pidgin {
Remove unnecessary parentheses around if conditions Pet peeve...
2012-12-28 19:54:15 +01:00
openssl = if config.pidgin.openssl or true then openssl else null;
gnutls = if config.pidgin.gnutls or false then gnutls else null;
libgcrypt = if config.pidgin.gnutls or false then libgcrypt else null;
pidgin: minor update 2.10.7 -> .8, including CVE-2013-6484 Also switch no newer libstartup-notification, add license and platforms.
2014-02-01 08:43:33 +01:00
startupnotification = libstartup_notification;
moved pidgin near packages starting with p (was near f maybe because pidgin was called gaim?) svn path=/nixpkgs/trunk/; revision=11724
2008-04-26 01:40:18 +02:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pidginlatex = callPackage ../applications/networking/instant-messengers/pidgin-plugins/pidgin-latex {
moved pidgin near packages starting with p (was near f maybe because pidgin was called gaim?) svn path=/nixpkgs/trunk/; revision=11724
2008-04-26 01:40:18 +02:00
imagemagick = imagemagickBig;
};
Fixed Python StringTemplate library. Most importantly, this change required updating the ANTLR 2.x expression to install the Python run-time library. While we're at it, we're building the run-time library for C++ and Java, too. There is still work to be done: the stringtemplate library doesn't find antlr.py without help yet. svn path=/nixpkgs/trunk/; revision=14489
2009-03-10 13:01:22 +01:00
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
pidginlatexSF = builderDefsPackage
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
(import ../applications/networking/instant-messengers/pidgin-plugins/pidgin-latex/pidgin-latex-sf.nix)
moved pidgin near packages starting with p (was near f maybe because pidgin was called gaim?) svn path=/nixpkgs/trunk/; revision=11724
2008-04-26 01:40:18 +02:00
{
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit pkgconfig pidgin texLive imagemagick which glib gtk;
moved pidgin near packages starting with p (was near f maybe because pidgin was called gaim?) svn path=/nixpkgs/trunk/; revision=11724
2008-04-26 01:40:18 +02:00
};
msn-pecan: an alternative MSN plugin for pidgin svn path=/nixpkgs/trunk/; revision=23050
2010-08-09 08:51:34 +02:00
pidginmsnpecan = callPackage ../applications/networking/instant-messengers/pidgin-plugins/msn-pecan { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pidginotr = callPackage ../applications/networking/instant-messengers/pidgin-plugins/otr { };
moved pidgin near packages starting with p (was near f maybe because pidgin was called gaim?) svn path=/nixpkgs/trunk/; revision=11724
2008-04-26 01:40:18 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pidginsipe = callPackage ../applications/networking/instant-messengers/pidgin-plugins/sipe { };
pidgin plugin sipe contributed by David Brown svn path=/nixpkgs/trunk/; revision=21730
2010-05-11 19:28:54 +02:00
Adding tox-prpl, a pidgin plugin for tox. I use the current master, because the release 0.2.0 doesn't match the libtoxcore expression.
2013-10-12 15:32:09 +02:00
toxprpl = callPackage ../applications/networking/instant-messengers/pidgin-plugins/tox-prpl { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pinfo = callPackage ../applications/misc/pinfo { };
Added libraries: - gtkmm: C++ bindings for gtk - glibmm: C++ bindings for glib - libsigc++ (C++) Added applications: - Batik: SVG rasterizer (and more) - Inkscape: vector graphics drawing application Upgraded: - boehm-gc svn path=/nixpkgs/trunk/; revision=3792
2005-09-07 16:57:30 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
pinta = callPackage ../applications/graphics/pinta {
Attempt at adding 'pinta'. It still does not build due to mono problems. Nevertheless, I updated the gnome attribute names a bit so all that gtk-sharp-2 goes a bit beyond. svn path=/nixpkgs/trunk/; revision=22287
2010-06-16 00:25:38 +02:00
gtksharp = gtksharp2;
};
Add a module for the pommed tool for Apple laptop keyboards. svn path=/nixpkgs/trunk/; revision=33286
2012-03-20 05:41:13 +01:00
pommed = callPackage ../os-specific/linux/pommed {
inherit (xorg) libXpm;
};
Add potrace-1.11, a tool for tracing bitmaps
2014-04-26 10:20:37 +02:00
potrace = callPackage ../applications/graphics/potrace {};
add Posterazor (close #2538) @vcunat patched for newer gcc.
2014-05-06 11:38:46 +02:00
posterazor = callPackage ../applications/misc/posterazor { };
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
pqiv = callPackage ../applications/graphics/pqiv { };
* added pqiv image viewer svn path=/nixpkgs/trunk/; revision=11908
2008-05-27 17:05:16 +02:00
qiv: add version 2.2.4
2013-01-11 20:24:20 +01:00
qiv = callPackage ../applications/graphics/qiv { };
Add processing: A language and IDE for electronic arts (cherry picked from commit 0db6387d1c3a8a8f7a9a1e111532d8acd1f794d6)
2014-08-25 23:43:14 +02:00
processing = callPackage ../applications/graphics/processing { inherit (xorg) libXxf86vm; };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
# perhaps there are better apps for this task? It's how I had configured my preivous system.
# And I don't want to rewrite all rules
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
procmail = callPackage ../applications/misc/procmail { };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pstree = callPackage ../applications/misc/pstree { };
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
pulseview: new package PulseView is a Qt-based LA/scope/MSO GUI for sigrok (a signal analysis software suite). http://sigrok.org/
2014-05-31 15:37:27 +02:00
pulseview = callPackage ../applications/science/electronics/pulseview { };
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
puredata = callPackage ../applications/audio/puredata { };
Adding vanilla puredata: Real-time graphical programming environment for audio, video, and graphical processing svn path=/nixpkgs/trunk/; revision=26744
2011-04-07 22:54:33 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pythonmagick = callPackage ../applications/graphics/PythonMagick { };
add PythonMagic svn path=/nixpkgs/trunk/; revision=9086
2007-08-09 21:58:39 +02:00
Adding qbittorrent
2013-11-08 09:59:28 +01:00
qbittorrent = callPackage ../applications/networking/p2p/qbittorrent { };
Add eiskaltdcpp, a p2p client for the DC protocol
2014-06-22 16:28:37 +02:00
eiskaltdcpp = callPackage ../applications/networking/p2p/eiskaltdcpp { };
qemu-1.3.1 Also, old qemu is unreferenced in nixos and nixpkgs tree, so remove it absent explicit need.
2013-02-08 02:44:02 +01:00
qemu = callPackage ../applications/virtualization/qemu { };
Adding qemu 1.0.1. svn path=/nixpkgs/trunk/; revision=33232
2012-03-18 11:31:15 +01:00
qmmp: new package Qmmp is a Qt-based audio player that look like Winamp.
2013-05-19 13:18:37 +02:00
qmmp = callPackage ../applications/audio/qmmp { };
Adding qsampler, the frontend for LinuxSampler svn path=/nixpkgs/trunk/; revision=33867
2012-04-21 00:44:50 +02:00
qsampler = callPackage ../applications/audio/qsampler { };
Adding Qsynth (GUI) and fluidsynth (CLI), Soundfont2 based synthesizer svn path=/nixpkgs/trunk/; revision=33504
2012-03-31 22:22:19 +02:00
qsynth = callPackage ../applications/audio/qsynth { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
qtpfsgui = callPackage ../applications/graphics/qtpfsgui { };
Adding qtpfsgui and pfstools. Updating fftw because the src URL didn't work anymore. svn path=/nixpkgs/trunk/; revision=14892
2009-04-05 23:41:13 +02:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
qtractor = callPackage ../applications/audio/qtractor { };
Adding Qtractor, an Audio/MIDI multi-track sequencer svn path=/nixpkgs/trunk/; revision=26949
2011-04-24 16:32:55 +02:00
Add quodlibet-2.5: GTK+Python based music player (close #481)
2013-04-18 01:44:12 +02:00
quodlibet = callPackage ../applications/audio/quodlibet {
inherit (pythonPackages) mutagen;
};
quodlibet: update to version 2.6.3 also provides two distinctive flavours, which either wrap the program to pull in the gstreamer plugins or not.
2013-10-29 11:33:46 +01:00
quodlibet-with-gst-plugins = callPackage ../applications/audio/quodlibet {
inherit (pythonPackages) mutagen;
withGstPlugins = true;
gst_plugins_bad = null;
};
all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=27648
2011-07-07 23:32:55 +02:00
rakarrack = callPackage ../applications/audio/rakarrack {
Adding Rakarrack: guitar effects-pedal emulator svn path=/nixpkgs/trunk/; revision=26955
2011-04-24 21:44:36 +02:00
inherit (xorg) libXpm libXft;
fltk-1.3.0 svn path=/nixpkgs/trunk/; revision=31223
2012-01-03 11:02:33 +01:00
fltk = fltk13;
Adding Rakarrack: guitar effects-pedal emulator svn path=/nixpkgs/trunk/; revision=26955
2011-04-24 21:44:36 +02:00
};
Fix typo
2012-08-27 13:49:33 +02:00
rapcad = callPackage ../applications/graphics/rapcad {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rapidsvn = callPackage ../applications/version-management/rapidsvn { };
Adding rapidsvn svn path=/nixpkgs/trunk/; revision=20538
2010-03-10 21:44:40 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ratpoison = callPackage ../applications/window-managers/ratpoison { };
Added ratpoison; commented out ext3cow - there is no working version for 2.6.22.1 svn path=/nixpkgs/trunk/; revision=9040
2007-08-04 00:38:36 +02:00
rawtherapee-4.0.10 . Add a 'float' option to fftw, as this version of rawtherapee requires it.
2013-04-01 06:33:21 +02:00
rawtherapee = callPackage ../applications/graphics/rawtherapee {
fftw: minor update and major refactoring - Unify the "single" and "float" variants, which are the same thing. - Enable threads and openmp wrapper by default (they are very small). - Don't use sse on i686, as I'm quite sure we have no warrant for that. Cf. http://en.wikipedia.org/wiki/Pentium_Pro - Disable static libs (big, no indication we need them). - I tested most builds using fftw (they build OK).
2014-01-01 11:51:56 +01:00
fftw = fftwSinglePrec;
rawtherapee-4.0.10 . Add a 'float' option to fftw, as this version of rawtherapee requires it.
2013-04-01 06:33:21 +02:00
};
Adding rawtherapee svn r25 svn path=/nixpkgs/trunk/; revision=19500
2010-01-17 18:49:35 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rcs = callPackage ../applications/version-management/rcs { };
* Added libexif and the exif frontend utility. svn path=/nixpkgs/trunk/; revision=2376
2005-03-11 11:46:20 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rdesktop = callPackage ../applications/networking/remote/rdesktop { };
* added rdesktop svn path=/nixpkgs/trunk/; revision=10304
2008-01-28 13:28:23 +01:00
pkgs/tools/text/recode: added (heavily patched) version 3.6 svn path=/nixpkgs/trunk/; revision=24384
2010-10-20 15:05:49 +02:00
recode = callPackage ../tools/text/recode { };
Adding a still broken restroshare expression. I'll develop further later. svn path=/nixpkgs/trunk/; revision=27540
2011-06-26 19:57:28 +02:00
retroshare = callPackage ../applications/networking/p2p/retroshare {
qt = qt4;
};
Setting retroshare 0.6 as lowPrio, it's unstable.
2014-07-31 10:13:20 +02:00
retroshare06 = lowPrio (callPackage ../applications/networking/p2p/retroshare/0.6.nix {
Adding retroshare 0.6 (unstable)
2014-07-09 22:21:45 +02:00
qt = qt4;
Setting retroshare 0.6 as lowPrio, it's unstable.
2014-07-31 10:13:20 +02:00
});
Adding retroshare 0.6 (unstable)
2014-07-09 22:21:45 +02:00
* Fix breakage in r22897. svn path=/nixpkgs/trunk/; revision=22901
2010-08-02 19:59:19 +02:00
rsync = callPackage ../applications/networking/sync/rsync {
rsync: fix build an FreeBSD (by disabling ACL support)
2013-03-25 12:36:32 +01:00
enableACLs = !(stdenv.isDarwin || stdenv.isSunOS || stdenv.isFreeBSD);
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
enableCopyDevicesPatch = (config.rsync.enableCopyDevicesPatch or false);
* Added TestDisk, a program for fixing unbootable disks. svn path=/nixpkgs/trunk/; revision=9318
2007-09-12 17:49:28 +02:00
};
sbagen (binaural sound generator) added svn path=/nixpkgs/trunk/; revision=9317
2007-09-12 12:56:56 +02:00
rtl-sdr: new package rtl-sdr turns your Realtek RTL2832 based DVB dongle into a SDR receiver. http://sdr.osmocom.org/trac/wiki/rtl-sdr
2014-03-08 00:42:42 +01:00
rtl-sdr = callPackage ../applications/misc/rtl-sdr { };
rubyripper: New expression Adds minimal support for being able to run rrip_cli
2013-09-25 14:05:54 +02:00
rubyripper = callPackage ../applications/audio/rubyripper {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rxvt = callPackage ../applications/misc/rxvt { };
sbagen (binaural sound generator) added svn path=/nixpkgs/trunk/; revision=9317
2007-09-12 12:56:56 +02:00
rxvt-unicode and jdk update provided by Tobias Hammerschmidt svn path=/nixpkgs/trunk/; revision=9561
2007-10-31 13:17:14 +01:00
# = urxvt
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
rxvt_unicode = callPackage ../applications/misc/rxvt_unicode {
Added rxvt_unicode_with_perl
2013-05-31 20:21:24 +02:00
perlSupport = true;
urxvt: Enable Gdk_pixbuf to be able to set custom icons/images
2013-07-26 15:03:18 +02:00
gdkPixbufSupport = true;
Add unicode3 option to rxvt_unicode Needed to user fonts patched for powerline.
2014-05-22 23:13:25 +02:00
unicode3Support = true;
* Added the Google Talk plugin. Doesn't work yet (says ‘ABORT: X_GLXCreateContext: BadValue’). svn path=/nixpkgs/trunk/; revision=27825
2011-07-18 16:44:28 +02:00
};
rxvt-unicode and jdk update provided by Tobias Hammerschmidt svn path=/nixpkgs/trunk/; revision=9561
2007-10-31 13:17:14 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
sakura = callPackage ../applications/misc/sakura {
applications/misc/sakura: New nixpkg. svn path=/nixpkgs/trunk/; revision=20152
2010-02-21 12:36:49 +01:00
inherit (gnome) vte;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sbagen = callPackage ../applications/misc/sbagen { };
sbagen (binaural sound generator) added svn path=/nixpkgs/trunk/; revision=9317
2007-09-12 12:56:56 +02:00
Added SciTE 3.3.7.
2014-01-23 10:35:02 +01:00
scite = callPackage ../applications/editors/scite { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
scribus = callPackage ../applications/office/scribus {
adding scribus - don't miss the comment about fonts! svn path=/nixpkgs/trunk/; revision=17866
2009-10-18 06:44:01 +02:00
inherit (gnome) libart_lgpl;
};
Dashify seafileShared and seafileClient
2014-02-05 18:25:43 +01:00
seafile-client = callPackage ../applications/networking/seafile-client { };
Add packages for libzdb, libsearpc, ccnet, seafile-shared, and seafile-client
2014-02-04 20:02:46 +01:00
Seeks 0.4.0. svn path=/nixpkgs/trunk/; revision=30729
2011-12-04 23:03:03 +01:00
seeks = callPackage ../tools/networking/p2p/seeks {
opencv = opencv_2_1;
};
Add Seeks, a "social" search engine. svn path=/nixpkgs/trunk/; revision=22698
2010-07-22 11:03:35 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
seg3d = callPackage ../applications/graphics/seg3d {
* Added the Google Talk plugin. Doesn't work yet (says ‘ABORT: X_GLXCreateContext: BadValue’). svn path=/nixpkgs/trunk/; revision=27825
2011-07-18 16:44:28 +02:00
wxGTK = wxGTK28.override { unicode = false; };
Adding the itk libraries. Adding a skeleton of the seg3d package. It builds, but libraries and rpaths are wrong. I hope to fix it soon. svn path=/nixpkgs/trunk/; revision=20320
2010-03-02 00:31:35 +01:00
};
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
seq24 = callPackage ../applications/audio/seq24 { };
Adding seq24: a minimal loop based midi sequencer svn path=/nixpkgs/trunk/; revision=26924
2011-04-23 00:07:59 +02:00
Add setBfree a DSP tonewheel organ emulator
2014-05-05 22:57:48 +02:00
setbfree = callPackage ../applications/audio/setbfree { };
Making sflphone build, and its gnome client too.
2013-06-27 00:09:26 +02:00
sflphone = callPackage ../applications/networking/instant-messengers/sflphone {
gtk = gtk3;
};
Adding partially sflphone (only daemon, maybe failing to build)
2013-06-26 23:48:55 +02:00
Adding siproxd svn path=/nixpkgs/trunk/; revision=25584
2011-01-16 12:41:19 +01:00
siproxd = callPackage ../applications/networking/siproxd { };
skype: 4.2.0.13 -> 4.3.0.37
2014-06-23 17:56:35 +02:00
skype = callPackage_i686 ../applications/networking/instant-messengers/skype { };
rxvt added svn path=/nixpkgs/trunk/; revision=9256
2007-09-05 10:25:23 +02:00
Adding skype4pidgin. It crashes.
2013-04-16 14:42:54 +02:00
skype4pidgin = callPackage ../applications/networking/instant-messengers/pidgin-plugins/skype4pidgin { };
Adding Skype Call Recorder.
2013-04-05 16:02:16 +02:00
skype_call_recorder = callPackage ../applications/networking/instant-messengers/skype-call-recorder { };
Started default.nix for slrn. Not finding slang
2014-03-21 19:07:56 +01:00
slrn = callPackage ../applications/networking/newsreaders/slrn { };
Add SpiderOak secure backup service.
2014-07-18 22:21:48 +02:00
spideroak = callPackage ../applications/networking/spideroak { };
ssvnc: The Enhanced TightVNC Viewer, SSVNC, adds encryption security to VNC connections. Close #950.
2013-09-09 21:13:10 +02:00
ssvnc = callPackage ../applications/networking/remote/ssvnc { };
st: Update to 0.4.1 and add support for custom config
2013-05-10 16:31:13 +02:00
st = callPackage ../applications/misc/st {
conf = config.st.conf or null;
};
Adding 'st-0.2.1'
2012-08-05 12:44:01 +02:00
Stella 4.0: New Package Stella is an Atari 2600 VCS emulator
2014-08-31 19:25:39 +02:00
stella = callPackage ../misc/emulators/stella { };
linuxstopmotion: new package Linux Stopmotion is a program for creating stop-motion animation movies. http://linuxstopmotion.org/ I had to apply a small patch to make grabbing images from webcam work (using uvccapture). I find it odd that it didn't work without the patch, seeing that Arch Linux also have the v0.8.0 version, but with no patch. Latest Ubuntu (14.04) has v0.7.2, which is unaffected.
2014-08-17 22:58:02 +02:00
linuxstopmotion = callPackage ../applications/video/linuxstopmotion { };
Adding SweetHome3D, TexturesLibraryEditor, FurnitureLibraryEditor
2014-04-15 14:12:44 +02:00
sweethome3d = recurseIntoAttrs ( (callPackage ../applications/misc/sweethome3d { })
// (callPackage ../applications/misc/sweethome3d/editors.nix {
sweethome3dApp = sweethome3d.application;
})
);
add sxiv-1.1
2013-05-24 10:21:34 +02:00
sxiv = callPackage ../applications/graphics/sxiv { };
Adding 'st-0.2.1'
2012-08-05 12:44:01 +02:00
add bittorrent sync
2013-04-27 18:43:43 +02:00
bittorrentSync = callPackage ../applications/networking/bittorrentsync { };
Copy.com: client #3617
2014-09-03 08:39:48 +02:00
copy-com = callPackage ../applications/networking/copy-com { };
Added dropbox (binary). svn path=/nixpkgs/trunk/; revision=32545
2012-02-24 18:53:19 +01:00
dropbox = callPackage ../applications/networking/dropbox { };
New package: dropbox-cli dropbox-cli, part of dropbox-nautilus is a small self-contained python script to control the dropbox daemon. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-03-27 20:12:49 +01:00
dropbox-cli = callPackage ../applications/networking/dropbox-cli { };
lightdm: Add lightdm and lightdm-gtk-greeter
2013-03-26 11:42:18 +01:00
lightdm = callPackage ../applications/display-managers/lightdm { };
lightdm_gtk_greeter = callPackage ../applications/display-managers/lightdm-gtk-greeter { };
slic3r: new package Slic3r is a G-code generator for 3D printers. - Math-Clipper and Boost-Geometry-Utils have been bumped to satisfy Slic3r. - Slic3r has problems with perl 5.16 due to a locale issue (comma vs period in floating point numbers). So we use perl 5.14. - The tests fail, so we skip them. According to the author of Slic3r, that should be safe: "Tests failed because of a typo when the 0.9.10b tag was applied. You can safely ignore the test results, Slic3r will work." See https://github.com/alexrj/Slic3r/issues/1303 For reference, the errors look like this: Use of uninitialized value $deg in numeric eq (==) at /tmp/nix-build-perl-slic3r-0.9.10b.drv-0/git-export/t/../lib/Slic3r/TriangleMesh.pm line 328. # Looks like your test exited with 255 before it could output anything.
2013-04-28 12:59:00 +02:00
# slic3r 0.9.10b says: "Running Slic3r under Perl >= 5.16 is not supported nor recommended"
slic3r = callPackage ../applications/misc/slic3r {
Slic3r: Bump to 1.1.7.
2014-08-20 16:27:47 +02:00
perlPackages = perl514Packages;
slic3r: new package Slic3r is a G-code generator for 3D printers. - Math-Clipper and Boost-Geometry-Utils have been bumped to satisfy Slic3r. - Slic3r has problems with perl 5.16 due to a locale issue (comma vs period in floating point numbers). So we use perl 5.14. - The tests fail, so we skip them. According to the author of Slic3r, that should be safe: "Tests failed because of a typo when the 0.9.10b tag was applied. You can safely ignore the test results, Slic3r will work." See https://github.com/alexrj/Slic3r/issues/1303 For reference, the errors look like this: Use of uninitialized value $deg in numeric eq (==) at /tmp/nix-build-perl-slic3r-0.9.10b.drv-0/git-export/t/../lib/Slic3r/TriangleMesh.pm line 328. # Looks like your test exited with 255 before it could output anything.
2013-04-28 12:59:00 +02:00
perl = perl514;
};
Add Cura.
2014-03-25 23:17:17 +01:00
curaengine = callPackage ../applications/misc/curaengine { };
cura = callPackage ../applications/misc/cura { };
Add Printrun.
2014-03-29 23:03:35 +01:00
printrun = callPackage ../applications/misc/printrun { };
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
slim = callPackage ../applications/display-managers/slim {
libpng = libpng12;
};
* SLiM, a lightweight display manager. svn path=/nixpkgs/trunk/; revision=8044
2007-02-25 23:25:25 +01:00
fftw: minor update and major refactoring - Unify the "single" and "float" variants, which are the same thing. - Enable threads and openmp wrapper by default (they are very small). - Don't use sse on i686, as I'm quite sure we have no warrant for that. Cf. http://en.wikipedia.org/wiki/Pentium_Pro - Disable static libs (big, no indication we need them). - I tested most builds using fftw (they build OK).
2014-01-01 11:51:56 +01:00
smartdeblur = callPackage ../applications/graphics/smartdeblur { };
Adding smartdeblur (gpl3 version, ~1.27)
2013-11-12 22:11:47 +01:00
snd: update to 14.3
2014-01-09 08:24:11 +01:00
snd = callPackage ../applications/audio/snd { };
Added Snd sound editor svn path=/nixpkgs/trunk/; revision=9573
2007-11-03 05:15:13 +01:00
shntool-3.0.10
2013-03-25 06:08:09 +01:00
shntool = callPackage ../applications/audio/shntool { };
Remove unused sonic-visualizer/ subdir, rename. Also move "qt=qt4" to default.nix svn path=/nixpkgs/trunk/; revision=28474
2011-08-11 00:39:53 +02:00
sonic_visualiser = callPackage ../applications/audio/sonic-visualiser {
inherit (pkgs.vamp) vampSDK;
inherit (pkgs.xlibs) libX11;
fftw = pkgs.fftwSinglePrec;
adding sonic visualizer (music analysis app) svn path=/nixpkgs/trunk/; revision=17325
2009-09-21 11:58:36 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
sox = callPackage ../applications/misc/audio/sox { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
audacity: minor update, prefer system-wide libs - Using system-wide libs where we have them (except for portaudio, which I couldn't make work). - Add the soxr library (now the preferred way of audio resampling).
2013-06-04 11:35:33 +02:00
soxr = callPackage ../applications/misc/audio/soxr { };
texinfo: update to version 5.1
2013-03-13 14:07:54 +01:00
spotify = callPackage ../applications/audio/spotify {
Initial try to update spotify to version 0.8.4.103. Still need to get rid of LD_LIBRARY_PATH wrapper, and properly patchelf any libs in the spotify prefix.
2012-07-02 10:46:30 +02:00
inherit (gnome) GConf;
libpng: keep versioning in all-packages.nix, not in individual expressions
2013-06-26 16:48:45 +02:00
libpng = libpng12;
Initial try to update spotify to version 0.8.4.103. Still need to get rid of LD_LIBRARY_PATH wrapper, and properly patchelf any libs in the spotify prefix.
2012-07-02 10:46:30 +02:00
};
* Spotify for Linux (preview version). It works, but not yet out of the box because it requires /usr/share/spotify to point at its resources. So to get it to work, you should do something like: $ nix-env -i spotify $ mkdir -p /usr/share $ ln -s /home/eelco/.nix-profile/share/spotify /usr/share/ Also note that the Linux client doesn't work with free Spotify accounts (as noted on https://www.spotify.com/nl/download/previews/). svn path=/nixpkgs/trunk/; revision=25431
2011-01-06 00:23:22 +01:00
Add libspotify
2013-01-25 07:10:36 +01:00
libspotify = callPackage ../development/libraries/libspotify {
apiKey = config.libspotify.apiKey or null;
};
Add stalonetray svn path=/nixpkgs/trunk/; revision=24595
2010-11-04 09:28:24 +01:00
stalonetray = callPackage ../applications/window-managers/stalonetray {};
STP: Simple Theorem Prover (a SMT solver for bitvectors & arrays).
2014-01-12 13:22:58 +01:00
stp = callPackage ../applications/science/logic/stp {};
Replacing StumpWM with a fresh lisp-packages version
2013-10-13 09:00:18 +02:00
stumpwm = lispPackages.stumpwm;
Added StumpWM svn path=/nixpkgs/trunk/; revision=12566
2008-08-09 22:21:33 +02:00
Add Sublime Text editor
2012-11-10 20:37:42 +01:00
sublime = callPackage ../applications/editors/sublime { };
Fix file name used for libcdio 0.82
2014-02-02 22:35:33 +01:00
Added SublimeText3 support. SublimeText2 and SublimeText3 can be installed side by side. They provide 'sublime', 'sublime2' and 'sublime3' commands. SublimeText3 has lower precedense than SublimeText2 because its in beta mode (for over a year now)
2014-01-25 21:45:08 +01:00
sublime3 = lowPrio (callPackage ../applications/editors/sublime3 { });
Add Sublime Text editor
2012-11-10 20:37:42 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
subversion = callPackage ../applications/version-management/subversion/default.nix {
subversion: dropped support for getConfig -- use override instead! Subversion was one of the last few packages that still supported the obsolete getConfig function. Inside of nixpkgs, we don't rely on that feature; other packages, like git, customize subversion by means of override. So it felt like about time to drop getConfig. svn path=/nixpkgs/trunk/; revision=26823
2011-04-13 19:53:01 +02:00
bdbSupport = true;
httpServer = false;
httpSupport = true;
pythonBindings = false;
perlBindings = false;
javahlBindings = false;
subversion: add sasl support svn path=/nixpkgs/trunk/; revision=31530
2012-01-14 12:41:06 +01:00
saslSupport = false;
* Drop pkgsOverriden. svn path=/nixpkgs/trunk/; revision=22823
2010-07-30 14:10:24 +02:00
httpd = apacheHttpd;
subversion: add sasl support svn path=/nixpkgs/trunk/; revision=31530
2012-01-14 12:41:06 +01:00
sasl = cyrus_sasl;
* Added Subversion 1.5.0. Some features probably don't work yet (building the Apache modules, building various language bindings). * Neon 0.28.2. Also kept Neon 0.26.x because Subversion 1.4.x needs it. svn path=/nixpkgs/trunk/; revision=12162
2008-06-19 17:29:25 +02:00
};
Make appendToName do the right thing I.e. append a suffix *before* the version, rather than after. So we get "sqlite-interactive-3.8.0.2" instead of "sqlite-3.8.0.2-interactive". The latter is broken since nix-env just sees it the suffix as part of the version, so "nix-env -u" will happily upgrade "sqlite-3.8.0.2-interactive" to "sqlite-3.9".
2014-03-10 15:01:56 +01:00
subversionClient = appendToName "client" (subversion.override {
all-packages.nix: added low-priority 'subversionClient' expression subversionClient comes without support for BBDB, but with bindings to Perl and Python. Having these is often desirable, i.e. when building Git with SVN support. svn path=/nixpkgs/trunk/; revision=26825
2011-04-13 19:53:14 +02:00
bdbSupport = false;
perlBindings = true;
pythonBindings = true;
Make appendToName do the right thing I.e. append a suffix *before* the version, rather than after. So we get "sqlite-interactive-3.8.0.2" instead of "sqlite-3.8.0.2-interactive". The latter is broken since nix-env just sees it the suffix as part of the version, so "nix-env -u" will happily upgrade "sqlite-3.8.0.2-interactive" to "sqlite-3.9".
2014-03-10 15:01:56 +01:00
});
all-packages.nix: added low-priority 'subversionClient' expression subversionClient comes without support for BBDB, but with bindings to Perl and Python. Having these is often desirable, i.e. when building Git with SVN support. svn path=/nixpkgs/trunk/; revision=26825
2011-04-13 19:53:14 +02:00
surf: version 0.4.1 svn path=/nixpkgs/trunk/; revision=28496
2011-08-11 18:33:41 +02:00
surf = callPackage ../applications/misc/surf {
get rid of old webkit and webkit_gtk2 packages
2014-03-30 03:02:07 +02:00
webkit = webkitgtk2;
surf: version 0.4.1 svn path=/nixpkgs/trunk/; revision=28496
2011-08-11 18:33:41 +02:00
};
* Drop the "perl" prefix from Perl attribute names. It's redundant now that Perl packages are in their own namespace (perlPackages.<pkg>). svn path=/nixpkgs/trunk/; revision=15176
2009-04-20 14:49:35 +02:00
svk = perlPackages.SVK;
Added SVK. svn path=/nixpkgs/trunk/; revision=11937
2008-05-30 20:15:25 +02:00
Add the LV2 version of the SWH audio plugins (used for audio production)
2012-10-02 01:00:13 +02:00
swh_lv2 = callPackage ../applications/audio/swh-lv2 { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
sylpheed = callPackage ../applications/networking/mailreaders/sylpheed {
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
sslSupport = true;
gpgSupport = true;
add xterm. Untested in NixOS (but will be in 10 minutes) svn path=/nixpkgs/trunk/; revision=4604
2006-01-26 21:45:11 +01:00
};
Add Mark Lord's symlinks utility
2014-07-08 19:19:15 +02:00
symlinks = callPackage ../tools/system/symlinks { };
syncthing: new package and nixos module
2014-04-03 18:54:10 +02:00
syncthing = callPackage ../applications/networking/syncthing { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
# linux only by now
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
synergy = callPackage ../applications/misc/synergy { };
Synergy added and fetchcvs modified (see mailinglist post) svn path=/nixpkgs/trunk/; revision=9624
2007-11-11 09:16:23 +01:00
Adding 'tabbed'. I think Alexander Foremny wanted to send this patch long ago, but I could not find it. svn path=/nixpkgs/trunk/; revision=33414
2012-03-25 22:10:25 +02:00
tabbed = callPackage ../applications/window-managers/tabbed { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
tahoelafs = callPackage ../tools/networking/p2p/tahoe-lafs {
Add Tahoe, a decentralized, fault-tolerant file system. svn path=/nixpkgs/trunk/; revision=16082
2009-06-28 23:03:00 +02:00
inherit (pythonPackages) twisted foolscap simplejson nevow zfec
tahoe-lafs: Upgrade from 1.9.2 -> 1.10.0 Remove patches which do not apply to the newer version.
2014-01-11 00:21:45 +01:00
pycryptopp sqlite3 darcsver setuptoolsTrial setuptoolsDarcs
* Update darcsver and mock. svn path=/nixpkgs/branches/modular-python/; revision=26681
2011-04-04 16:38:53 +02:00
numpy pyasn1 mock;
Add Tahoe, a decentralized, fault-tolerant file system. svn path=/nixpkgs/trunk/; revision=16082
2009-06-28 23:03:00 +02:00
};
Remove multiversion expression for tailor for easier use of custom versions svn path=/nixpkgs/trunk/; revision=15296
2009-04-25 13:19:42 +02:00
tailor = builderDefsPackage (import ../applications/version-management/tailor) {
Upgrade default to python version 2.5.x. svn path=/nixpkgs/trunk/; revision=12910
2008-09-24 10:50:32 +02:00
inherit makeWrapper python;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
all-packages.nix changes; now builderDefsPackage includes .meta.function attribute svn path=/nixpkgs/trunk/; revision=11767
2008-05-07 09:23:20 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
tangogps = callPackage ../applications/misc/tangogps {
Add tangoGPS, a friendly GPS and map user interface. svn path=/nixpkgs/trunk/; revision=15840
2009-06-03 15:52:38 +02:00
gconf = gnome.GConf;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
teamspeak_client = callPackage ../applications/networking/instant-messengers/teamspeak/client.nix { };
Add TeamSpeak 3 server & service module (close #2056) Conflicts (trivial): lib/maintainers.nix nixos/modules/misc/ids.nix
2014-03-29 01:40:30 +01:00
teamspeak_server = callPackage ../applications/networking/instant-messengers/teamspeak/server.nix { };
Unfinished teamspeak client svn path=/nixpkgs/trunk/; revision=9934
2007-12-14 02:50:19 +01:00
kde-3: Remove KDE 3 hasn't built in a long time. Also remove six, the only package with a dependency on KDE 3.
2013-01-29 12:23:34 +01:00
taskjuggler = callPackage ../applications/misc/taskjuggler { };
Add TaskJuggler: A project management tool. svn path=/nixpkgs/trunk/; revision=11933
2008-05-29 21:12:53 +02:00
Adding task warrior, stable. svn path=/nixpkgs/trunk/; revision=31150
2011-12-29 23:14:08 +01:00
taskwarrior = callPackage ../applications/misc/taskwarrior { };
Add taskserver package (close #3269)
2014-07-13 07:09:52 +02:00
taskserver = callPackage ../servers/misc/taskserver { };
added telegram-cli as instant-messenger application
2014-03-04 22:50:01 +01:00
telegram-cli = callPackage ../applications/networking/instant-messengers/telegram-cli/default.nix { };
telepathy-gabble: major update 0.17.2 -> 0.18.2 Also doCheck, enableParallelBuilding, and add meta attributes.
2014-06-19 23:19:22 +02:00
telepathy_gabble = callPackage ../applications/networking/instant-messengers/telepathy/gabble { };
Move telepathy-gabble to applications svn path=/nixpkgs/trunk/; revision=33064
2012-03-14 16:41:37 +01:00
Mass telepathy update, add telepathy-haze svn path=/nixpkgs/trunk/; revision=34494
2012-06-13 09:09:19 +02:00
telepathy_haze = callPackage ../applications/networking/instant-messengers/telepathy/haze {};
Add telepathy-logger svn path=/nixpkgs/trunk/; revision=33457
2012-03-28 21:23:42 +02:00
telepathy_logger = callPackage ../applications/networking/instant-messengers/telepathy/logger {};
Add telepathy-mission-control svn path=/nixpkgs/trunk/; revision=33066
2012-03-14 17:28:11 +01:00
telepathy_mission_control = callPackage ../applications/networking/instant-messengers/telepathy/mission-control { };
Batch update telepathy-related packages Some of these packages need glib-2.30.x, so I commit it to this branch. Add sofia-sip and telepathy-rakia. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33475
2012-03-29 18:33:32 +02:00
telepathy_rakia = callPackage ../applications/networking/instant-messengers/telepathy/rakia { };
Add telepathy-salut svn path=/nixpkgs/trunk/; revision=33143
2012-03-16 07:58:03 +01:00
telepathy_salut = callPackage ../applications/networking/instant-messengers/telepathy/salut {};
Rename 'gnome-terminator' to 'terminator' Align the package name with what other distros call it. Other distros: Fedora, Debian, Archlinux, OpenSUSE, Mageia, Slackware (and probably more).
2014-02-17 20:43:35 +01:00
terminator = callPackage ../applications/misc/terminator {
vte = gnome.vte.override { pythonSupport = true; };
inherit (pythonPackages) notify;
};
Adding tesseract, an OCR engine I just found but never tried. svn path=/nixpkgs/trunk/; revision=26952
2011-04-24 20:04:07 +02:00
tesseract = callPackage ../applications/graphics/tesseract { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
thinkingRock = callPackage ../applications/misc/thinking-rock { };
added thinkingRock svn path=/nixpkgs/trunk/; revision=13993
2009-02-06 04:14:30 +01:00
thunderbird: Update to 16.0.2
2012-10-31 17:16:01 +01:00
thunderbird = callPackage ../applications/networking/mailreaders/thunderbird {
Add Thunderbird 5.0. svn path=/nixpkgs/trunk/; revision=28710
2011-08-20 16:30:09 +02:00
inherit (gnome) libIDL;
thunderbird: major update 17.* -> 31.0 - To fix build problems, I refactored the build process according to Mozilla recommendations. - 31.0 should become the next ESR branch (31 released today). CC @nbp @edolstra
2014-07-22 22:18:24 +02:00
inherit (pythonPackages) pysqlite;
libpng = libpng_apng;
Add Thunderbird 5.0. svn path=/nixpkgs/trunk/; revision=28710
2011-08-20 16:30:09 +02:00
};
add thunderbird-bin: the binary package for Thunderbird mail client
2014-04-12 17:29:14 +02:00
thunderbird-bin = callPackage ../applications/networking/mailreaders/thunderbird-bin {
gconf = pkgs.gnome.GConf;
inherit (pkgs.gnome) libgnome libgnomeui;
inherit (pkgs.xlibs) libX11 libXScrnSaver libXext
libXinerama libXrender libXt;
};
Tig: cosmetics
2012-08-08 00:53:05 +02:00
tig = gitAndTools.tig;
Tilda (version 1.1.12): New Package Tida is a GTK-based drop-down terminal emulator
2014-08-28 00:10:47 +02:00
tilda = callPackage ../applications/misc/tilda {
vte = gnome3.vte;
tilda: fixups; seems to work now - xgettext hack inspired by a guix thread - gsettings to prevent crashes - expression refactoring
2014-08-29 11:27:21 +02:00
gtk = gtk3;
Tilda (version 1.1.12): New Package Tida is a GTK-based drop-down terminal emulator
2014-08-28 00:10:47 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
timidity = callPackage ../tools/misc/timidity { };
Added TiMidity MIDI renderer svn path=/nixpkgs/trunk/; revision=9359
2007-09-23 16:47:11 +02:00
tint2 nixpkg
2013-12-22 17:20:17 +01:00
tint2 = callPackage ../applications/misc/tint2 { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tkcvs = callPackage ../applications/version-management/tkcvs { };
Adding tkcvs (which manages also subversion repositories well, they claim) svn path=/nixpkgs/trunk/; revision=16008
2009-06-19 11:02:48 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tla = callPackage ../applications/version-management/arch { };
Add GNU Arch (tla). svn path=/nixpkgs/trunk/; revision=10714
2008-02-17 14:44:30 +01:00
Add todo.txt-cli, a cli todo list manager Signed-off-by: Shea Levy <shea@shealevy.com>
2014-01-16 01:44:37 +01:00
todo-txt-cli = callPackage ../applications/office/todo.txt-cli { };
TorChat: packaged svn path=/nixpkgs/trunk/; revision=30480
2011-11-19 18:12:00 +01:00
torchat = callPackage ../applications/networking/instant-messengers/torchat {
wrapPython = pythonPackages.wrapPython;
};
Adding toxic, the reference CLI for Tox
2013-10-11 21:42:42 +02:00
toxic = callPackage ../applications/networking/instant-messengers/toxic { };
transmission: update to 2.77, but leave the old 2.60 for its gtk client The gtk client in 2.61 and above require a gtk3 we don't have in nixpkgs yet.
2013-03-17 22:27:55 +01:00
transcode: new package Suite of command line utilities for transcoding video and audio codecs, and for converting beween different container formats. http://www.transcoding.org/
2014-06-22 19:23:16 +02:00
transcode = callPackage ../applications/audio/transcode { };
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
transmission = callPackage ../applications/networking/p2p/transmission { };
transmission: unify versions to the newest, use gtk3 Also introduce transmission_gtk attribute and signify gtk client support in the name (so newbies using package names can see there's a gui version).
2013-10-04 20:31:02 +02:00
transmission_gtk = transmission.override { enableGTK3 = true; };
applications/networking/p2p/transmission: New nixpkg. svn path=/nixpkgs/trunk/; revision=20840
2010-03-28 01:06:30 +01:00
transmission-remote-gtk: add version 1.0.1 Patch submitted by Jan Malakhovski <oxij@oxij.org>.
2012-07-02 16:24:24 +02:00
transmission_remote_gtk = callPackage ../applications/networking/p2p/transmission-remote-gtk {};
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
trayer = callPackage ../applications/window-managers/trayer { };
Add trayer svn path=/nixpkgs/trunk/; revision=28558
2011-08-14 07:03:54 +02:00
Many minor fixes to get things building after recent compiler changes
2014-08-11 06:18:57 +02:00
tree = callPackage ../tools/system/tree {};
all-packages.nix: added the 'tree' utility svn path=/nixpkgs/trunk/; revision=27916
2011-07-24 11:57:06 +02:00
svn path=/nixpkgs/trunk/; revision=27128
2011-05-04 10:55:30 +02:00
tribler = callPackage ../applications/networking/p2p/tribler { };
* Added Tribler. Doesn't quite work yet. svn path=/nixpkgs/trunk/; revision=27124
2011-05-03 19:12:31 +02:00
twister: Add new package, version 0.9.22. This includes another source-only derivation for the web interface (and patches the path into the twister binary), so there shouldn't be a need to move it into ~/.twister/html separately. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2014-07-13 23:56:11 +02:00
twister = callPackage ../applications/networking/p2p/twister { };
twmn: add twmn to all-packages.nix
2014-02-22 18:13:26 +01:00
twmn = callPackage ../applications/misc/twmn { };
twinkle: fix build (fixes #3673) Pulled patches from Debian and hacked around linking errors. I'm able to ring my mobile phone now. However, on exit the process is stuck and needs kill -9. CC: maintainer @MarcWeber.
2014-08-20 21:27:43 +02:00
twinkle = callPackage ../applications/networking/instant-messengers/twinkle { };
adding twinkle, a voice over IP phone software svn path=/nixpkgs/trunk/; revision=17303
2009-09-20 19:01:19 +02:00
Adding umurmur and protobuf-c.
2012-09-25 19:35:03 +02:00
umurmur = callPackage ../applications/networking/umurmur { };
* Update lablgtk2 (and enable hydra build) svn path=/nixpkgs/trunk/; revision=25213
2010-12-20 15:58:56 +01:00
unison = callPackage ../applications/networking/sync/unison {
inherit (ocamlPackages) lablgtk;
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
enableX11 = config.unison.enableX11 or true;
* Update lablgtk2 (and enable hydra build) svn path=/nixpkgs/trunk/; revision=25213
2010-12-20 15:58:56 +01:00
};
* add unison - unison uses a wrapper script to add font-schumacher-misc to the local X font path if the font isn't already present; this is necessary for it to work, but not terribly nice ... * lablgtk is a dependency of unison - handling of library dirs with ocaml is a hack so far; in principle, ocaml needs a general setup for library dirs like ghc svn path=/nixpkgs/trunk/; revision=9094
2007-08-10 10:21:31 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
uucp = callPackage ../tools/misc/uucp { };
all-packages.nix changes for all the previous commits svn path=/nixpkgs/trunk/; revision=11564
2008-04-11 11:32:27 +02:00
uvccapture: new package "Capture image from USB webcam at a specified interval" I apply patches from Debian to make it build with V4L2 (instead of v1 API) and fix some warnings/bugs. Source code is also downloaded from Debian, as uvccapture homepage is unavailable. Homepage: http://linux-uvc.berlios.de/ (seems to have vanished...)
2014-08-17 23:43:08 +02:00
uvccapture = callPackage ../applications/video/uvccapture { };
Adding prayer. It builds on linux x86_64, but I've not tried to run it. svn path=/nixpkgs/trunk/; revision=30347
2011-11-08 22:07:57 +01:00
uwimap = callPackage ../tools/networking/uwimap { };
uzbl: build with webkitgtk2, cleanup
2014-03-30 03:52:36 +02:00
uzbl = callPackage ../applications/networking/browsers/uzbl {
webkit = webkitgtk2;
Adding uzbl experimental snapshot svn path=/nixpkgs/trunk/; revision=17344
2009-09-22 05:51:04 +02:00
};
all-packages.nix: strip trailing whitespace
2014-08-20 11:57:56 +02:00
add uTox
2014-07-31 12:56:16 +02:00
uTox = callPackage ../applications/networking/instant-messengers/utox { };
Adding uzbl experimental snapshot svn path=/nixpkgs/trunk/; revision=17344
2009-09-22 05:51:04 +02:00
Add vanitygen
2013-05-30 12:41:29 +02:00
vanitygen = callPackage ../applications/misc/vanitygen { };
vbindiff: New package, version 3.0_beta4. Visual binary differences viewer, very useful for reverse-engineering proprieritary file formats. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-12 07:07:50 +01:00
vbindiff = callPackage ../applications/editors/vbindiff { };
vcprompt: new package This adds the vcprompt utility, a little C program that prints a short string with barebones information about the current working directory for various version control systems.
2014-07-02 08:43:47 +02:00
vcprompt = callPackage ../applications/version-management/vcprompt { };
* Added libvdpau and vdpauinfo. svn path=/nixpkgs/branches/stdenv-updates/; revision=25296
2010-12-27 19:30:52 +01:00
vdpauinfo = callPackage ../tools/X11/vdpauinfo { };
Add Veracity distributed VCS (+ issue tracker) svn path=/nixpkgs/trunk/; revision=23031
2010-08-08 00:44:25 +02:00
veracity = callPackage ../applications/version-management/veracity {};
Moved monotone packages to a more appropriate position within all-packages.nix svn path=/nixpkgs/trunk/; revision=19144
2009-12-29 12:57:27 +01:00
viewMtn = builderDefsPackage (import ../applications/version-management/viewmtn/0.10.nix)
{
Moved "flup" from all-packages.nix into python-packages.nix. svn path=/nixpkgs/trunk/; revision=24044
2010-10-04 11:49:09 +02:00
inherit monotone cheetahTemplate highlight ctags
Moved monotone packages to a more appropriate position within all-packages.nix svn path=/nixpkgs/trunk/; revision=19144
2009-12-29 12:57:27 +01:00
makeWrapper graphviz which python;
Moved "flup" from all-packages.nix into python-packages.nix. svn path=/nixpkgs/trunk/; revision=24044
2010-10-04 11:49:09 +02:00
flup = pythonPackages.flup;
Moved monotone packages to a more appropriate position within all-packages.nix svn path=/nixpkgs/trunk/; revision=19144
2009-12-29 12:57:27 +01:00
};
vim: no longer need to use clangStdenv on darwin
2014-05-31 22:19:02 +02:00
vim = callPackage ../applications/editors/vim { };
* eclipse-sdk: added support for plugins * Added Spoofax editor plugin. * re-added eclipse-sdk 3.1, which wasn't necessary after all. svn path=/nixpkgs/trunk/; revision=4255
2005-11-08 00:02:17 +01:00
add MacVim
2014-06-06 23:45:22 +02:00
macvim = callPackage ../applications/editors/vim/macvim.nix { };
* eclipse-sdk: added support for plugins * Added Spoofax editor plugin. * re-added eclipse-sdk 3.1, which wasn't necessary after all. svn path=/nixpkgs/trunk/; revision=4255
2005-11-08 00:02:17 +01:00
* Turn vim/default.nix into a regular package. We don't need two configurable VIMs. svn path=/nixpkgs/trunk/; revision=22784
2010-07-28 14:52:54 +02:00
vimHugeX = vim_configurable;
Included some configuration for Vim. svn path=/nixpkgs/trunk/; revision=9099
2007-08-10 21:53:30 +02:00
vim_configurable: fix compilation on darwin * compile with gccApple * enable darwinSupport by default * do not use patchelf
2013-06-13 10:12:12 +02:00
vim_configurable = callPackage ../applications/editors/vim/configurable.nix {
Update vim_configurable to the same source tag as default vim
2013-12-29 16:38:43 +01:00
inherit (pkgs) fetchurl fetchhg stdenv ncurses pkgconfig gettext
vim_configurable: fix compilation on darwin * compile with gccApple * enable darwinSupport by default * do not use patchelf
2013-06-13 10:12:12 +02:00
composableDerivation lib config glib gtk python perl tcl ruby;
inherit (pkgs.xlibs) libX11 libXext libSM libXpm libXt libXaw libXau libXmu
libICE;
vim_configurable example added. broken see comment. svn path=/nixpkgs/trunk/; revision=9923
2007-12-12 08:20:41 +01:00
features = "huge"; # one of tiny, small, normal, big or huge
Explicit pkgs.prefix svn path=/nixpkgs/trunk/; revision=23329
2010-08-21 21:27:31 +02:00
lua = pkgs.lua5;
vim_configurable: improvements * add ruby interpreter (may have been accidentally removed, or may never have existed) * allow selection of GUI options by setting `config.vim.gui`
2013-06-15 12:48:20 +02:00
gui = config.vim.gui or "auto";
vim_configurable: fix compilation on darwin * compile with gccApple * enable darwinSupport by default * do not use patchelf
2013-06-13 10:12:12 +02:00
vim_configurable example added. broken see comment. svn path=/nixpkgs/trunk/; revision=9923
2007-12-12 08:20:41 +01:00
# optional features by flags
Turn on Python plugin for vim_configurable by default Python plugin for vim is turned on by default in ubuntu and other flavors of linux and mimicking this in NixOS will help contribut to the impression that NixOS "just works."
2012-12-17 21:54:39 +01:00
flags = [ "python" "X11" ]; # only flag "X11" by now
vim_configurable: fix compilation on darwin * compile with gccApple * enable darwinSupport by default * do not use patchelf
2013-06-13 10:12:12 +02:00
# so that we can use gccApple if we're building on darwin
inherit stdenvAdapters gccApple;
vim_configurable example added. broken see comment. svn path=/nixpkgs/trunk/; revision=9923
2007-12-12 08:20:41 +01:00
};
Fix Nixpkgs evaluation http://hydra.nixos.org/build/5722962
2013-08-16 11:52:10 +02:00
Fix some name collisions
2013-07-30 12:31:31 +02:00
vimNox = lowPrio (vim_configurable.override { source = "vim-nox"; });
vim_configurable example added. broken see comment. svn path=/nixpkgs/trunk/; revision=9923
2007-12-12 08:20:41 +01:00
Add qvim - an experimental Qt gui for Vim vim-qt has the most complete set of Ctrl-Alt-Meta binding functionality. For example, qvim is able to correctly bind keys like Alt-<nonlatin>. More: https://bitbucket.org/equalsraf/vim-qt/wiki/Features
2013-11-04 19:55:13 +01:00
qvim = lowPrio (callPackage ../applications/editors/vim/qvim.nix {
inherit (pkgs) fetchgit stdenv ncurses pkgconfig gettext
composableDerivation lib config python perl tcl ruby qt4;
inherit (pkgs.xlibs) libX11 libXext libSM libXpm libXt libXaw libXau libXmu
libICE;
Add missing arguments to qvim --- needed to preserve the partial Darwin compatibility fixes inherited from main vim expression
2013-11-08 06:01:28 +01:00
inherit (pkgs) stdenvAdapters gccApple;
Add qvim - an experimental Qt gui for Vim vim-qt has the most complete set of Ctrl-Alt-Meta binding functionality. For example, qvim is able to correctly bind keys like Alt-<nonlatin>. More: https://bitbucket.org/equalsraf/vim-qt/wiki/Features
2013-11-04 19:55:13 +01:00
features = "huge"; # one of tiny, small, normal, big or huge
lua = pkgs.lua5;
flags = [ "python" "X11" ]; # only flag "X11" by now
});
vimpc: initial install script
2014-07-25 15:32:04 +02:00
vimpc = callPackage ../applications/audio/vimpc { };
vimHugeX: also add wrapper for system-wide vimrc
2013-08-29 23:27:48 +02:00
Bump virt-viewer to 0.6.0, from the 2009 version
2014-05-10 10:37:59 +02:00
virtviewer = callPackage ../applications/virtualization/virt-viewer {
gtkvnc = gtkvnc.override { enableGTK3 = true; };
spice_gtk = spice_gtk.override { enableGTK3 = true; };
};
fixed most virt-manager issues!
2012-07-21 01:27:24 +02:00
virtmanager = callPackage ../applications/virtualization/virt-manager {
all-packages.nix: strip trailing whitespace
2012-07-22 18:55:02 +02:00
inherit (gnome) gnome_python;
virt-manager: update to 1.0.1, fix & update dependencies, gtk3 support - Vte, add gtk3 support, enable introspection, update to 0.35.90 - Spice-gtk, add gtk3 support - gtk-vnc, add gtk3 support - Add libvirt-glib (thanks @bjornfor) - Add usbredir - qemu, enable usbredir - spice-gtk, enable usbredir - virt-manager, update to 1.0.1 [Bjørn: * Set namePrefix = "" to preserve package name "virt-manager" (instead of "python2.7-virt-manager") * Add dconf to GIO_EXTRA_MODULES to get persistent settings in virt-manager. Without it: GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications. * Add ${gtk3}/share to XDG_DATA_DIRS to unbreak "Take Screenshot" feature (fixes "Settings schema 'org.gtk.Settings.FileChooser' is not installed") * gtk-vnc: don't pull "pkgs" attrset for optionalString, use stdenv.lib.optionalString instead. ]
2014-03-23 18:12:07 +01:00
vte = gnome3.vte;
dconf = gnome3.dconf;
gtkvnc = gtkvnc.override { enableGTK3 = true; };
spice_gtk = spice_gtk.override { enableGTK3 = true; };
fixed most virt-manager issues!
2012-07-21 01:27:24 +02:00
};
virtinst installs now. still most tools don't work and virt-manager still has problems with finding libvirt. svn path=/nixpkgs/trunk/; revision=34052
2012-05-10 21:29:54 +02:00
virtinst = callPackage ../applications/virtualization/virtinst {};
Adding virt-viewer svn path=/nixpkgs/trunk/; revision=25548
2011-01-13 23:30:32 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
virtualgl = callPackage ../tools/X11/virtualgl { };
Adding virtualgl (and therefore, libjpeg-turbo, a SIMD API-compatible libjpeg) svn path=/nixpkgs/trunk/; revision=22553
2010-07-10 10:45:44 +02:00
Added 'bumblebee', a package that facilitates NVidia Optimus graphics with X11. Note: it relies heavily on 'virtualgl'. This also makes the approach taken by bumblebee not very effective. So, this package is actually mainly useful for shutting down your card so that it does not consume power/produce heat. See the comments in bumblebee/default.nix svn path=/nixpkgs/trunk/; revision=32036
2012-02-05 01:51:35 +01:00
bumblebee = callPackage ../tools/X11/bumblebee { };
Adding vkeybd, a virtual midi keyboard svn path=/nixpkgs/trunk/; revision=26919
2011-04-22 11:39:48 +02:00
vkeybd = callPackage ../applications/audio/vkeybd {
inherit (xlibs) libX11;
};
vlc: use default/latest ffmpeg
2013-12-23 10:51:22 +01:00
vlc = callPackage ../applications/video/vlc { };
* development/libraries/gnome/*: upgraded all gnome packages to 2.8.3. * development/libraries/gnome/*: copied gtk packages to gnome directory. gnome 2.8.3 did not work on gtk 2.4 nor gtk 2.6. Using the specific version of the gnome platform 2.8.3 directory 'solved' the issue. * development/libraries/gnome/gnome-icon-theme: new packag * development/libraries/gnome/libgtkhtml: new package * development/libraries/gnome/gtkhtml: new package * development/libraries/gnome/libgnomeprint: new package * development/libraries/gnome/libgnomeprintui: new package * development/libraries/gnome/gnome-keyring: new package * development/libraries/gnome/gail: new package * applications/editors/monodoc: new package svn path=/nixpkgs/trunk/; revision=2312
2005-02-27 00:45:19 +01:00
add vmpk 0.5.1, a virtual midi piano keyboard
2014-03-15 06:13:25 +01:00
vmpk = callPackage ../applications/audio/vmpk { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vnstat = callPackage ../applications/networking/vnstat { };
Adding vnstat. Unless using "vnstat -l", it wants some directories in /var, where it collects information. svn path=/nixpkgs/trunk/; revision=17753
2009-10-12 13:08:52 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vorbisTools = callPackage ../applications/audio/vorbis-tools { };
Add Vorbis Tools. svn path=/nixpkgs/trunk/; revision=10628
2008-02-11 23:39:54 +01:00
Give up and use Oracle JRE for VUE
2013-11-26 19:41:29 +01:00
vue = callPackage ../applications/misc/vue {
Use IcedTea for VUE, not Oracle JRE
2014-04-16 12:47:18 +02:00
jre = icedtea7_jre;
Give up and use Oracle JRE for VUE
2013-11-26 19:41:29 +01:00
};
adding VUE mindmapper svn path=/nixpkgs/trunk/; revision=28957
2011-09-01 15:41:42 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
vwm = callPackage ../applications/window-managers/vwm { };
Adding vwm, the console window manager. svn path=/nixpkgs/trunk/; revision=15255
2009-04-22 23:33:24 +02:00
vym: new package VYM (View Your Mind) is a mind-mapping program. [Bjørn: two whitespace adjustments and quote the "$out" variable.]
2014-08-20 23:08:07 +02:00
vym = callPackage ../applications/misc/vym { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
w3m = callPackage ../applications/networking/browsers/w3m {
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
graphicsSupport = false;
* development/libraries/gnome/*: upgraded all gnome packages to 2.8.3. * development/libraries/gnome/*: copied gtk packages to gnome directory. gnome 2.8.3 did not work on gtk 2.4 nor gtk 2.6. Using the specific version of the gnome platform 2.8.3 directory 'solved' the issue. * development/libraries/gnome/gnome-icon-theme: new packag * development/libraries/gnome/libgtkhtml: new package * development/libraries/gnome/gtkhtml: new package * development/libraries/gnome/libgnomeprint: new package * development/libraries/gnome/libgnomeprintui: new package * development/libraries/gnome/gnome-keyring: new package * development/libraries/gnome/gail: new package * applications/editors/monodoc: new package svn path=/nixpkgs/trunk/; revision=2312
2005-02-27 00:45:19 +01:00
};
weechat: Backport fix for freeze with gnutls 3.2. Fixes /exit when using gnutls 3.2. This is a temporary solution as 3.1 isn't building right now. The next release of weechat will include this fix.
2014-03-21 13:26:03 +01:00
weechat = callPackage ../applications/networking/irc/weechat { };
* Added weechat and updated xfce-terminal and vte. (From Graeme Caldwell <graemercaldwell@gmail.com>.) svn path=/nixpkgs/trunk/; revision=22965
2010-08-05 17:47:15 +02:00
Mark the development version of weechat 'lowPrio' so that user install the stable release version by default.
2014-05-07 17:39:18 +02:00
weechatDevel = lowPrio (callPackage ../applications/networking/irc/weechat/devel.nix { });
adding development version of weechat (alongside stable)
2014-04-17 23:22:54 +02:00
wayland, weston: update to 1.3.1, fix weston build Also make Hydra build weston, so we can see the breakages in future.
2013-11-23 23:30:47 +01:00
weston = callPackage ../applications/window-managers/weston { };
winswitch: Basic somewhat working version. Wow, this is one of the most dangerous programs I've seen in a while. It not only tries to probe for a package manager to install dependencies but also tries to execute a whole bunch of programs in $PATH. That's why I decided to override the postFixup phase for now in order to get rid of the current $PATH and meanwhile getting the basics working. So, I'm still not sure how to do the best implementation here on NixOS without allowing winswitch to be too invasive and without restricting it too much so that it's of no use. But let's figure that out once we trimmed down the radiation level of this "living" thing ;-) Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-06-21 16:15:07 +02:00
windowmaker: New package in version 0.95.4. Packaged this for @devhell sometime ago and adding it here so maybe it's useful for other people using Nix(OS). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-08-14 18:57:06 +02:00
windowmaker = callPackage ../applications/window-managers/windowmaker { };
winswitch: Basic somewhat working version. Wow, this is one of the most dangerous programs I've seen in a while. It not only tries to probe for a package manager to install dependencies but also tries to execute a whole bunch of programs in $PATH. That's why I decided to override the postFixup phase for now in order to get rid of the current $PATH and meanwhile getting the basics working. So, I'm still not sure how to do the best implementation here on NixOS without allowing winswitch to be too invasive and without restricting it too much so that it's of no use. But let's figure that out once we trimmed down the radiation level of this "living" thing ;-) Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-06-21 16:15:07 +02:00
winswitch = callPackage ../tools/X11/winswitch { };
Making wings work (it works with the old erlang).
2013-03-27 15:38:09 +01:00
wings = callPackage ../applications/graphics/wings {
erlangR16: updated to R16B03-1 - couchdb: using erlangR16 (fails to build with R17) - rename erlang attr names to use only major version in attr name
2014-06-05 02:16:50 +02:00
erlang = erlangR14;
esdl = esdl.override { erlang = erlangR14; };
Making wings work (it works with the old erlang).
2013-03-27 15:38:09 +01:00
};
Adding Wings 3D (as a side effect, update erlang, and add esdl). svn path=/nixpkgs/trunk/; revision=22436
2010-07-01 11:08:37 +02:00
wmname: add version 0.1 Run "wmname LG3D" to fix Java GUIs running in the ratpoison window manager. This probably applies to other tiling window managers, too.
2012-11-17 12:57:25 +01:00
wmname = callPackage ../applications/misc/wmname { };
wmctrl: command-line window-manipulation tool
2013-07-26 16:15:22 +02:00
wmctrl = callPackage ../tools/X11/wmctrl { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
# I'm keen on wmiimenu only >wmii-3.5 no longer has it...
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
wmiimenu = import ../applications/window-managers/wmii31 {
removed libixp-0.3 (wmiimenu does also build with 0.4) wmii updated svn path=/nixpkgs/trunk/; revision=12011
2008-06-08 23:41:07 +02:00
libixp = libixp_for_wmii;
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
inherit fetchurl /* fetchhg */ stdenv gawk;
inherit (xlibs) libX11;
};
wmiiSnap = import ../applications/window-managers/wmii {
libixp = libixp_for_wmii;
inherit fetchurl /* fetchhg */ stdenv gawk;
removed libixp-0.3 (wmiimenu does also build with 0.4) wmii updated svn path=/nixpkgs/trunk/; revision=12011
2008-06-08 23:41:07 +02:00
inherit (xlibs) libX11 xextproto libXt libXext;
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
includeUnpack = config.stdenv.includeUnpack or false;
add wmii window manager + all dependencies. Interesting excercise... svn path=/nixpkgs/trunk/; revision=8338
2007-03-19 00:58:22 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wordnet = callPackage ../applications/misc/wordnet { };
Add WordNet, a lexical database for English. svn path=/nixpkgs/trunk/; revision=10659
2008-02-13 15:26:01 +01:00
synchronize with trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=29696
2011-10-06 15:16:47 +02:00
wrapFirefox =
* Set the Chrome icon in its desktop item. svn path=/nixpkgs/trunk/; revision=29701
2011-10-06 15:52:54 +02:00
{ browser, browserName ? "firefox", desktopName ? "Firefox", nameSuffix ? ""
Fix default icon location in 'wrapFirefox'
2014-08-11 10:20:17 +02:00
, icon ? "${browser}/lib/${browser.name}/browser/icons/mozicon128.png" }:
firefoxWrapper: Fix Quake Live support.
2013-02-03 19:17:33 +01:00
let
cfg = stdenv.lib.attrByPath [ browserName ] {} config;
Don't enable Flash by default in the Firefox wrapper
2014-03-14 13:32:01 +01:00
enableAdobeFlash = cfg.enableAdobeFlash or false;
firefoxWrapper: Fix Quake Live support.
2013-02-03 19:17:33 +01:00
enableGnash = cfg.enableGnash or false;
in
synchronize with trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=29696
2011-10-06 15:16:47 +02:00
import ../applications/networking/browsers/firefox/wrapper.nix {
Fix references to pkgs/lib
2013-09-30 22:43:34 +02:00
inherit stdenv lib makeWrapper makeDesktopItem browser browserName desktopName nameSuffix icon;
synchronize with trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=29696
2011-10-06 15:16:47 +02:00
plugins =
assert !(enableGnash && enableAdobeFlash);
([ ]
++ lib.optional enableGnash gnash
++ lib.optional enableAdobeFlash flashplayer
Fix Firefox config option processing
2012-09-26 23:27:20 +02:00
++ lib.optional (cfg.enableDjvu or false) (djview4)
++ lib.optional (cfg.enableMPlayer or false) (MPlayerPlugin browser)
++ lib.optional (cfg.enableGeckoMediaPlayer or false) gecko_mediaplayer
++ lib.optional (supportsJDK && cfg.jre or false && jrePlugin ? mozillaPlugin) jrePlugin
Typo, fix the googleTalkPlugin
2012-09-26 23:45:35 +02:00
++ lib.optional (cfg.enableGoogleTalkPlugin or false) google_talk_plugin
Adding FriBID browser plugin FriBID is an open source software for the Swedish e-id system called BankID. FriBID also supports processor architectures and Linux/BSD distributions that the official software doesn't support. https://fribid.se/index.en.html FriBID plugin is a firefoxWrapper plugin. Enabled by setting: nixpkgs.config.enableFriBIDPlugin = true
2013-09-04 21:29:37 +02:00
++ lib.optional (cfg.enableFriBIDPlugin or false) fribid
Add gnome shell extensions plugin for browsers
2014-07-05 21:15:51 +02:00
++ lib.optional (cfg.enableGnomeExtensions or false) gnome3.gnome_shell
synchronize with trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=29696
2011-10-06 15:16:47 +02:00
);
firefox: enable gstreamer for h.264 support in HTML5 video
2013-12-23 15:48:02 +01:00
libs = [ gstreamer gst_plugins_base ] ++ lib.optionals (cfg.enableQuakeLive or false)
(with xlibs; [ stdenv.gcc libX11 libXxf86dga libXxf86vm libXext libXt alsaLib zlib ]);
firefoxWrapper: Add libcanberra gtk module to firefox
2013-05-10 02:44:03 +02:00
gtk_modules = [ libcanberra ];
synchronize with trunk svn path=/nixpkgs/branches/stdenv-updates/; revision=29696
2011-10-06 15:16:47 +02:00
};
Finally, a real text editor in Nix. Todo: allow configuration with modes. svn path=/nixpkgs/trunk/; revision=1543
2004-10-06 13:32:20 +02:00
wxhexeditor: adding version 0.22 wxhexeditor: add the package to all-packages.nix wxhexeditor: fix shebang
2014-08-22 13:24:18 +02:00
wxhexeditor = callPackage ../applications/editors/wxhexeditor { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
x11vnc = callPackage ../tools/X11/x11vnc { };
- svn path=/nixpkgs/branches/stdenv-updates-merge/; revision=10823
2008-02-22 04:06:12 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
x2vnc = callPackage ../tools/X11/x2vnc { };
Added x2vnc, a tool to control physically close but formally remote VNC display as an extension of local one. svn path=/nixpkgs/trunk/; revision=11148
2008-03-17 07:29:32 +01:00
Added XaoS fractal viewer svn path=/nixpkgs/trunk/; revision=14004
2009-02-08 15:17:05 +01:00
xaos = builderDefsPackage (import ../applications/graphics/xaos) {
inherit (xlibs) libXt libX11 libXext xextproto xproto;
XaoS wants libpng12 svn path=/nixpkgs/trunk/; revision=32809
2012-03-06 10:28:08 +01:00
inherit gsl aalib zlib intltool gettext perl;
libpng = libpng12;
Added XaoS fractal viewer svn path=/nixpkgs/trunk/; revision=14004
2009-02-08 15:17:05 +01:00
};
Fix XaraLX, add debian-patches.sh svn path=/nixpkgs/trunk/; revision=31358
2012-01-06 19:13:11 +01:00
xara = callPackage ../applications/graphics/xara { };
* Emacs 22.0.50 (CVS dump). svn path=/nixpkgs/trunk/; revision=4359
2005-12-13 01:13:01 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xawtv = callPackage ../applications/video/xawtv { };
* Added the Emacs 22.0 branch with anti-aliasing (Xft) support. * Added an option to Adobe Reader to make it start faster (by deleting all the plugins). svn path=/nixpkgs/trunk/; revision=4406
2005-12-22 11:49:43 +01:00
Adding xbindkeys (now with all the files) svn path=/nixpkgs/trunk/; revision=26448
2011-03-21 19:10:20 +01:00
xbindkeys = callPackage ../tools/X11/xbindkeys { };
Adding xbindkeys svn path=/nixpkgs/trunk/; revision=26436
2011-03-20 23:16:32 +01:00
xbmc: pin to ffmpeg 1
2013-12-16 14:37:04 +01:00
xbmc = callPackage ../applications/video/xbmc {
ffmpeg = ffmpeg_1;
};
xbmc: add version 11
2013-01-05 22:07:47 +01:00
Add xca, interface for managing keys like RSA or DSA
2013-10-07 12:57:09 +02:00
xca = callPackage ../applications/misc/xca { };
Add xcalib 0.8, a tiny monitor calibration loader
2012-12-11 11:33:11 +01:00
xcalib = callPackage ../tools/X11/xcalib { };
Adding x-cape keyboard mapping helper
2013-07-30 13:51:01 +02:00
xcape = callPackage ../tools/X11/xcape { };
add xchainkeys-0.11
2013-03-08 06:55:32 +01:00
xchainkeys = callPackage ../tools/X11/xchainkeys { };
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
xchat = callPackage ../applications/networking/irc/xchat { };
* nxml package. svn path=/nixpkgs/trunk/; revision=578
2003-12-08 12:56:50 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xchm = callPackage ../applications/misc/xchm { };
Upgraded nxml mode and added cua mode svn path=/nixpkgs/trunk/; revision=1544
2004-10-06 14:06:23 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xcompmgr = callPackage ../applications/window-managers/xcompmgr { };
applications/window-managers/xcompmgr: New package. svn path=/nixpkgs/trunk/; revision=19272
2010-01-06 21:45:43 +01:00
Committing some outstanding modifications that I cannot make into smaller chunks anymore. * added briss: a pdf cropper * added compton, an improved fork of xcompmgr * added myself to the maintainers list * minor version bumps: xcompmgr, upower svn path=/nixpkgs/trunk/; revision=34380
2012-06-08 12:16:46 +02:00
compton = callPackage ../applications/window-managers/compton { };
Adding XDaliClock svn path=/nixpkgs/trunk/; revision=26591
2011-03-29 12:32:49 +02:00
xdaliclock = callPackage ../tools/misc/xdaliclock {};
xdg-user-dirs: new package A tool to help manage well known user directories like the desktop folder and the music folder http://freedesktop.org/wiki/Software/xdg-user-dirs
2014-04-16 15:01:11 +02:00
xdg-user-dirs = callPackage ../tools/X11/xdg-user-dirs { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xdg_utils = callPackage ../tools/X11/xdg-utils { };
* Added xdg-utils, a package that contains desktop integration commands such as `xdg-open' (which opens a URL with the user's default browser). svn path=/nixpkgs/trunk/; revision=20829
2010-03-25 20:48:06 +01:00
Adding xdotool svn path=/nixpkgs/trunk/; revision=26896
2011-04-19 22:51:40 +02:00
xdotool = callPackage ../tools/X11/xdotool { };
Remove broken flag for xen, build with gcc45.
2014-08-01 17:18:27 +02:00
xen = callPackage ../applications/virtualization/xen {
stdenv = overrideGCC stdenv gcc45;
};
Some of preparation work for adding Xen. Troubles: 1. Xen Dom0 support not complete in mainline. 2. Xen's love to check for headers in /usr/include. To do afterwards: We need to change bootloading setup a bit. svn path=/nixpkgs/trunk/; revision=12941
2008-10-04 17:24:08 +02:00
Making xfe find and load icons fine I added more dependencies to fox, for that. I tried to add mesa too, but it wasn't trivial for it to find it, so I took it out.
2013-05-16 23:35:48 +02:00
xfe = callPackage ../applications/misc/xfe {
fox = fox_1_6;
};
Add xfe-1.33 and fox-1.6.9 This specific version of fox is required by xfe Signed-off-by: Baptist BENOIST <return_0@live.com>
2012-10-16 17:30:44 +02:00
xfig: Use the default gcc
2013-01-28 18:25:10 +01:00
xfig = callPackage ../applications/graphics/xfig { };
* By popular demand: xfig. svn path=/nixpkgs/trunk/; revision=7278
2006-12-08 02:17:21 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xineUI = callPackage ../applications/video/xine-ui { };
Haskell mode for emacs svn path=/nixpkgs/trunk/; revision=1832
2004-12-06 08:36:56 +01:00
gxneur: add frontend for XNEUR keyboard layout switcher
2012-08-14 12:50:25 +02:00
xneur_0_13 = callPackage ../applications/misc/xneur { };
all-packages.nix changes for previous commits svn path=/nixpkgs/trunk/; revision=11217
2008-03-20 10:52:40 +01:00
Make nixpkgs ready for gst_all attrset removal svn path=/nixpkgs/trunk/; revision=33092
2012-03-14 23:44:52 +01:00
xneur_0_8 = callPackage ../applications/misc/xneur/0.8.nix { };
all-packages.nix changes for previous commits svn path=/nixpkgs/trunk/; revision=11217
2008-03-20 10:52:40 +01:00
gxneur: add frontend for XNEUR keyboard layout switcher
2012-08-14 12:50:25 +02:00
xneur = xneur_0_13;
gxneur = callPackage ../applications/misc/gxneur {
inherit (gnome) libglade GConf;
};
Xiphos - New Package (version 3.2.1) This is a new expression for Xiphos 3.2.1, followed by an update of Sword library to 1.7.3 (required)
2014-04-19 21:33:00 +02:00
xiphos = callPackage ../applications/misc/xiphos {
gconf = gnome2.GConf;
inherit (gnome2) gtkhtml libgtkhtml libglade scrollkeeper;
python = python27;
webkitgtk = webkitgtk2;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
xournal = callPackage ../applications/graphics/xournal {
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit (gnome) libgnomeprint libgnomeprintui libgnomecanvas;
Adding Xournal - a note-taking application for stylus usage svn path=/nixpkgs/trunk/; revision=16538
2009-08-02 23:47:10 +02:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
xpdf = callPackage ../applications/misc/xpdf {
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
motif = lesstif;
* xpdf updated to 3.02pl1. Also patch its configuration file so that it uses the Base-14 fonts from Ghostscript. svn path=/nixpkgs/trunk/; revision=9396
2007-10-03 14:16:48 +02:00
base14Fonts = "${ghostscript}/share/ghostscript/fonts";
statically linked nano. For some reason I had to use the --enable-tiny configure flag, so the full blown normal glibc dynamically linked version is a bit less functional now, but it is only intended to be used in rescue mode anyway, since normal people use vi. svn path=/nixpkgs/trunk/; revision=6318
2006-08-30 01:40:29 +02:00
};
xkb_switch: command line tool to switch X keyboard layouts
2012-12-27 12:43:00 +01:00
xkb_switch = callPackage ../tools/X11/xkb-switch { };
Minor cleanup
2012-11-29 14:40:25 +01:00
libxpdf = callPackage ../applications/misc/xpdf/libxpdf.nix { };
added libxpdf and pdf2xml svn path=/nixpkgs/trunk/; revision=23427
2010-08-25 16:25:51 +02:00
Upgrading xpra to 0.8.8
2013-03-29 02:30:18 +01:00
xpra = callPackage ../tools/X11/xpra { };
* Adde xpra. Doesn't quite work yet. * Removed python_alts. svn path=/nixpkgs/trunk/; revision=11161
2008-03-17 14:45:50 +01:00
xrestop: package 0.4
2013-08-06 02:56:21 +02:00
xrestop = callPackage ../tools/X11/xrestop { };
xscreensaver: updated to version 5.15 (and moved to pkgs/misc/screensavers hierarchy) svn path=/nixpkgs/trunk/; revision=33655
2012-04-06 21:30:30 +02:00
xscreensaver = callPackage ../misc/screensavers/xscreensaver {
* Get rid of the `(import (__toPath ((toString ./JustNothing/.. )+"/"+args.version+".nix")))' hack, you can also just write `import (./path/to/pkg + "/${version}.nix)'. svn path=/nixpkgs/trunk/; revision=9792
2007-11-26 14:24:56 +01:00
inherit (gnome) libglade;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
Added XScreensaver; also changed version-stub.nix (now it does sumArgs itself, and requires builderDefs to be used) and added a merge of composing-builder and declarative flag processing. svn path=/nixpkgs/trunk/; revision=9776
2007-11-22 21:26:00 +01:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
xsynth_dssi = callPackage ../applications/audio/xsynth-dssi { };
Adding XSynth-DSSI, a classic analog style software synthesizer svn path=/nixpkgs/trunk/; revision=26909
2011-04-20 18:31:41 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xterm = callPackage ../applications/misc/xterm { };
* User-Mode Linux and GNU Patch. svn path=/nixpkgs/trunk/; revision=779
2004-02-13 15:42:28 +01:00
finalterm: Add package
2014-04-26 22:56:58 +02:00
finalterm = callPackage ../applications/misc/finalterm { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xtrace = callPackage ../tools/X11/xtrace { };
Adding xtrace (not that of glibc, but a X protocol tracer) svn path=/nixpkgs/trunk/; revision=19013
2009-12-17 12:58:05 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xlaunch = callPackage ../tools/X11/xlaunch { };
Fixed bridge-utils, added qemu, tuned builder-defs unpack, added xlaunch - a tool to launch X using everything possible from the job except slim. svn path=/nixpkgs/trunk/; revision=9985
2007-12-31 09:49:41 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xmacro = callPackage ../tools/X11/xmacro { };
Added xmacro; updated clisp - well, it compiles now... svn path=/nixpkgs/trunk/; revision=9098
2007-08-10 20:54:44 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xmove = callPackage ../applications/misc/xmove { };
Fixed bridge-utils, added qemu, tuned builder-defs unpack, added xlaunch - a tool to launch X using everything possible from the job except slim. svn path=/nixpkgs/trunk/; revision=9985
2007-12-31 09:49:41 +01:00
add xmp 4.0.7
2014-06-10 06:03:13 +02:00
xmp = callPackage ../applications/audio/xmp { };
xnee: update to 3.19
2014-08-27 15:55:26 +02:00
xnee = callPackage ../tools/X11/xnee { };
Added xnee utility for X11 action recording svn path=/nixpkgs/trunk/; revision=12612
2008-08-14 11:25:26 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
xvidcap = callPackage ../applications/video/xvidcap {
* Xvidcap for making screen recordings. svn path=/nixpkgs/trunk/; revision=7186
2006-12-01 17:44:26 +01:00
inherit (gnome) scrollkeeper libglade;
};
State qt version (3/4) in packages, not in all-packages.nix svn path=/nixpkgs/trunk/; revision=31406
2012-01-07 18:06:49 +01:00
yate = callPackage ../applications/misc/yate { };
adding yate2 telephony engine svn path=/nixpkgs/trunk/; revision=17861
2009-10-18 06:43:48 +02:00
yelp: new package Yelp is the help viewer in Gnome. https://wiki.gnome.org/Apps/Yelp
2014-02-16 11:42:22 +01:00
inherit (gnome3) yelp;
qgis-1.6.0, compiles Don't know whether it works: it fails to start on my computer because it loads KDE gui_platform plugin from incompatible Qt version. svn path=/nixpkgs/trunk/; revision=28483
2011-08-11 11:35:17 +02:00
qgis = callPackage ../applications/misc/qgis {};
hddtemp (tool to get harddisk temperatures) added and unfinished qgis expression (in case someone else want's to continue working on it) svn path=/nixpkgs/trunk/; revision=9903
2007-12-10 23:36:52 +01:00
qtbitcointrader: initial expression
2014-04-26 22:09:48 +02:00
qtbitcointrader = callPackage ../applications/misc/qtbitcointrader { };
Add ykpers (aka yubikey-personalization) package
2014-01-25 03:17:06 +01:00
ykpers = callPackage ../applications/misc/ykpers {};
Adding Yoshimi, a fork of ZynAddSubFX (audio synthesizer) with many enhancements including jack support svn path=/nixpkgs/trunk/; revision=26935
2011-04-23 15:54:25 +02:00
yoshimi = callPackage ../applications/audio/yoshimi {
fltk-1.3.0 svn path=/nixpkgs/trunk/; revision=31223
2012-01-03 11:02:33 +01:00
fltk = fltk13;
t/gis/qgis updating qgis Signed-off-by: Marc Weber <marco-oweber@gmx.de> svn path=/nixpkgs/trunk/; revision=22115
2010-06-03 02:51:23 +02:00
};
zathura: version 0.1.2 with plugins Expression handles new modular structure of zathura and adds support for djvu, pdf and ps plugins.
2012-05-14 23:43:46 +02:00
zathuraCollection = recurseIntoAttrs
(let callPackage = newScope pkgs.zathuraCollection; in
zathura: mupdf plugin
2014-05-17 14:16:50 +02:00
import ../applications/misc/zathura {
inherit callPackage pkgs fetchurl;
useMupdf = config.zathura.useMupdf or false;
});
zathura: version 0.1.2 with plugins Expression handles new modular structure of zathura and adds support for djvu, pdf and ps plugins.
2012-05-14 23:43:46 +02:00
zathura = zathuraCollection.zathuraWrapper;
new package: zed 0.12.0 (installer)
2014-07-26 14:39:06 +02:00
zed = callPackage ../applications/editors/zed { };
zeroc-ice: Add package
2014-01-31 02:41:58 +01:00
zeroc_ice = callPackage ../development/libraries/zeroc-ice { };
zathuraCollection: update to latest girara -> 0.1.9 zathura-core -> 0.2.5 zathura-djvu -> 0.2.3 zathura-pdf-poppler -> 0.2.4 zathura-ps -> 0.2.2
2013-11-23 15:19:54 +01:00
girara = callPackage ../applications/misc/girara {
gtk = gtk3;
};
* Added NEdit. svn path=/nixpkgs/trunk/; revision=4329
2005-12-03 01:04:13 +01:00
Adding zgrviewer svn path=/nixpkgs/trunk/; revision=34166
2012-05-18 11:32:02 +02:00
zgrviewer = callPackage ../applications/graphics/zgrviewer {};
Added support for minimal zim desktop wiki package.
2014-08-14 07:00:00 +02:00
zim = callPackage ../applications/office/zim {
pygtk = pyGtkGlade;
};
firefox: bring back version 30.0 for zotero
2014-08-04 18:13:48 +02:00
zotero = callPackage ../applications/office/zotero {
xulrunner = xulrunner_30;
};
Add zotero 4.0.19 (close #2043) @vcunat simplied the expression a little.
2014-03-27 00:24:20 +01:00
Fix most packages depending on fltk I failed to build cinepaint svn path=/nixpkgs/trunk/; revision=31224
2012-01-03 11:32:56 +01:00
zynaddsubfx = callPackage ../applications/audio/zynaddsubfx { };
Adding ZynAddSubFX, a software synthesizer, and minixml (a dependency of ZynAddSubFX) svn path=/nixpkgs/trunk/; revision=26746
2011-04-08 00:24:56 +02:00
Consistent whitespace
2013-06-13 15:18:16 +02:00
* Fixed Stratego. * Added Zoom, an interpreter for Z-Code. svn path=/nixpkgs/trunk/; revision=894
2004-04-01 18:02:53 +02:00
### GAMES
games/alienarena: New nixbuild. svn path=/nixpkgs/trunk/; revision=29975
2011-10-22 23:04:29 +02:00
alienarena = callPackage ../games/alienarena { };
all-packages.nix: define the 'andyetitmoves' attribute only on Linux platforms svn path=/nixpkgs/trunk/; revision=32410
2012-02-20 00:32:43 +01:00
andyetitmoves = if stdenv.isLinux then callPackage ../games/andyetitmoves {} else null;
and yet it moves: gravity/physics game Demo and commercial version are supported. This nix expression shows some of the techniques used to package closed-source binaries. Committed on behalf of Mathijs Kwik. svn path=/nixpkgs/trunk/; revision=32408
2012-02-19 22:36:54 +01:00
anki: add version 2.0.3
2013-01-04 04:48:47 +01:00
anki = callPackage ../games/anki { };
Adding the game Advanced Strategic Command. I had to add an old version of libsigc++ for it. svn path=/nixpkgs/trunk/; revision=23490
2010-08-29 11:43:46 +02:00
asc = callPackage ../games/asc {
lua = lua5;
libsigcxx = libsigcxx12;
};
added astromenace: Hardcore 3D space shooter
2014-08-02 15:40:51 +02:00
astromenace = callPackage ../games/astromenace { };
Adding atanks svn path=/nixpkgs/trunk/; revision=24893
2010-11-27 20:18:22 +01:00
atanks = callPackage ../games/atanks {};
Prepare for the Guile 2.0 switchover. svn path=/nixpkgs/trunk/; revision=25976
2011-02-15 14:14:29 +01:00
ballAndPaddle = callPackage ../games/ball-and-paddle {
guile = guile_1_8;
};
Add GNU Ball and Paddle, the ultimate game. svn path=/nixpkgs/trunk/; revision=12938
2008-10-04 12:08:59 +02:00
Adding the game Bits&Bots svn path=/nixpkgs/trunk/; revision=32227
2012-02-11 15:33:27 +01:00
bitsnbots = callPackage ../games/bitsnbots {
lua = lua5;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
blackshades = callPackage ../games/blackshades { };
Adding Black Shades svn path=/nixpkgs/trunk/; revision=22520
2010-07-08 00:22:19 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
blackshadeselite = callPackage ../games/blackshadeselite { };
Adding Black Shades Elite (a fork of Black Shades) svn path=/nixpkgs/trunk/; revision=22538
2010-07-08 20:06:01 +02:00
Update Blobby Volley
2014-07-01 09:04:36 +02:00
blobby = callPackage ../games/blobby { };
Adding blobby volleybal svn path=/nixpkgs/trunk/; revision=33810
2012-04-17 15:06:12 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
bsdgames = callPackage ../games/bsdgames { };
Adding bsdgames and miscfiles (this later, for 'words') I could not easily make some bsdgames build or install. Too much patching against the installer trying to write beyond the nix store. svn path=/nixpkgs/trunk/; revision=17971
2009-10-27 00:03:36 +01:00
Adding some skeleton for btanks. It needs smpeg still, to build. svn path=/nixpkgs/trunk/; revision=26554
2011-03-27 23:18:05 +02:00
btanks = callPackage ../games/btanks { };
Adding bzflag. svn path=/nixpkgs/trunk/; revision=26549
2011-03-27 18:35:45 +02:00
bzflag = callPackage ../games/bzflag { };
Castle-Combat: Start fixing; rewrite using `buildPythonPackage'. svn path=/nixpkgs/trunk/; revision=23225
2010-08-18 16:25:07 +02:00
castle_combat = callPackage ../games/castle-combat { };
Add Castle-Combat, a clone of Rampart. svn path=/nixpkgs/trunk/; revision=12978
2008-10-07 00:49:37 +02:00
Add expression for ChessDB
2014-05-26 09:45:59 +02:00
chessdb = callPackage ../games/chessdb { };
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
construoBase = lowPrio (callPackage ../games/construo {
* ltrace: updated to 0.5.3. * libdbi / libdbi-drivers: updated to 0.8.3, and make it compile with SQLite. * qemu-image: fix the URL. * gdmap: make it build again (requires an older GTK+). * rlwrap: updated to 0.37. * smbfs-fuse -> fusesmb to match the upstream name. * x11vnc: updated to 0.9.10. * clearlyU: fix the URL. * Various packages: follow the coding conventions. svn path=/nixpkgs/trunk/; revision=22814
2010-07-29 20:55:16 +02:00
mesa = null;
freeglut = null;
Mark some packages as low priority and disambiguate some others
2012-11-29 15:08:29 +01:00
});
Added PostgreSQL job. svn path=/nixpkgs/trunk/; revision=9831
2007-12-03 05:48:44 +01:00
* composedArgsAndFun -> makeOverridable for consistency. * Rename a few single-version packages to "default.nix". svn path=/nixpkgs/trunk/; revision=22803
2010-07-29 10:21:21 +02:00
construo = construoBase.override {
Added PostgreSQL job. svn path=/nixpkgs/trunk/; revision=9831
2007-12-03 05:48:44 +01:00
inherit mesa freeglut;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
* Fixed Stratego. * Added Zoom, an interpreter for Z-Code. svn path=/nixpkgs/trunk/; revision=894
2004-04-01 18:02:53 +02:00
Adding crack-attack (patch sent by Piotr Pietraszkiewicz) svn path=/nixpkgs/trunk/; revision=23987
2010-09-29 00:37:27 +02:00
crack_attack = callPackage ../games/crack-attack { };
crafty: simplify expression
2014-06-07 14:16:20 +02:00
crafty = callPackage ../games/crafty { };
Add expression for building crafty and craftyFull
2014-05-27 19:57:50 +02:00
craftyFull = appendToName "full" (crafty.override { fullVariant = true; });
Adding crrcsim model airplane flight simulator svn path=/nixpkgs/trunk/; revision=24931
2010-11-29 22:12:53 +01:00
crrcsim = callPackage ../games/crrcsim {};
dhewm3: add current master from github This is a port of the Doom 3 source code released under GPL. Amongst others, this makes use of SDL to be multiplatform, and supports amd64.
2013-04-01 17:56:34 +02:00
dhewm3 = callPackage ../games/dhewm3 {};
Add rncbc's Vee One suite: sampler, synth and drum kit
2013-03-06 01:06:16 +01:00
drumkv1 = callPackage ../applications/audio/drumkv1 { };
dwarf-fortress: Update to 0.34.11. Somehow Dwarf Fortress suddenly started failing to use our libpng (or zlib). I tried all possible combinations (supplying them via LD_LIBRARY_PATH in the script) but it just won't work. This solution was found in the Archlinux bug tracker: It just symlinks all problematic .png files to their .bmp counterparts. It's ugly and *sadly* breaks tileset support (unless you convert them to bmp) but I think it's acceptable, as the whole expression is pretty problematic in terms of purity. Let's hope the next release of Dwarf Fortress will be easier to support. (fixes #710)
2013-05-01 14:29:57 +02:00
dwarf_fortress = callPackage_i686 ../games/dwarf-fortress {
SDL_image = pkgsi686Linux.SDL_image.override {
libpng = pkgsi686Linux.libpng12;
};
};
Add dwarf fortress 2014 (unstable) version
2014-07-24 04:41:30 +02:00
dwarf_fortress_2014 = callPackage_i686 ../games/dwarf-fortress/df2014.nix {
SDL_image = pkgsi686Linux.SDL_image.override {
libpng = pkgsi686Linux.libpng12;
};
};
dwarf-fortress: Update to 0.34.11. Somehow Dwarf Fortress suddenly started failing to use our libpng (or zlib). I tried all possible combinations (supplying them via LD_LIBRARY_PATH in the script) but it just won't work. This solution was found in the Archlinux bug tracker: It just symlinks all problematic .png files to their .bmp counterparts. It's ugly and *sadly* breaks tileset support (unless you convert them to bmp) but I think it's acceptable, as the whole expression is pretty problematic in terms of purity. Let's hope the next release of Dwarf Fortress will be easier to support. (fixes #710)
2013-05-01 14:29:57 +02:00
dwarf_fortress_modable = appendToName "moddable" (dwarf_fortress.override {
copyDataDirectory = true;
});
Dwarf Fortress The wrapper script works by creating an image of the distribution in the users home directory (defaulting to $HOME/.config/df_linux). This is done because the program expects to write state into it's own distribution. Better ideas are welcome! What further is needed is to allow users to configure the init. One way is to use nix-config to apply patches to the init.txt file, though this would break sharing of the package between different users. svn path=/nixpkgs/trunk/; revision=24538
2010-10-30 08:00:44 +02:00
Add dwarf fortress 2014 (unstable) version
2014-07-24 04:41:30 +02:00
dwarf_fortress_2014_modable = appendToName "moddable" (dwarf_fortress_2014.override {
copyDataDirectory = true;
});
dwarf-therapist: New package Dwarf Therapist is a tool to manage your Dwarves' work orders and other management stuff. Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
2013-10-10 01:15:16 +02:00
dwarf-therapist = callPackage ../games/dwarf-therapist { };
Dwarf Fortress The wrapper script works by creating an image of the distribution in the users home directory (defaulting to $HOME/.config/df_linux). This is done because the program expects to write state into it's own distribution. Better ideas are welcome! What further is needed is to allow users to configure the init. One way is to use nix-config to apply patches to the init.txt file, though this would break sharing of the package between different users. svn path=/nixpkgs/trunk/; revision=24538
2010-10-30 08:00:44 +02:00
Adding d1x-rebirth, Descent 1 source port.
2013-04-05 22:53:12 +02:00
d1x_rebirth = callPackage ../games/d1x-rebirth { };
Adding d2x-rebirth, source port of the Descent 2 engine
2013-04-05 22:58:43 +02:00
d2x_rebirth = callPackage ../games/d2x-rebirth { };
Add expression to build the eboard chess client
2014-05-25 10:21:21 +02:00
eboard = callPackage ../games/eboard { };
Remove gcc 4.7 There is really no reason to keep it around, given that it was never the default in Nixpkgs.
2014-01-07 10:36:15 +01:00
eduke32 = callPackage ../games/eduke32 { };
Added EDuke32 package to celebrate the moment that 3DRealms is dead and Duke Nukem Forever is never going to be released svn path=/nixpkgs/trunk/; revision=15601
2009-05-14 15:48:45 +02:00
Adding a more-or-less working 'egoboo'. I'll update to a better expression after some egoboo upstream work. svn path=/nixpkgs/trunk/; revision=23408
2010-08-24 21:36:42 +02:00
egoboo = callPackage ../games/egoboo { };
exult: Update to 1.4.9rc1
2014-07-22 14:51:05 +02:00
exult = callPackage ../games/exult { };
add scummvm (scummvm.sf.net) svn path=/nixpkgs/trunk/; revision=6079
2006-08-09 01:39:03 +02:00
flightgear: fix build via update; but no testing, hope it works
2013-02-23 20:32:12 +01:00
flightgear = callPackage ../games/flightgear { };
Adding FlightGear svn path=/nixpkgs/trunk/; revision=26770
2011-04-09 20:57:00 +02:00
Add game freeciv. svn path=/nixpkgs/trunk/; revision=28711
2011-08-20 16:30:16 +02:00
freeciv = callPackage ../games/freeciv { };
Adding an attribute for the gtk freeciv too.
2013-10-20 18:26:32 +02:00
freeciv_gtk = callPackage ../games/freeciv {
gtkClient = true;
sdlClient = false;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
freedink = callPackage ../games/freedink { };
Add GNU FreeDink. svn path=/nixpkgs/trunk/; revision=21555
2010-05-02 11:27:51 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
fsg = callPackage ../games/fsg {
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
wxGTK = wxGTK28.override { unicode = false; };
Added a new setup proposal, builder is no more derived from shell script (where edit=glibc rebuild), but is composed from a nix attribute set with strings and dependencies - so if you add a function, old expressions ignore it; collateral damage are packages in this style: Fastest Fourier Transform in the West, Audacity sound editor, Falling Sand game. Also added string equality that ignores dependencies to lib. Note that hasSuffixHack is now the more predictable version, but hasSuffix is left to remind us to fix the bug. svn path=/nixpkgs/trunk/; revision=9549
2007-10-29 11:52:04 +01:00
};
Added Falling Sand Game and wxGTK without unicode for it. svn path=/nixpkgs/trunk/; revision=9543
2007-10-27 19:55:13 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gemrb = callPackage ../games/gemrb { };
Adding GL-117 svn path=/nixpkgs/trunk/; revision=24930
2010-11-29 21:51:09 +01:00
gl117 = callPackage ../games/gl-117 {};
Adding Glest Advanced Engine into all-packages svn path=/nixpkgs/trunk/; revision=26920
2011-04-22 12:26:45 +02:00
glestae = callPackage ../games/glestae {};
Adding globulation svn path=/nixpkgs/trunk/; revision=26892
2011-04-19 18:02:29 +02:00
globulation2 = callPackage ../games/globulation {};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gltron = callPackage ../games/gltron { };
* Added GemRB, a reimplementation of the Infinity Engine. svn path=/nixpkgs/trunk/; revision=8695
2007-05-14 23:47:11 +02:00
Fixing gnuchess build svn path=/nixpkgs/branches/stdenv-updates/; revision=25270
2010-12-24 06:47:55 +01:00
gnuchess = callPackage ../games/gnuchess { };
Added GNU Chess and XBoard svn path=/nixpkgs/trunk/; revision=13923
2009-01-31 21:09:54 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gnugo = callPackage ../games/gnugo { };
Three Games and Perl Support for Irssi Here are four patches. Three of them add expressions for games. The fourth, irssi-perl.patch, adds perl as an input for irssi, so that one can run perl plugins in irssi. I didn't make the perl input optional, but maybe it should be to keep the irssi expression light. svn path=/nixpkgs/trunk/; revision=21813
2010-05-17 11:21:42 +02:00
gparted: upgrade, use newer parted, clean expression
2013-02-14 13:13:10 +01:00
gparted = callPackage ../tools/misc/gparted { };
adding gparted. qparted is no longer maintained (?) svn path=/nixpkgs/trunk/; revision=17016
2009-09-10 18:57:21 +02:00
added gsmartcontrol 0.8.7 to nixpkgs
2012-10-12 02:45:42 +02:00
gsmartcontrol = callPackage ../tools/misc/gsmartcontrol {
inherit (gnome) libglademm;
};
gtypist, typing tutor Now all I need is time to practise :) svn path=/nixpkgs/trunk/; revision=33228
2012-03-18 09:11:17 +01:00
gtypist = callPackage ../games/gtypist { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
hexen = callPackage ../games/hexen { };
Adding the simple port of hexen. svn path=/nixpkgs/trunk/; revision=15046
2009-04-15 00:25:14 +02:00
Adding the videogame icbm3d svn path=/nixpkgs/trunk/; revision=27499
2011-06-19 23:46:45 +02:00
icbm3d = callPackage ../games/icbm3d { };
add ingen: A modular audio processing system using JACK and LV2 or LADSPA
2014-03-09 20:32:06 +01:00
ingen = callPackage ../applications/audio/ingen { };
Adding the game engine 'instead' and some games. svn path=/nixpkgs/trunk/; revision=24009
2010-09-30 20:58:48 +02:00
instead = callPackage ../games/instead {
lua = lua5;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
kobodeluxe = callPackage ../games/kobodeluxe { };
Adding Kobo Deluxe. svn path=/nixpkgs/trunk/; revision=15045
2009-04-15 00:25:03 +02:00
Added lincity - a city simulation. And if I build houses, I build houses here. svn path=/nixpkgs/trunk/; revision=12539
2008-08-08 09:16:34 +02:00
lincity = builderDefsPackage (import ../games/lincity) {
bison: use version 2.3 by default (the latest) svn path=/nixpkgs/trunk/; revision=12703
2008-08-25 15:25:07 +02:00
inherit (xlibs) libX11 libXext xextproto
Added lincity - a city simulation. And if I build houses, I build houses here. svn path=/nixpkgs/trunk/; revision=12539
2008-08-08 09:16:34 +02:00
libICE libSM xproto;
inherit libpng zlib;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
Added lincity - a city simulation. And if I build houses, I build houses here. svn path=/nixpkgs/trunk/; revision=12539
2008-08-08 09:16:34 +02:00
Add Lincity-NG fork
2012-11-30 19:59:26 +01:00
lincity_ng = callPackage ../games/lincity/ng.nix {};
games/mars: New nixpkg. svn path=/nixpkgs/trunk/; revision=26434
2011-03-20 19:24:39 +01:00
mars = callPackage ../games/mars { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
micropolis = callPackage ../games/micropolis { };
all-packages.nix: drop trailing whitespace
2014-04-11 10:06:06 +02:00
mnemosyne = callPackage ../games/mnemosyne {
Mnemosyne: provide capacity to override dependencies at the fidelity of a Python package.
2014-03-25 17:37:05 +01:00
inherit (pythonPackages) matplotlib cherrypy sqlite3;
};
Added: * dmenu * gftp * micropolis * byacc as a build-time dependency for micropolis contributed by baldo <baldo@quimby.lan> svn path=/nixpkgs/trunk/; revision=12526
2008-08-06 22:39:01 +02:00
Adding the videogame Naev (beta version, because they label the non-beta 'deprecated') svn path=/nixpkgs/trunk/; revision=27017
2011-04-27 23:57:27 +02:00
naev = callPackage ../games/naev { };
Added Nexuiz-2.5.2.
2014-01-01 17:59:42 +01:00
nexuiz = callPackage ../games/nexuiz { };
Adding the pacman-like game njam. svn path=/nixpkgs/trunk/; revision=26553
2011-03-27 22:35:08 +02:00
njam = callPackage ../games/njam { };
games/oilrush: New nixpkg. svn path=/nixpkgs/trunk/; revision=31925
2012-01-29 23:44:49 +01:00
oilrush = callPackage ../games/oilrush { };
Merge #2030: add openra game (C&C RTS engine) Modifications from @vcunat, who tried Dune, but it typically segfaults in mono after a few minutes (IMHO unlikely to be a problem with packaging it).
2014-04-06 17:01:34 +02:00
openra = callPackage ../games/openra { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
openttd = callPackage ../games/openttd {
Add new game: openttd. svn path=/nixpkgs/trunk/; revision=11553
2008-04-11 00:12:20 +02:00
zlib = zlibStatic;
};
Add opentyrian game. svn path=/nixpkgs/trunk/; revision=33797
2012-04-16 01:38:38 +02:00
opentyrian = callPackage ../games/opentyrian { };
openxcom: add version 1.0.0
2014-06-14 11:58:00 +02:00
openxcom = callPackage ../games/openxcom { };
Add Pingus
2012-12-01 21:18:42 +01:00
pingus = callPackage ../games/pingus {};
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
pioneers = callPackage ../games/pioneers { };
Adding the game 'pioneers' svn path=/nixpkgs/trunk/; revision=19769
2010-02-02 23:21:56 +01:00
Adding 3dpong. svn path=/nixpkgs/trunk/; revision=27498
2011-06-19 23:33:31 +02:00
pong3d = callPackage ../games/pong3d { };
Fixing the gcc-cross-wrapper; it failed after some changes related to breaking dependencies with it. (I should never link ld.so with a NIX_LDFLAGS -rpath forced) I made vim, scummvm cross-build. I added prboom (that cross-builds). Mplayer and elinks don't cross-build fine still, but are on the way. The mplayer fails to build in a weird way; nix does not show either a gcc error message or even the 'make' error message. svn path=/nixpkgs/branches/stdenv-updates/; revision=23131
2010-08-11 22:14:25 +02:00
prboom = callPackage ../games/prboom { };
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
quake3demo = callPackage ../games/quake3/wrapper {
* ioquake: updated to 1.34rc3. * rss-glx: fixed the build. * Removed the OpenGL wrapper stuff, it's no longer needed (thanks to the RUNPATH you just need to put the appropriate libGL.so in the LD_LIBRARY_PATH). svn path=/nixpkgs/trunk/; revision=12093
2008-06-14 22:55:48 +02:00
name = "quake3-demo-${quake3game.name}";
* Added a bunch of descriptions. svn path=/nixpkgs/trunk/; revision=6705
2006-10-11 18:45:55 +02:00
description = "Demo of Quake 3 Arena, a classic first-person shooter";
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
game = quake3game;
paks = [quake3demodata];
* Added basic Quake 3. Some wrapper stuff is still needed to get it to work "out of the box" with hardware acceleration and either the shareware or full PAK files. But with some hackery, I have gotten it to work with both Mesa software rendering and NVidia hardware rendering. svn path=/nixpkgs/trunk/; revision=4595
2006-01-26 15:43:05 +01:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
quake3demodata = callPackage ../games/quake3/demo { };
* Get the Quake 3 demo data to work with the open source Quake 3. quake3/demo takes care of downloading and patching the required PAK files. quake3/wrapper calls the Quake binary with a synthesised directory of symlinks to activated PAK files. This should make it easy to plug in the commercial PAKs, or third-party mods. svn path=/nixpkgs/trunk/; revision=4611
2006-01-28 00:51:36 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
quake3game = callPackage ../games/quake3/game { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Adding Quantum Minigolf game
2013-10-27 21:09:46 +01:00
quantumminigolf = callPackage ../games/quantumminigolf {};
Adding the game 'racer'. It works only in i686-linux. svn path=/nixpkgs/trunk/; revision=26520
2011-03-26 00:33:09 +01:00
racer = callPackage ../games/racer { };
Merge remote-tracking branch 'origin/master' into stdenv-updates. Conflicts: pkgs/top-level/all-packages.nix
2013-10-26 18:28:05 +02:00
residualvm = callPackage ../games/residualvm {
openglSupport = mesaSupported;
package residualvm 0.1.1 ResidualVM is an interpreter for LucasArts' Lua-based 3D adventure games like Grim Fandango. From: #1118.
2013-10-25 13:12:31 +02:00
};
Adding Rigs of Rods. Basically it builds, but I still don't know how to run it. I imagine the installPhase is still too poor, but it's better than nothing. I also added two mygui versions. That stable, and that required by Rigs of Roads (svn). svn path=/nixpkgs/trunk/; revision=26618
2011-03-31 00:08:33 +02:00
rigsofrods = callPackage ../games/rigsofrods {
mygui = myguiSvn;
};
lxc: fix documentation build and make version 0.8.0-rc2 the default
2012-10-20 12:10:28 +02:00
rili = callPackage ../games/rili { };
- openttd 1.2.2, rili 2.0.1, widelands-build17, uqm-0.7.0
2012-10-05 08:32:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rogue = callPackage ../games/rogue { };
* Now Nixpkgs is officially complete. svn path=/nixpkgs/trunk/; revision=7573
2007-01-08 22:19:15 +01:00
Add rncbc's Vee One suite: sampler, synth and drum kit
2013-03-06 01:06:16 +01:00
samplv1 = callPackage ../applications/audio/samplv1 { };
Adding sauerbraten svn path=/nixpkgs/trunk/; revision=25278
2010-12-26 14:14:15 +01:00
sauerbraten = callPackage ../games/sauerbraten {};
scid: New package, version 4.3. Just saw Michael Raskin's GNU Chess and XBoard updates and did a short check if Scid is already in nixpkgs. It wasn't, so I decided to add it, so thanks to @7c6f434c :-) The package involves a lot of patching, as usual with Tcl/Tk on NixOS. In this case the program is written in C++ and embeds the Tcl/Wish interpreter. Unfortunately this doesn't make it easier to inject TCLLIBPATH, as there doesn't seem to be a direct library call (well in theory you could `lappend TCLLIBPATH`, but that won't help with TK_LIBRARY). Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2012-12-12 10:39:35 +01:00
scid = callPackage ../games/scid { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
scummvm = callPackage ../games/scummvm { };
* Unreal Tournament 2004 Demo. Also a binary-only component. An interesting complication is that we have to change the ELF type of the executable from `Linux' to `SVR4', otherwise the `ld-linux.so.2' trick to override the glibc used doesn't work (apparently `Linux' is not a recognised ELF type!). UT doesn't work with software Mesa, so right now we impurily use `/usr/lib/libGL.so'. I cannot really test whether it works with hardware Mesa, since it barfs with an error about missing OpenGL extensions. But that's probably because I'm testing this on an iBook over an SSH connection to a Linux machine. svn path=/nixpkgs/trunk/; revision=1047
2004-06-09 20:06:29 +02:00
Minor cleanup
2012-11-29 14:40:25 +01:00
scorched3d = callPackage ../games/scorched3d { };
Added Scorched3D. svn path=/nixpkgs/trunk/; revision=15108
2009-04-17 00:50:36 +02:00
sdlmame: add expression
2013-10-12 02:31:46 +02:00
sdlmame = callPackage ../games/sdlmame { };
all-packages.nix changes for my last commits svn path=/nixpkgs/trunk/; revision=13693
2009-01-03 14:44:04 +01:00
sgtpuzzles = builderDefsPackage (import ../games/sgt-puzzles) {
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
inherit pkgconfig fetchsvn perl gtk;
all-packages.nix changes for my last commits svn path=/nixpkgs/trunk/; revision=13693
2009-01-03 14:44:04 +01:00
inherit (xlibs) libX11;
};
Add expression for the simutrans game. svn path=/nixpkgs/trunk/; revision=26523
2011-03-26 08:22:24 +01:00
simutrans = callPackage ../games/simutrans { };
Adding Sphere of Influence svn path=/nixpkgs/trunk/; revision=25711
2011-01-28 09:13:52 +01:00
soi = callPackage ../games/soi {};
Added Orbit space flight simulation. Unfortunately, it doesn't feature gravity. svn path=/nixpkgs/trunk/; revision=10249
2008-01-22 18:56:53 +01:00
# You still can override by passing more arguments.
Stop using ESound for space-orbit svn path=/nixpkgs/trunk/; revision=31429
2012-01-07 22:59:16 +01:00
spaceOrbit = callPackage ../games/orbit { };
Added Orbit space flight simulation. Unfortunately, it doesn't feature gravity. svn path=/nixpkgs/trunk/; revision=10249
2008-01-22 18:56:53 +01:00
spring: bump and fix build
2013-03-29 16:43:38 +01:00
spring = callPackage ../games/spring { };
Spring RTS: packaged along with its deps and utils: libDevIL, libtorrent-rasterbar, spring-lobby. svn path=/nixpkgs/trunk/; revision=24681
2010-11-13 08:47:04 +01:00
updated springlobby to 141 and changed the name of the package svn path=/nixpkgs/trunk/; revision=32896
2012-03-08 16:32:20 +01:00
springLobby = callPackage ../games/spring/springlobby.nix { };
Spring RTS: packaged along with its deps and utils: libDevIL, libtorrent-rasterbar, spring-lobby. svn path=/nixpkgs/trunk/; revision=24681
2010-11-13 08:47:04 +01:00
Add stardust svn path=/nixpkgs/trunk/; revision=24905
2010-11-28 14:16:47 +01:00
stardust = callPackage ../games/stardust {};
steam: revert adding amd64 version. It turns out that the .deb only contains the changelog and some other docs. Revert back to using the i686 version, but keep the double url for the future.
2013-02-19 20:52:19 +01:00
steam = callPackage_i686 ../games/steam {};
all-packages.nix: string trailing whitespace
2013-09-16 10:59:39 +02:00
My attempt to get Steam working in NixOS. It uses a function called buildFHSChrootEnv {} that composed chroot environments. In such a chroot environment, I could run Steam without much problem
2013-09-13 23:58:59 +02:00
steamChrootEnv = callPackage_i686 ../games/steam/chrootenv.nix {
zenity = gnome2.zenity;
};
Steam: first attempt at adding the beta client. The script installed with this expression only copies a boostrapper and another script to the user's home folder. Those also need to be patched to get on with the installation.
2012-12-08 11:52:54 +01:00
Adding stunt rally. svn path=/nixpkgs/trunk/; revision=32217
2012-02-10 21:24:13 +01:00
stuntrally = callPackage ../games/stuntrally { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
superTux = callPackage ../games/super-tux { };
Three Games and Perl Support for Irssi Here are four patches. Three of them add expressions for games. The fourth, irssi-perl.patch, adds perl as an input for irssi, so that one can run perl plugins in irssi. I didn't make the perl input optional, but maybe it should be to keep the irssi expression light. svn path=/nixpkgs/trunk/; revision=21813
2010-05-17 11:21:42 +02:00
supertuxkart: updating to 0.8
2013-01-10 20:55:46 +01:00
superTuxKart = callPackage ../games/super-tux-kart { };
Super Tux Kart, a free kart racing game. svn path=/nixpkgs/trunk/; revision=13052
2008-10-12 16:28:51 +02:00
Add rncbc's Vee One suite: sampler, synth and drum kit
2013-03-06 01:06:16 +01:00
synthv1 = callPackage ../applications/audio/synthv1 { };
Adding tbe game svn path=/nixpkgs/trunk/; revision=25178
2010-12-17 16:41:30 +01:00
tbe = callPackage ../games/the-butterfly-effect {};
Adding the videogame teeter torture. svn path=/nixpkgs/trunk/; revision=27500
2011-06-20 00:25:52 +02:00
teetertorture = callPackage ../games/teetertorture { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
teeworlds = callPackage ../games/teeworlds { };
Add Teeworlds, a Worms-like game, if you see what I mean. svn path=/nixpkgs/trunk/; revision=13762
2009-01-13 20:44:11 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tennix = callPackage ../games/tennix { };
Adding (quite blindly) some gnome packages to get gnucash built. svn path=/nixpkgs/trunk/; revision=19758
2010-02-01 20:55:03 +01:00
tibia: version 10.38 Closes #2396
2014-04-25 20:35:18 +02:00
tibia = callPackage ../games/tibia { };
tintin: add expression
2013-11-29 00:36:30 +01:00
tintin = callPackage ../games/tintin { };
Fixing libcgroup attribute name svn path=/nixpkgs/trunk/; revision=25229
2010-12-22 10:52:32 +01:00
tpm = callPackage ../games/thePenguinMachine { };
Added pygame and some of its dependencies. Also added Python Imaging library. svn path=/nixpkgs/trunk/; revision=9082
2007-08-09 19:33:18 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
tremulous = callPackage ../games/tremulous { };
games/tremulous: New nixpkg. svn path=/nixpkgs/trunk/; revision=22413
2010-06-25 17:09:53 +02:00
Adding Speed Dreams (a TORCS fork) svn path=/nixpkgs/trunk/; revision=26673
2011-04-04 07:01:53 +02:00
speed_dreams = callPackage ../games/speed-dreams {
# Torcs wants to make shared libraries linked with plib libraries (it provides static).
# i686 is the only platform I know than can do that linking without plib built with -fPIC
Clean up redundant "if condition then true else false"
2012-12-28 19:57:47 +01:00
plib = plib.override { enablePIC = !stdenv.isi686; };
speed dreams: fixing the build (libpng version)
2012-07-02 20:38:57 +02:00
libpng = libpng12;
Adding Speed Dreams (a TORCS fork) svn path=/nixpkgs/trunk/; revision=26673
2011-04-04 07:01:53 +02:00
};
Adding torcs svn path=/nixpkgs/trunk/; revision=23354
2010-08-22 16:18:58 +02:00
torcs = callPackage ../games/torcs {
# Torcs wants to make shared libraries linked with plib libraries (it provides static).
# i686 is the only platform I know than can do that linking without plib built with -fPIC
Clean up redundant "if condition then true else false"
2012-12-28 19:57:47 +01:00
plib = plib.override { enablePIC = !stdenv.isi686; };
Adding torcs svn path=/nixpkgs/trunk/; revision=23354
2010-08-22 16:18:58 +02:00
};
Adding the rally game Trigger. As a side effect, I add jam. svn path=/nixpkgs/trunk/; revision=26615
2011-03-30 20:45:11 +02:00
trigger = callPackage ../games/trigger { };
Working on adding typespeed.
2014-06-04 05:55:32 +02:00
typespeed = callPackage ../games/typespeed { };
Update ufoai to 2.4, clean dependencies and the expression.
2013-01-22 14:56:01 +01:00
ufoai = callPackage ../games/ufoai { };
Adding the game UFO: Alien Invasion. svn path=/nixpkgs/trunk/; revision=23488
2010-08-29 02:45:29 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ultimatestunts = callPackage ../games/ultimatestunts { };
Adding Ultimate Stunts, a racing game. svn path=/nixpkgs/trunk/; revision=19088
2009-12-23 23:28:50 +01:00
Trying to add ultrastardx. It fails for me in x86_64. I invite others to test or fix it, as I know zero about fpc. svn path=/nixpkgs/trunk/; revision=25305
2010-12-28 15:56:08 +01:00
ultrastardx = callPackage ../games/ultrastardx {
Fixing the Ultrastardx build. Not tested if it works and how.
2013-12-07 00:07:04 +01:00
ffmpeg = ffmpeg_0_6;
Trying to add ultrastardx. It fails for me in x86_64. I invite others to test or fix it, as I know zero about fpc. svn path=/nixpkgs/trunk/; revision=25305
2010-12-28 15:56:08 +01:00
lua = lua5;
};
games/unvanquished: New nixpkg.
2013-02-24 15:02:53 +01:00
unvanquished = callPackage ../games/unvanquished { };
- openttd 1.2.2, rili 2.0.1, widelands-build17, uqm-0.7.0
2012-10-05 08:32:34 +02:00
uqm = callPackage ../games/uqm { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
urbanterror = callPackage ../games/urbanterror { };
games/urbanterror: New nixpkg for viric. svn path=/nixpkgs/trunk/; revision=19770
2010-02-03 01:46:43 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ut2004demo = callPackage ../games/ut2004demo { };
* Quake 3 Arena Demo. The goal is to show that Nix can also be used to deploy existing binary-only components. We use the `ld-linux.so.2 PROGRAM' trick to force the use of our own glibc, and set LD_LIBRARY_PATH to point to the required libraries (X11, Mesa). Since Mesa is software-only, Q3A is rather slow. I'll have to figure out how to use the Mesa from XFree86 (X.Org), since it knows how to use DRI (or at least speak the GLX protocol). Unfortunately the xlibs people haven't modularised that part of XFree86 yet. Also, the flag `+set s_initsound 0' has to be passed to Quake to disable sound, otherwise it segfaults on startup. It doesn't do this with the normal glibc, which is strange. Maybe it tries to dynamically load some sound library or something. svn path=/nixpkgs/trunk/; revision=1046
2004-06-09 19:59:46 +02:00
Adding the racing videogame VDrift. I added the asio library as a side effect. svn path=/nixpkgs/trunk/; revision=26575
2011-03-28 18:08:21 +02:00
vdrift = callPackage ../games/vdrift { };
Adding the videogame Vectoroids. svn path=/nixpkgs/trunk/; revision=27497
2011-06-19 23:07:35 +02:00
vectoroids = callPackage ../games/vectoroids { };
add Vessel, a fluid physics puzzle game.
2012-12-17 08:24:31 +01:00
vessel = callPackage_i686 ../games/vessel { };
Adding the racing videogame VDrift. I added the asio library as a side effect. svn path=/nixpkgs/trunk/; revision=26575
2011-03-28 18:08:21 +02:00
warmux = callPackage ../games/warmux { };
Adding warmux svn path=/nixpkgs/trunk/; revision=25997
2011-02-16 23:19:59 +01:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
warsow = callPackage ../games/warsow {
games/warsow: Needs libjpeg62. svn path=/nixpkgs/trunk/; revision=19891
2010-02-10 00:12:47 +01:00
libjpeg = libjpeg62;
games/warsow: New package. svn path=/nixpkgs/trunk/; revision=19718
2010-01-27 23:22:35 +01:00
};
Making the current versions of flex/bison the default. Evaluation test passes. Please explicitly pass older versions to any package that can be adversely affected by too-fresh versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=25086
2010-12-12 22:48:29 +01:00
warzone2100 = callPackage ../games/warzone2100 { };
warzone2100: New nixpkg. svn path=/nixpkgs/trunk/; revision=21582
2010-05-03 18:07:01 +02:00
Pass libpng-1.2 to widelands svn path=/nixpkgs/branches/libpng15/; revision=32405
2012-02-19 18:39:37 +01:00
widelands = callPackage ../games/widelands {
widelands: update to build-18 (close #2062) @vcunat enabled parallelBuilding.
2014-03-29 16:10:03 +01:00
lua = lua5_1;
Pass libpng-1.2 to widelands svn path=/nixpkgs/branches/libpng15/; revision=32405
2012-02-19 18:39:37 +01:00
};
Add Widelands RTS svn path=/nixpkgs/trunk/; revision=26869
2011-04-17 19:55:29 +02:00
World of Goo 1.41.
2012-11-28 23:38:46 +01:00
worldofgoo_demo = callPackage ../games/worldofgoo {
demo = true;
};
worldofgoo = callPackage ../games/worldofgoo { };
XBoard: update to 4.6.2
2012-12-12 06:29:49 +01:00
xboard = callPackage ../games/xboard { };
Added GNU Chess and XBoard svn path=/nixpkgs/trunk/; revision=13923
2009-01-31 21:09:54 +01:00
Adding Xconq turn-based strategy svn path=/nixpkgs/trunk/; revision=27306
2011-05-28 17:36:56 +02:00
xconq = callPackage ../games/xconq {};
all-packages.nix: disable 'xracer' attribute to fix evaluation errors on Hydra svn path=/nixpkgs/trunk/; revision=28135
2011-08-03 10:43:52 +02:00
# TODO: the corresponding nix file is missing
# xracer = callPackage ../games/xracer { };
Adding mairix svn path=/nixpkgs/trunk/; revision=28122
2011-08-02 16:26:47 +02:00
games/xonotic: New nixbuild. svn path=/nixpkgs/trunk/; revision=30260
2011-11-06 14:54:03 +01:00
xonotic = callPackage ../games/xonotic { };
xskat: new package Play the german card game Skat against the AI or over IRC.
2014-08-23 17:09:11 +02:00
xskat = callPackage ../games/xskat { };
Added XSokoban svn path=/nixpkgs/trunk/; revision=13737
2009-01-11 23:05:19 +01:00
xsokoban = builderDefsPackage (import ../games/xsokoban) {
inherit (xlibs) libX11 xproto libXpm libXt;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
zdoom = callPackage ../games/zdoom { };
Adding zdoom. svn path=/nixpkgs/trunk/; revision=14194
2009-02-22 23:06:34 +01:00
Adding the zod engine, a multiplayer zed remake. svn path=/nixpkgs/trunk/; revision=26577
2011-03-28 18:08:29 +02:00
zod = callPackage ../games/zod { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
zoom = callPackage ../games/zoom { };
* Latest ALSA, SDL. svn path=/nixpkgs/trunk/; revision=6500
2006-09-12 01:06:26 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
keen4 = callPackage ../games/keen4 { };
* An example of supporting legacy applications using dosbox ;-) svn path=/nixpkgs/trunk/; revision=6895
2006-10-29 00:28:35 +02:00
Add 0 A.D.
2014-06-18 23:18:53 +02:00
zeroad = callPackage ../games/0ad { };
* Fixed Stratego. * Added Zoom, an interpreter for Z-Code. svn path=/nixpkgs/trunk/; revision=894
2004-04-01 18:02:53 +02:00
* Refactoring: move KDE and Gnome out of development/libraries into desktops. svn path=/nixpkgs/trunk/; revision=8105
2007-02-28 17:18:58 +01:00
### DESKTOP ENVIRONMENTS
cinnamon: various fixes cinnamon-translations: use $out/share instead of $out/usr/share, add version into name all-packages.nix: refactor
2013-12-07 14:27:21 +01:00
cinnamon = recurseIntoAttrs rec {
callPackage = newScope pkgs.cinnamon;
new package: muffin
2014-04-19 10:20:56 +02:00
inherit (gnome3) gnome_common libgnomekbd gnome-menus zenity;
all-packages.nix: strip trailing whitespace
2014-05-04 14:39:40 +02:00
new package: muffin
2014-04-19 10:20:56 +02:00
muffin = callPackage ../desktops/cinnamon/muffin.nix { } ;
all-packages.nix: strip trailing whitespace
2014-05-04 14:39:40 +02:00
new package: cinnamon-control-center
2014-04-13 21:46:48 +02:00
cinnamon-control-center = callPackage ../desktops/cinnamon/cinnamon-control-center.nix{ };
all-packages.nix: strip trailing whitespace
2014-05-04 14:39:40 +02:00
new package: cinnamon-settings-daemon (close #2205) With tiny changes from @vcunat.
2014-04-13 11:19:02 +02:00
cinnamon-settings-daemon = callPackage ../desktops/cinnamon/cinnamon-settings-daemon.nix{ };
add cinnamon-desktop (close #1314) Reviewed and refactored by @vcunat.
2013-12-02 08:58:56 +01:00
added cinnamon-session.nix
2013-12-08 21:40:52 +01:00
cinnamon-session = callPackage ../desktops/cinnamon/cinnamon-session.nix{ } ;
added cinnamon-session
2013-12-07 20:00:54 +01:00
cinnamon: various fixes cinnamon-translations: use $out/share instead of $out/usr/share, add version into name all-packages.nix: refactor
2013-12-07 14:27:21 +01:00
cinnamon-desktop = callPackage ../desktops/cinnamon/cinnamon-desktop.nix { };
cinnamon-translations = callPackage ../desktops/cinnamon/cinnamon-translations.nix { };
cjs = callPackage ../desktops/cinnamon/cjs.nix { };
merge #1309: add cjs -- JavaScript bindings for cinnamon I also fixed whitespace around.
2013-11-30 22:47:57 +01:00
};
* Refactoring: move KDE and Gnome out of development/libraries into desktops. svn path=/nixpkgs/trunk/; revision=8105
2007-02-28 17:18:58 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
enlightenment = callPackage ../desktops/enlightenment { };
Enlightenment 0.16.8.15. Patch by John Altobelli <acocaracha@gmail.com>, minor edits by Ludovic Courtès <ludo@gnu.org>. svn path=/nixpkgs/trunk/; revision=13823
2009-01-22 23:46:39 +01:00
all-packages.nix: Uncomment e17.
2013-02-16 18:56:17 +01:00
e17 = recurseIntoAttrs (
let callPackage = newScope pkgs.e17; in
import ../desktops/e17 { inherit callPackage pkgs; }
);
desktops/e17: Add e17. WIP. Make hangs during build of enlightenment. svn path=/nixpkgs/trunk/; revision=29506
2011-09-27 00:28:35 +02:00
e18: enlightenment desktop manager version 18
2014-03-18 23:04:33 +01:00
e18 = recurseIntoAttrs (
let callPackage = newScope pkgs.e18; in
import ../desktops/e18 { inherit callPackage pkgs; }
);
Move libsoup to development/libraries It is used in many packages outside of gnome2 set. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33197
2012-03-17 17:45:37 +01:00
gnome2 = callPackage ../desktops/gnome-2 {
gnome: use callPackage, move to gnome-2 gnome28 was a mix of packages from various releases, so do not mention 2.28 in the attribute name. svn path=/nixpkgs/trunk/; revision=29721
2011-10-08 18:58:32 +02:00
callPackage = pkgs.newScope pkgs.gnome2;
self = pkgs.gnome2;
Move libsoup to development/libraries It is used in many packages outside of gnome2 set. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33197
2012-03-17 17:45:37 +01:00
} // pkgs.gtkLibs // {
# Backwards compatibility;
Move libwnck to top-level svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33253
2012-03-19 05:36:47 +01:00
inherit (pkgs) libsoup libwnck gtk_doc gnome_doc_utils;
Move libsoup to development/libraries It is used in many packages outside of gnome2 set. svn path=/nixpkgs/branches/glib-2.30-take2/; revision=33197
2012-03-17 17:45:37 +01:00
};
* Refactoring: move KDE and Gnome out of development/libraries into desktops. svn path=/nixpkgs/trunk/; revision=8105
2007-02-28 17:18:58 +01:00
Branch gnome 3.12
2014-05-18 21:08:04 +02:00
gnome3 = recurseIntoAttrs (callPackage ../desktops/gnome-3/3.10 {
Attempt to define isolated attrset for gnome-3
2012-07-10 18:03:13 +02:00
callPackage = pkgs.newScope pkgs.gnome3;
self = pkgs.gnome3;
Add recurseIntoAttrs for gnome3 So that we can search for gnome3.* packages like this: nix-env -qaP \* | grep gnome3
2013-07-28 22:06:00 +02:00
});
Attempt to define isolated attrset for gnome-3
2012-07-10 18:03:13 +02:00
Branch gnome 3.12
2014-05-18 21:08:04 +02:00
gnome3_12 = recurseIntoAttrs (callPackage ../desktops/gnome-3/3.12 {
callPackage = pkgs.newScope pkgs.gnome3_12;
});
gnome: use callPackage, move to gnome-2 gnome28 was a mix of packages from various releases, so do not mention 2.28 in the attribute name. svn path=/nixpkgs/trunk/; revision=29721
2011-10-08 18:58:32 +02:00
gnome = recurseIntoAttrs gnome2;
Add gnome-2.28 to top-level svn path=/nixpkgs/trunk/; revision=17520
2009-09-30 07:29:08 +02:00
Add simple hsetroot package.
2013-08-01 20:12:44 +02:00
hsetroot = callPackage ../tools/X11/hsetroot { };
add kakasi, a Kanji to Hiragana, Katakana or Romaji converter
2014-04-18 16:07:17 +02:00
kakasi = callPackage ../tools/text/kakasi { };
Add simple hsetroot package.
2013-08-01 20:12:44 +02:00
Use KDE 4.12
2014-04-21 18:05:24 +02:00
kde4 = recurseIntoAttrs pkgs.kde412;
pkgs/applications/editors/emacs-modes/magit: updated to version magit-0.7-94-gbf42bf8 Magit has seen plenty of development since version 0.7, but for some reason there haven't been any new releases. This version bump updates the expression to build a current version of Magit directly from the Git repository. This change adds buildInputs 'autoconf' and 'automake'. These tools are required only because we aren't building from a proper release tarball. Once version 0.8 comes out, these dependencies can be dropped again. svn path=/nixpkgs/trunk/; revision=20650
2010-03-16 13:13:40 +01:00
KDE-4.12: package 4.12.2
2014-02-13 03:25:11 +01:00
kde4_next = recurseIntoAttrs( lib.lowPrioSet pkgs.kde412 );
KDE: default to 4.11
2014-02-05 19:14:16 +01:00
kde-4.10: Remove
2014-04-14 15:07:15 +02:00
kde412 = kdePackagesFor (pkgs.kde412 // {
KDE-4.12: package 4.12.2
2014-02-13 03:25:11 +01:00
eigen = eigen2;
libusb = libusb1;
libcanberra = libcanberra_kde;
}) ../desktops/kde-4.12;
Cleanup
2012-10-15 16:50:38 +02:00
kdePackagesFor = self: dir:
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
let callPackageOrig = callPackage; in
let
callPackage = newScope self;
Cleanup
2012-10-15 16:50:38 +02:00
kde4 = callPackageOrig dir {
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
inherit callPackage callPackageOrig;
};
in kde4 // {
inherit kde4;
Adding a KDE wrapper, to easily have KDE programs in nix-env. Specially for those not running KDE.
2013-05-09 20:40:29 +02:00
wrapper = callPackage ../build-support/kdewrapper {};
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
recurseForRelease = true;
akunambol = callPackage ../applications/networking/sync/akunambol { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
amarok = callPackage ../applications/audio/amarok { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
bangarang = callPackage ../applications/video/bangarang { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add kde4.basket svn path=/nixpkgs/trunk/; revision=31334
2012-01-06 01:55:30 +01:00
basket = callPackage ../applications/office/basket { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
bluedevil = callPackage ../tools/bluetooth/bluedevil { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add calligra suite KOffice, rebranded. Let hydra build it. svn path=/nixpkgs/trunk/; revision=32264
2012-02-13 20:34:42 +01:00
calligra = callPackage ../applications/office/calligra { };
Add colord-kde. A KDE front-end for colord.
2014-08-20 01:54:45 +02:00
colord-kde = callPackage ../tools/misc/colord-kde { };
digikam: updating (2.9 for kde 4.7/8, 3.2 for kde 4.10)
2013-05-30 15:11:20 +02:00
digikam = if builtins.compareVersions "4.9" kde4.release == 1 then
callPackage ../applications/graphics/digikam/2.nix { }
else
callPackage ../applications/graphics/digikam { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Changed the hash checker to sha256 and fixed (hopefully) all-packages.nix.
2013-09-29 15:30:08 +02:00
eventlist = callPackage ../applications/office/eventlist {};
all-packages.nix: strip trailing whitespace
2013-10-10 11:40:06 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
k3b = callPackage ../applications/misc/k3b { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
kadu = callPackage ../applications/networking/instant-messengers/kadu { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add kbibtex svn path=/nixpkgs/trunk/; revision=34404
2012-06-09 15:09:45 +02:00
kbibtex = callPackage ../applications/office/kbibtex { };
add kde-gtk-config-2.2.1
2013-12-25 02:15:42 +01:00
kde_gtk_config = callPackage ../tools/misc/kde-gtk-config { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
kde_wacomtablet = callPackage ../applications/misc/kde-wacomtablet { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add KDE Connect: A tool to connect and sync your devices with KDE
2014-06-22 10:56:43 +02:00
kdeconnect = callPackage ../applications/misc/kdeconnect { };
MLT: 0.9.0 -> 0.9.2, add movit and frei0r plugins, add qt4 and qt5 variants Shotcut segfaults on startup when compiled against an MLT which was built with qt4. Kdenlive seqfaults when compiled against an MLT which was built with qt5. Hence the need for the two variants. Also, I'm adopting MLT as a maintainer.
2014-07-27 12:36:07 +02:00
kdenlive = callPackage ../applications/video/kdenlive { mlt = mlt-qt4; };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
kdesvn = callPackage ../applications/version-management/kdesvn { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
kdevelop = callPackage ../applications/editors/kdevelop { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
kdevplatform = callPackage ../development/libraries/kdevplatform { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
kdiff3 = callPackage ../tools/text/kdiff3 { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add new kgraphviewer and massif-visualizer packages I chose the unstable versions because the stable versions seemed too outdated to me. They work with kde 4.12 anyway.
2014-09-03 17:00:13 +02:00
kgraphviewer = callPackage ../applications/graphics/kgraphviewer { };
Drop kde3.kile Use kde4.kile instead svn path=/nixpkgs/trunk/; revision=29715
2011-10-07 22:46:29 +02:00
kile = callPackage ../applications/editors/kile { };
Add kde4.kile svn path=/nixpkgs/trunk/; revision=29622
2011-10-04 13:12:11 +02:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
kmplayer = callPackage ../applications/video/kmplayer { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add kmymoney svn path=/nixpkgs/trunk/; revision=28910
2011-08-30 00:43:11 +02:00
kmymoney = callPackage ../applications/office/kmymoney { };
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
kipi_plugins = callPackage ../applications/graphics/kipi-plugins { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
konversation = callPackage ../applications/networking/irc/konversation { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Adding KVIrc : a IRC Client for Qt and KDE. in kde4.kvirc
2013-10-29 23:18:53 +01:00
kvirc = callPackage ../applications/networking/irc/kvirc { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
krename = callPackage ../applications/misc/krename { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
krusader = callPackage ../applications/misc/krusader { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add ksshaskpass Patch supplied by Kirill Elagin, edited by Yury Kudryashov. svn path=/nixpkgs/trunk/; revision=33386
2012-03-23 19:56:35 +01:00
ksshaskpass = callPackage ../tools/security/ksshaskpass {};
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
ktorrent = callPackage ../applications/networking/p2p/ktorrent { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
-kde3.kuickshow, +kde4.kuickshow svn path=/nixpkgs/trunk/; revision=31407
2012-01-07 18:06:57 +01:00
kuickshow = callPackage ../applications/graphics/kuickshow { };
Add bunch of kmymoney-4.6.1 dependencies svn path=/nixpkgs/trunk/; revision=31436
2012-01-08 20:29:07 +01:00
libalkimia = callPackage ../development/libraries/libalkimia { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
libktorrent = callPackage ../development/libraries/libktorrent { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add libkvkontakte svn path=/nixpkgs/trunk/; revision=31240
2012-01-03 17:15:22 +01:00
libkvkontakte = callPackage ../development/libraries/libkvkontakte { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
liblikeback = callPackage ../development/libraries/liblikeback { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Packaging plasma-nm and its dependencies
2014-07-05 13:54:01 +02:00
libmm-qt = callPackage ../development/libraries/libmm-qt { };
libnm-qt = callPackage ../development/libraries/libnm-qt { };
Add new kgraphviewer and massif-visualizer packages I chose the unstable versions because the stable versions seemed too outdated to me. They work with kde 4.12 anyway.
2014-09-03 17:00:13 +02:00
massif-visualizer = callPackage ../development/tools/analysis/massif-visualizer { };
Add kde4.networkmanagement You still need to start NetworkManager daemon manually to use this widget svn path=/nixpkgs/trunk/; revision=31229
2012-01-03 14:39:09 +01:00
networkmanagement = callPackage ../tools/networking/networkmanagement { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
partitionManager = callPackage ../tools/misc/partition-manager { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Packaging plasma-nm and its dependencies
2014-07-05 13:54:01 +02:00
plasma-nm = callPackage ../tools/networking/plasma-nm { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
polkit_kde_agent = callPackage ../tools/security/polkit-kde-agent { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
psi = callPackage ../applications/networking/instant-messengers/psi { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
webkitgtk, kde.qtcurve: build with default gcc (not 4.7)
2014-01-05 09:42:07 +01:00
qtcurve = callPackage ../misc/themes/qtcurve { };
add qtcurve-1.8.17
2013-12-28 16:42:10 +01:00
Fixed settings issue. The following warning was shown when I clicked on links: 'GLib-GIO-Message: Using the 'memory' GSettings backend. Your settings will not be saved or shared with other applications.'
2014-07-03 23:19:15 +02:00
quassel = callPackage ../applications/networking/irc/quassel { dconf = gnome3.dconf; };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
quassel: add quassel and quassel-client without kde integration Close #3508.
2014-08-09 21:04:06 +02:00
quasselWithoutKDE = (self.quassel.override {
withKDE = false;
tag = "-without-kde";
});
Rename quassel packages
2013-12-05 23:29:23 +01:00
quasselDaemon = (self.quassel.override {
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
monolithic = false;
daemon = true;
Rename quassel packages
2013-12-05 23:29:23 +01:00
tag = "-daemon";
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
});
Wrap kde-related packages in kdePackagesFor This lets hydra build kde packages for all available KDE releases. Will commit NixOS-fix in a few minutes. svn path=/nixpkgs/trunk/; revision=28833
2011-08-26 15:49:23 +02:00
Rename quassel packages
2013-12-05 23:29:23 +01:00
quasselClient = (self.quassel.override {
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
monolithic = false;
client = true;
Rename quassel packages
2013-12-05 23:29:23 +01:00
tag = "-client";
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
});
Wrap kde-related packages in kdePackagesFor This lets hydra build kde packages for all available KDE releases. Will commit NixOS-fix in a few minutes. svn path=/nixpkgs/trunk/; revision=28833
2011-08-26 15:49:23 +02:00
quassel: add quassel and quassel-client without kde integration Close #3508.
2014-08-09 21:04:06 +02:00
quasselClientWithoutKDE = (self.quasselClient.override {
withKDE = false;
tag = "-client-without-kde";
});
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
rekonq = callPackage ../applications/networking/browsers/rekonq { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
KWebKitPart: new package
2013-05-10 04:03:54 +02:00
kwebkitpart = callPackage ../applications/networking/browsers/kwebkitpart { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
rsibreak = callPackage ../applications/misc/rsibreak { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
semnotes = callPackage ../applications/misc/semnotes { };
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=28862
2011-08-29 09:39:08 +02:00
Add skrooge svn path=/nixpkgs/trunk/; revision=31438
2012-01-08 20:29:28 +01:00
skrooge = callPackage ../applications/office/skrooge { };
Add KDE-Telepathy It compiles but I haven't tried to run it. svn path=/nixpkgs/trunk/; revision=33063
2012-03-14 10:52:21 +01:00
telepathy = callPackage ../applications/networking/instant-messengers/telepathy/kde {};
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
yakuake = callPackage ../applications/misc/yakuake { };
Add skrooge svn path=/nixpkgs/trunk/; revision=31438
2012-01-08 20:29:28 +01:00
zanshin = callPackage ../applications/office/zanshin { };
added kwooty: a binary newsreader (kde). svn path=/nixpkgs/trunk/; revision=31829
2012-01-24 23:09:17 +01:00
kwooty = callPackage ../applications/networking/newsreaders/kwooty { };
* Fix indentation/layout. svn path=/nixpkgs/trunk/; revision=28848
2011-08-27 17:19:19 +02:00
};
Start kde-4.6: copy 4.5, remove from release svn path=/nixpkgs/trunk/; revision=25279
2010-12-26 16:26:01 +01:00
Adding redshift; it changes the color temperature of your screen gradually to match the lighting conditions svn path=/nixpkgs/trunk/; revision=25686
2011-01-25 00:52:22 +01:00
redshift = callPackage ../applications/misc/redshift {
inherit (xorg) libX11 libXrandr libxcb randrproto libXxf86vm
xf86vidmodeproto;
redshift: update to 1.8 and fix redshift-gtk script
2013-10-26 19:15:57 +02:00
inherit (gnome) GConf;
inherit (pythonPackages) pyxdg;
changes in: redshift, geoclue, libsoup - added support for geoclue for redshift - package geoclue 2.0.0 (as geoclue2) - package libsoup 2.44.1 (as libsoup_2_40)
2013-10-29 16:23:24 +01:00
geoclue = geoclue2;
Adding redshift; it changes the color temperature of your screen gradually to match the lighting conditions svn path=/nixpkgs/trunk/; revision=25686
2011-01-25 00:52:22 +01:00
};
pkgs/top-level/all-packages.nix: strip trailing whitenspace svn path=/nixpkgs/trunk/; revision=23118
2010-08-11 17:49:42 +02:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
oxygen_gtk = callPackage ../misc/themes/gtk2/oxygen-gtk { };
Adding the Oxygen-GTK theme svn path=/nixpkgs/trunk/; revision=25676
2011-01-23 22:04:12 +01:00
add gtk-engines 2.20.2
2013-08-11 05:49:43 +02:00
gtk_engines = callPackage ../misc/themes/gtk2/gtk-engines { };
add gtk-engine-murrine 0.98.2
2013-08-27 12:57:19 +02:00
gtk-engine-murrine = callPackage ../misc/themes/gtk2/gtk-engine-murrine { };
gnome_themes_standard: bump to 3.10.0 and move into gnome3 attrset
2014-01-09 13:45:12 +01:00
gnome_themes_standard = gnome3.gnome_themes_standard;
gnome-themes-standard: Initial expression
2013-03-25 15:23:45 +01:00
add mate-icon-theme 1.6.1
2013-08-27 15:01:24 +02:00
mate-icon-theme = callPackage ../misc/themes/mate-icon-theme { };
add mate-themes 1.6.1
2013-08-27 15:02:46 +02:00
mate-themes = callPackage ../misc/themes/mate-themes { };
vlada/xfce Major Xfce refactoring, also adding versions 4.10.* Signed-off-by: Vladimír Čunát <vcunat@gmail.com>
2013-02-21 12:16:51 +01:00
xfce = xfce4_10;
xfce4_10 = recurseIntoAttrs (import ../desktops/xfce { inherit pkgs newScope; });
pkgs/top-level/all-packages.nix: strip trailing whitenspace svn path=/nixpkgs/trunk/; revision=23118
2010-08-11 17:49:42 +02:00
Consistent whitespace
2013-06-13 15:18:16 +02:00
Added XPlanet support to kdeedu-4.3.1, not that is an essential feature but it looks cool :-) svn path=/nixpkgs/trunk/; revision=17054
2009-09-11 16:06:51 +02:00
### SCIENCE
xlock: fixed build and updated to version 5.24 svn path=/nixpkgs/trunk/; revision=17356
2009-09-22 22:16:38 +02:00
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
### SCIENCE/GEOMETRY
Added toplevel clustalw2 svn path=/nixpkgs/trunk/; revision=11632
2008-04-15 11:35:52 +02:00
Added DrGeo svn path=/nixpkgs/trunk/; revision=12204
2008-06-27 21:15:01 +02:00
drgeo = builderDefsPackage (import ../applications/science/geometry/drgeo) {
Make nixpkgs ready to gtkLibs attrset removal svn path=/nixpkgs/trunk/; revision=33091
2012-03-14 23:44:41 +01:00
inherit (gnome) libglade;
inherit libxml2 perl intltool libtool pkgconfig gtk;
Prepare for the Guile 2.0 switchover. svn path=/nixpkgs/trunk/; revision=25976
2011-02-15 14:14:29 +01:00
guile = guile_1_8;
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
};
Added DrGeo svn path=/nixpkgs/trunk/; revision=12204
2008-06-27 21:15:01 +02:00
Adding tetgen svn path=/nixpkgs/trunk/; revision=23138
2010-08-12 12:59:05 +02:00
tetgen = callPackage ../applications/science/geometry/tetgen { };
Updated CMake to version 2.6.3. svn path=/nixpkgs/trunk/; revision=15114
2009-04-17 15:48:22 +02:00
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
### SCIENCE/BIOLOGY
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
alliance = callPackage ../applications/science/electronics/alliance {
Adding alliance 5.0 svn path=/nixpkgs/trunk/; revision=14008
2009-02-08 17:28:31 +01:00
motif = lesstif;
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
arb = callPackage ../applications/science/biology/arb {
Added older version of lesstif for arb svn path=/nixpkgs/trunk/; revision=12974
2008-10-06 17:11:36 +02:00
lesstif = lesstif93;
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
};
Introduced biolib package svn path=/nixpkgs/trunk/; revision=12535
2008-08-07 17:01:21 +02:00
Adding GNU archimedes. svn path=/nixpkgs/trunk/; revision=31505
2012-01-12 20:23:47 +01:00
archimedes = callPackage ../applications/science/electronics/archimedes { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
biolib = callPackage ../development/libraries/science/biology/biolib { };
Introduced biolib package svn path=/nixpkgs/trunk/; revision=12535
2008-08-07 17:01:21 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
emboss = callPackage ../applications/science/biology/emboss { };
Control for biology packages svn path=/nixpkgs/trunk/; revision=11994
2008-06-05 19:15:27 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
mrbayes = callPackage ../applications/science/biology/mrbayes { };
Control for biology packages svn path=/nixpkgs/trunk/; revision=11994
2008-06-05 19:15:27 +02:00
All-packages entry for NCBI C toolbox svn path=/nixpkgs/trunk/; revision=18925
2009-12-13 21:24:23 +01:00
ncbiCTools = builderDefsPackage ../development/libraries/ncbi {
inherit tcsh mesa lesstif;
pkgs/top-level/all-packages.nix: switch to Python 2.6 (except on Darwin) MacOS X can build Python 2.6 just fine, but for some reason a lot of modules don't work, so the resulting binary isn't very useful. svn path=/nixpkgs/branches/stdenv-updates/; revision=19598
2010-01-21 16:39:11 +01:00
inherit (xlibs) libX11 libXaw xproto libXt libSM libICE
All-packages entry for NCBI C toolbox svn path=/nixpkgs/trunk/; revision=18925
2009-12-13 21:24:23 +01:00
libXmu libXext;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ncbi_tools = callPackage ../applications/science/biology/ncbi-tools { };
Added ncbi-tools svn path=/nixpkgs/trunk/; revision=12003
2008-06-06 21:42:00 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
paml = callPackage ../applications/science/biology/paml { };
biology/paml added svn path=/nixpkgs/trunk/; revision=11997
2008-06-06 10:23:49 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pal2nal = callPackage ../applications/science/biology/pal2nal { };
Introduced pal2nal package svn path=/nixpkgs/trunk/; revision=12896
2008-09-19 15:39:17 +02:00
Added expression for PLINK
2013-09-19 01:36:40 +02:00
plink = callPackage ../applications/science/biology/plink/default.nix { };
Updated CMake to version 2.6.3. svn path=/nixpkgs/trunk/; revision=15114
2009-04-17 15:48:22 +02:00
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
### SCIENCE/MATH
add arpack-3.1.4
2013-12-27 21:14:42 +01:00
arpack = callPackage ../development/libraries/science/math/arpack { };
Atlas aborts the build some kind of CPU frequency scaling is detected on the build machine because that feature offsets the performance timings. We ignore that check, however, because with binaries being pre-built on Hydra those timings aren't accurate for the local machine in the first place. The build log might show something such as the following: | It appears you have cpu throttling enabled, which makes timings | unreliable and an ATLAS install nonsensical. Aborting. | See ATLAS/INSTALL.txt for further information | Ignoring CPU throttling by user override! svn path=/nixpkgs/trunk/; revision=32506
2012-02-23 12:33:26 +01:00
atlas = callPackage ../development/libraries/science/math/atlas {
# The build process measures CPU capabilities and optimizes the
# library to perform best on that particular machine. That is a
# great feature, but it's of limited use with pre-built binaries
# coming from a central build farm.
tolerateCpuTimingInaccuracy = true;
};
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
blas = callPackage ../development/libraries/science/math/blas { };
pkgs/development/libraries/science/math/blas: added BLAS version 20070405 svn path=/nixpkgs/trunk/; revision=19671
2010-01-26 15:53:08 +01:00
changes for Content svn path=/nixpkgs/trunk/; revision=18928
2009-12-14 01:00:34 +01:00
content = builderDefsPackage ../applications/science/math/content {
inherit mesa lesstif;
pkgs/top-level/all-packages.nix: switch to Python 2.6 (except on Darwin) MacOS X can build Python 2.6 just fine, but for some reason a lot of modules don't work, so the resulting binary isn't very useful. svn path=/nixpkgs/branches/stdenv-updates/; revision=19598
2010-01-21 16:39:11 +01:00
inherit (xlibs) libX11 libXaw xproto libXt libSM libICE
adding libxcursor dependency svn path=/nixpkgs/trunk/; revision=18929
2009-12-14 01:14:43 +01:00
libXmu libXext libXcursor;
changes for Content svn path=/nixpkgs/trunk/; revision=18928
2009-12-14 01:00:34 +01:00
};
Added JAGS. svn path=/nixpkgs/trunk/; revision=26396
2011-03-17 15:45:36 +01:00
jags = callPackage ../applications/science/math/jags { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
liblapack = callPackage ../development/libraries/science/math/liblapack { };
Adding Julia 0.3.0: some progress, but doesn't work yet
2014-08-21 20:09:39 +02:00
liblapack_3_5_0 = callPackage ../development/libraries/science/math/liblapack/3.5.0.nix { };
Add all my latest packages to all-packages.nix svn path=/nixpkgs/trunk/; revision=12957
2008-10-05 11:04:30 +02:00
Add liblbfgs 1.10
2014-05-07 14:22:04 +02:00
liblbfgs = callPackage ../development/libraries/science/math/liblbfgs { };
openblas: pin all the versions julia requires
2014-08-28 23:07:30 +02:00
# julia is pinned to specific versions of openblas, so keep old versions
# until they aren't needed. The un-versioned attribute may continue to track
# upstream development.
openblas: add version 0.2.11
2014-08-28 23:39:01 +02:00
openblas = callPackage ../development/libraries/science/math/openblas {
liblapack = liblapack_3_5_0;
};
xnee: update to 3.19
2014-08-27 15:55:26 +02:00
openblas_0_2_10 = callPackage ../development/libraries/science/math/openblas/0.2.10.nix {
Fix Julia 0.3.0 build (for most purposes). Not making default yet because it is unclear if I missed something important. Failed to make it use external openblas and lapack correctly…
2014-08-23 22:24:46 +02:00
liblapack = liblapack_3_5_0;
};
openblas: pin all the versions julia requires
2014-08-28 23:07:30 +02:00
openblas_0_2_2 = callPackage ../development/libraries/science/math/openblas/0.2.2.nix { };
Updated CMake to version 2.6.3. svn path=/nixpkgs/trunk/; revision=15114
2009-04-17 15:48:22 +02:00
add mathematica version 9.0.0 Wolfram Mathematica based on the makeself archive found on the Mathematica installation DVD.
2013-09-15 14:22:27 +02:00
mathematica = callPackage ../applications/science/math/mathematica { };
Add GROMACS v4.5.5
2012-11-23 03:38:13 +01:00
Add expression for sage
2014-04-22 21:10:36 +02:00
sage = callPackage ../applications/science/math/sage { };
Add GROMACS v4.5.5
2012-11-23 03:38:13 +01:00
### SCIENCE/MOLECULAR-DYNAMICS
gromacs = callPackage ../applications/science/molecular-dynamics/gromacs {
singlePrec = true;
fftw = fftwSinglePrec;
cmake = cmakeCurses;
};
Update based on comments to pull request
2012-11-23 15:29:17 +01:00
gromacsDouble = lowPrio (callPackage ../applications/science/molecular-dynamics/gromacs {
Add GROMACS v4.5.5
2012-11-23 03:38:13 +01:00
singlePrec = false;
fftw = fftw;
cmake = cmakeCurses;
Update based on comments to pull request
2012-11-23 15:29:17 +01:00
});
Add GROMACS v4.5.5
2012-11-23 03:38:13 +01:00
Consistent whitespace
2013-06-13 15:18:16 +02:00
Added a preliminary expression for Coq (no IDE support yet). svn path=/nixpkgs/trunk/; revision=11983
2008-06-04 17:10:05 +02:00
### SCIENCE/LOGIC
nixpkgs: add abc version 040509 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-10 04:37:41 +02:00
abc-verifier = callPackage ../applications/science/logic/abc {};
nixpkgs: add alt-ergo 0.95.2 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-01 09:29:42 +02:00
alt-ergo = callPackage ../applications/science/logic/alt-ergo {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
coq = callPackage ../applications/science/logic/coq {
* Update lablgtk2 (and enable hydra build) svn path=/nixpkgs/trunk/; revision=25213
2010-12-20 15:58:56 +01:00
inherit (ocamlPackages) findlib lablgtk;
Update coq to use camlp5 version 6. svn path=/nixpkgs/trunk/; revision=34261
2012-05-28 21:41:26 +02:00
camlp5 = ocamlPackages.camlp5_transitional;
Added a preliminary expression for Coq (no IDE support yet). svn path=/nixpkgs/trunk/; revision=11983
2008-06-04 17:10:05 +02:00
};
Added toplevel clustalw2 svn path=/nixpkgs/trunk/; revision=11632
2008-04-15 11:35:52 +02:00
Add an expression for building Coq HEAD
2014-08-07 21:47:06 +02:00
coq_HEAD = callPackage ../applications/science/logic/coq/HEAD.nix {
inherit (ocamlPackages) findlib lablgtk;
camlp5 = ocamlPackages.camlp5_transitional;
};
Added toplevel clustalw2 svn path=/nixpkgs/trunk/; revision=11632
2008-04-15 11:35:52 +02:00
Update coq to 8.4
2012-08-19 07:01:30 +02:00
coq_8_3 = callPackage ../applications/science/logic/coq/8.3.nix {
inherit (ocamlPackages) findlib lablgtk;
camlp5 = ocamlPackages.camlp5_transitional;
};
Adding CVC3 satisfiability modulo theory (SMT) solver svn path=/nixpkgs/trunk/; revision=24975
2010-12-05 18:28:41 +01:00
cvc3 = callPackage ../applications/science/logic/cvc3 {};
Adding E-KRHyper theorem prover
2013-05-09 15:47:40 +02:00
ekrhyper = callPackage ../applications/science/logic/ekrhyper {};
Update E prover
2012-12-08 21:36:38 +01:00
eprover = callPackage ../applications/science/logic/eprover {
Move E prover to applications/science/logic svn path=/nixpkgs/trunk/; revision=23434
2010-08-26 00:38:11 +02:00
texLive = texLiveAggregationFun {
paths = [
texLive texLiveExtra
];
Add GiNaC svn path=/nixpkgs/trunk/; revision=34403
2012-06-09 15:09:41 +02:00
};
Move E prover to applications/science/logic svn path=/nixpkgs/trunk/; revision=23434
2010-08-26 00:38:11 +02:00
};
Add GiNaC svn path=/nixpkgs/trunk/; revision=34403
2012-06-09 15:09:41 +02:00
ginac = callPackage ../applications/science/math/ginac { };
Move E prover to applications/science/logic svn path=/nixpkgs/trunk/; revision=23434
2010-08-26 00:38:11 +02:00
pkgs/applications/science/logic/hol: initial version svn path=/nixpkgs/trunk/; revision=23430
2010-08-25 21:50:24 +02:00
hol = callPackage ../applications/science/logic/hol { };
Added toplevel clustalw2 svn path=/nixpkgs/trunk/; revision=11632
2008-04-15 11:35:52 +02:00
* Update camlp5 svn path=/nixpkgs/trunk/; revision=25206
2010-12-20 11:32:22 +01:00
hol_light = callPackage ../applications/science/logic/hol_light {
Update hol_light and cleanup: * Update hol_light to rev 90 * Remove dmtcp checkpoint (it doesn't work properly). * General cleanup and simplification svn path=/nixpkgs/trunk/; revision=27290
2011-05-21 13:18:35 +02:00
inherit (ocamlPackages) findlib;
camlp5 = ocamlPackages.camlp5_strict;
* Update camlp5 svn path=/nixpkgs/trunk/; revision=25206
2010-12-20 11:32:22 +01:00
};
Add HOL Light and its dependencies. Add pkgs/applications/science/logic/hol_light and pkgs/applications/science/emacs-modes/hol_light Some functionalities of HOL Light requires the compiled sources of OCaml. For now we provide a new package ocaml_with_sources. After this shuold be merged with the current version of OCaml already present in nixpkgs. svn path=/nixpkgs/trunk/; revision=20008
2010-02-15 12:00:02 +01:00
Add expression for Isabelle2009 svn path=/nixpkgs/trunk/; revision=18905
2009-12-11 18:00:52 +01:00
isabelle = import ../applications/science/logic/isabelle {
svn path=/nixpkgs/trunk/; revision=22880
2010-08-02 18:01:55 +02:00
inherit (pkgs) stdenv fetchurl nettools perl polyml;
Updated Emacs default version from 23.3 to 24.1. Yay! svn path=/nixpkgs/trunk/; revision=34461
2012-06-11 18:41:31 +02:00
inherit (pkgs.emacs24Packages) proofgeneral;
Add expression for Isabelle2009 svn path=/nixpkgs/trunk/; revision=18905
2009-12-11 18:00:52 +01:00
};
Adding iProver svn path=/nixpkgs/trunk/; revision=24969
2010-12-04 19:39:44 +01:00
iprover = callPackage ../applications/science/logic/iprover {};
Adding LEO2 automated higher-order prover svn path=/nixpkgs/trunk/; revision=24952
2010-12-01 22:29:42 +01:00
leo2 = callPackage ../applications/science/logic/leo2 {};
Added Logisim-2.7.1.
2012-12-27 16:25:39 +01:00
logisim = callPackage ../applications/science/logic/logisim {};
nixpkgs: add ltl2ba 1.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-01 09:27:05 +02:00
ltl2ba = callPackage ../applications/science/logic/ltl2ba {};
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
matita = callPackage ../applications/science/logic/matita {
Reparing stable build of Matita. Also correcting the version and simplifying the prerelease package of Matita. svn path=/nixpkgs/trunk/; revision=33420
2012-03-25 23:27:30 +02:00
ocaml = ocaml_3_11_2;
inherit (ocamlPackages_3_11_2) findlib lablgtk ocaml_expat gmetadom ocaml_http
lablgtkmathview ocaml_mysql ocaml_sqlite3 ocamlnet camlzip ocaml_pcre;
ulex08 = ocamlPackages_3_11_2.ulex08.override { camlp5 = ocamlPackages_3_11_2.camlp5_5_transitional; };
Matita and its dependencies. svn path=/nixpkgs/trunk/; revision=25328
2010-12-31 18:48:55 +01:00
};
Adding a package for a preview release of Matita. svn path=/nixpkgs/trunk/; revision=33418
2012-03-25 22:43:00 +02:00
matita_130312 = lowPrio (callPackage ../applications/science/logic/matita/130312.nix {
inherit (ocamlPackages) findlib lablgtk ocaml_expat gmetadom ocaml_http
ocaml_mysql ocamlnet ulex08 camlzip ocaml_pcre;
});
Adding MiniSAT svn path=/nixpkgs/trunk/; revision=24984
2010-12-05 20:54:27 +01:00
minisat = callPackage ../applications/science/logic/minisat {};
Making the current versions of flex/bison the default. Evaluation test passes. Please explicitly pass older versions to any package that can be adversely affected by too-fresh versions. svn path=/nixpkgs/branches/stdenv-updates/; revision=25086
2010-12-12 22:48:29 +01:00
opensmt = callPackage ../applications/science/logic/opensmt { };
Adding OpenSMT svn path=/nixpkgs/trunk/; revision=24978
2010-12-05 19:22:14 +01:00
Adding Otter theorem prover. The development is frozen, but because of that Otter is considered a very reliable prover from soundness point of view.
2013-05-09 10:23:27 +02:00
otter = callPackage ../applications/science/logic/otter {};
Forgot to add picosat to the all-packages.nix in revision 29869. Now I'm adding it. svn path=/nixpkgs/trunk/; revision=30554
2011-11-24 20:53:42 +01:00
picosat = callPackage ../applications/science/logic/picosat {};
prooftree: new expression 0.12
2014-06-08 07:35:26 +02:00
prooftree = callPackage ../applications/science/logic/prooftree {
inherit (ocamlPackages) findlib lablgtk;
camlp5 = ocamlPackages.camlp5_transitional;
};
pkgs/applications/science/logic/prover9: initial version svn path=/nixpkgs/trunk/; revision=23446
2010-08-26 13:37:05 +02:00
prover9 = callPackage ../applications/science/logic/prover9 { };
Adding Satallax prover svn path=/nixpkgs/trunk/; revision=24963
2010-12-03 12:26:34 +01:00
satallax = callPackage ../applications/science/logic/satallax {};
Adding SPASS svn path=/nixpkgs/trunk/; revision=24967
2010-12-04 12:43:01 +01:00
spass = callPackage ../applications/science/logic/spass {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
ssreflect = callPackage ../applications/science/logic/ssreflect {
Updatings ssreflect to depend on camlp5 version 6. svn path=/nixpkgs/trunk/; revision=34263
2012-05-28 22:53:17 +02:00
camlp5 = ocamlPackages.camlp5_transitional;
Preliminary version of package ssreflect Add expression for ssreflect, an extension to the Coq Proof Assistant. Still has some clitches (see TODO in default.nix) but is usable anyway. svn path=/nixpkgs/trunk/; revision=18145
2009-11-05 16:08:12 +01:00
};
Adding TPTP svn path=/nixpkgs/trunk/; revision=27468
2011-06-15 12:35:18 +02:00
tptp = callPackage ../applications/science/logic/tptp {};
twelf: new expression; prover for PL theory and logic
2014-06-27 00:54:12 +02:00
twelf = callPackage ../applications/science/logic/twelf {
smlnj = if stdenv.isDarwin
then smlnjBootstrap
else smlnj;
};
verifast: 14.5, x86_64 linux only Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-06-10 23:38:45 +02:00
verifast = callPackage ../applications/science/logic/verifast {};
nixpkgs: verifast 13.11.14 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-28 20:46:16 +02:00
nixpkgs: add why3 0.83 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-01 09:28:52 +02:00
why3 = callPackage ../applications/science/logic/why3 {};
nixpkgs: yices 2.2.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-27 20:05:35 +02:00
yices = callPackage ../applications/science/logic/yices {};
z3: version 4.3.1 Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-03-08 05:45:15 +01:00
z3 = callPackage ../applications/science/logic/z3 {};
Consistent whitespace
2013-06-13 15:18:16 +02:00
boolector: add version 1.5 and 1.6 There are two versions here because beginning with 1.6.0, Boolector has a more restrictive, unfree license which disallows commercial use. As a result, Boolector 1.5 is the default 'boolector' expression. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-04-06 18:47:42 +02:00
boolector = boolector15;
boolector15 = callPackage ../applications/science/logic/boolector {};
boolector16 = lowPrio (callPackage ../applications/science/logic/boolector {
useV16 = true;
});
added ngspice svn path=/nixpkgs/trunk/; revision=12686
2008-08-21 22:43:53 +02:00
### SCIENCE / ELECTRONICS
eagle: new package Eagle is a schematic capture and PCB layout program from CadSoft. This is proprietary software; CadSoft provide a self-extracting shell script with embedded tarball of the prebuilt application. Add the latest Eagle version, 6.4.0. I've added a small LD_PRELOAD library that redirects operations on the license file from <eagle_install_path>/bin/eagle.key to $HOME/.eagle.key. Without this Eagle will never get past the license dialog (because you cannot write to the nix store). Eagle also has issues copying its example projects to other locations; it seems that it wants to preserve the read-only permissions from the source over to the destination. Because of this it cannot complete the copy operation because it cannot write the project files into to the (read-only) project directory it just created. So wrap chmod by OR'ing in the write-by-owner bit.
2013-05-11 13:33:54 +02:00
eagle = callPackage_i686 ../applications/science/electronics/eagle { };
* Get rid of Qt 4.6. It doesn't compile with GCC 4.6. There was only one application still using it (Caneda), but upgrading it allowed it to build with Qt 4.7. svn path=/nixpkgs/branches/stdenv-updates/; revision=32353
2012-02-17 15:34:42 +01:00
caneda = callPackage ../applications/science/electronics/caneda { };
Adding caneda svn path=/nixpkgs/trunk/; revision=24450
2010-10-24 19:01:09 +02:00
Adding qucs svn path=/nixpkgs/trunk/; revision=24449
2010-10-24 19:00:57 +02:00
gtkwave = callPackage ../applications/science/electronics/gtkwave { };
kicad: upgrade to stable version 20130325, libraries to r220 - changed to require wxWidgets 2.9 -- seems to satisfy requirement for libgtkprint, even with gtk2
2013-04-01 04:11:21 +02:00
kicad = callPackage ../applications/science/electronics/kicad {
wxGTK = wxGTK29;
};
Adding Kicad svn path=/nixpkgs/trunk/; revision=23352
2010-08-22 14:09:47 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ngspice = callPackage ../applications/science/electronics/ngspice { };
added ngspice svn path=/nixpkgs/trunk/; revision=12686
2008-08-21 22:43:53 +02:00
Move qt3/qt4 choice to .nix expressions svn path=/nixpkgs/trunk/; revision=29404
2011-09-21 00:49:13 +02:00
qucs = callPackage ../applications/science/electronics/qucs { };
Updated CMake to version 2.6.3. svn path=/nixpkgs/trunk/; revision=15114
2009-04-17 15:48:22 +02:00
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
xoscope = callPackage ../applications/science/electronics/xoscope { };
Updated CMake to version 2.6.3. svn path=/nixpkgs/trunk/; revision=15114
2009-04-17 15:48:22 +02:00
Adding xoscope (oscilloscope for the sound card input, among others) svn path=/nixpkgs/trunk/; revision=22242
2010-06-13 12:01:16 +02:00
Add scilab-4.1.2 svn path=/nixpkgs/trunk/; revision=12810
2008-09-05 19:12:04 +02:00
### SCIENCE / MATH
Adding ecm-6.2.3. svn path=/nixpkgs/trunk/; revision=26930
2011-04-23 14:25:51 +02:00
ecm = callPackage ../applications/science/math/ecm { };
eukleides: build with texinfo 4.x; version 5 doesn't succeed
2014-01-21 20:26:45 +01:00
eukleides = callPackage ../applications/science/math/eukleides {
texinfo = texinfo4;
};
Added Eukleides, a geometry drawing language. svn path=/nixpkgs/trunk/; revision=27655
2011-07-07 23:53:21 +02:00
all-packages.nix: move 'science/misc' builds into the proper place and add attribute for 'fricas'
2014-01-20 18:24:56 +01:00
fricas = callPackage ../applications/science/math/fricas { };
Adding GAP discrete algebra system svn path=/nixpkgs/trunk/; revision=32908
2012-03-08 19:23:47 +01:00
gap = callPackage ../applications/science/math/gap { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
maxima = callPackage ../applications/science/math/maxima { };
Move maxima close to scilab. (applications/science/math) Requested by Michael Raskin. svn path=/nixpkgs/trunk/; revision=12812
2008-09-05 19:21:45 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
wxmaxima = callPackage ../applications/science/math/wxmaxima { };
Added wxMaxima version 0.8.3. svn path=/nixpkgs/trunk/; revision=18015
2009-10-29 12:57:58 +01:00
Adding PARI/GP svn path=/nixpkgs/trunk/; revision=24983
2010-12-05 20:11:21 +01:00
pari = callPackage ../applications/science/math/pari {};
pspp: add version 0.8.1
2013-09-26 11:41:07 +02:00
pspp = callPackage ../applications/science/math/pssp {
inherit (gnome) libglade gtksourceview;
};
Adding Singular CAS svn path=/nixpkgs/trunk/; revision=24980
2010-12-05 19:36:07 +01:00
singular = callPackage ../applications/science/math/singular {};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
scilab = callPackage ../applications/science/math/scilab {
Add scilab-4.1.2 svn path=/nixpkgs/trunk/; revision=12810
2008-09-05 19:12:04 +02:00
withXaw3d = false;
withTk = true;
withGtk = false;
withOCaml = true;
withX = true;
};
Package for msieve. This would be better if gmp-emc were packaged as well. svn path=/nixpkgs/trunk/; revision=26915
2011-04-21 14:48:07 +02:00
msieve = callPackage ../applications/science/math/msieve { };
Adding 'weka'.
2013-06-19 16:12:55 +02:00
weka = callPackage ../applications/science/math/weka { };
yad: a nice zenity clone for creating GUI dialogs from the shell
2014-01-09 22:02:31 +01:00
yad = callPackage ../tools/misc/yad { };
Adding 'yacas', a CAS implemented in C++. svn path=/nixpkgs/trunk/; revision=23074
2010-08-09 23:58:21 +02:00
yacas = callPackage ../applications/science/math/yacas { };
speedcrunch: new package speedcrunch is a fast power user calculator.
2013-09-27 00:58:54 +02:00
speedcrunch = callPackage ../applications/science/math/speedcrunch {
qt = qt4;
cmake = cmakeCurses;
};
Consistent whitespace
2013-06-13 15:18:16 +02:00
Add Tulip, a graph visualization framework. svn path=/nixpkgs/trunk/; revision=22264
2010-06-14 20:30:35 +02:00
### SCIENCE / MISC
Adding boinc. It installs. I don't know how to use it. svn path=/nixpkgs/trunk/; revision=29704
2011-10-06 22:25:05 +02:00
boinc = callPackage ../applications/science/misc/boinc { };
all-packages.nix: move 'science/misc' builds into the proper place and add attribute for 'fricas'
2014-01-20 18:24:56 +01:00
celestia = callPackage ../applications/science/astronomy/celestia {
lua = lua5_1;
inherit (xlibs) libXmu;
inherit (pkgs.gnome) gtkglext;
};
Add application for scientific data analysis: fityk
2014-08-14 01:52:06 +02:00
fityk = callPackage ../applications/science/misc/fityk { };
all-packages.nix: move 'science/misc' builds into the proper place and add attribute for 'fricas'
2014-01-20 18:24:56 +01:00
gravit = callPackage ../applications/science/astronomy/gravit { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
golly = callPackage ../applications/science/misc/golly { };
Adding golly (a cellular automata program) svn path=/nixpkgs/trunk/; revision=22391
2010-06-23 09:41:17 +02:00
megam: New package Maximum Entropy (GA) Model Optimization Package
2014-04-15 14:23:07 +02:00
megam = callPackage ../applications/science/misc/megam { };
all-packages.nix: move 'science/misc' builds into the proper place and add attribute for 'fricas'
2014-01-20 18:24:56 +01:00
root = callPackage ../applications/science/misc/root { };
Merging from trunk (the callPackage change) svn path=/nixpkgs/branches/stdenv-updates/; revision=22915
2010-08-03 10:14:13 +02:00
simgrid = callPackage ../applications/science/misc/simgrid { };
Move SimGrid under `science/misc'. svn path=/nixpkgs/trunk/; revision=22312
2010-06-17 19:06:40 +02:00
all-packages.nix: move 'science/misc' builds into the proper place and add attribute for 'fricas'
2014-01-20 18:24:56 +01:00
spyder = callPackage ../applications/science/spyder {
inherit (pythonPackages) pyflakes rope sphinx numpy scipy matplotlib; # recommended
inherit (pythonPackages) ipython pep8; # optional
inherit pylint;
};
stellarium = callPackage ../applications/science/astronomy/stellarium { };
tulip-3.6.1 svn path=/nixpkgs/trunk/; revision=31216
2012-01-02 19:36:04 +01:00
tulip = callPackage ../applications/science/misc/tulip { };
Updated CMake to version 2.6.3. svn path=/nixpkgs/trunk/; revision=15114
2009-04-17 15:48:22 +02:00
State qt version (3/4) in packages, not in all-packages.nix svn path=/nixpkgs/trunk/; revision=31406
2012-01-07 18:06:49 +01:00
vite = callPackage ../applications/science/misc/vite { };
Updated CMake to version 2.6.3. svn path=/nixpkgs/trunk/; revision=15114
2009-04-17 15:48:22 +02:00
all-packages.nix: move 'science/misc' builds into the proper place and add attribute for 'fricas'
2014-01-20 18:24:56 +01:00
xplanet = callPackage ../applications/science/astronomy/xplanet { };
Consistent whitespace
2013-06-13 15:18:16 +02:00
* User-Mode Linux and GNU Patch. svn path=/nixpkgs/trunk/; revision=779
2004-02-13 15:42:28 +01:00
### MISC
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
atari800 = callPackage ../misc/emulators/atari800 { };
* Gnome: use GTK 2.4. svn path=/nixpkgs/trunk/; revision=1671
2004-11-03 22:28:03 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
ataripp = callPackage ../misc/emulators/atari++ { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
auctex = callPackage ../tools/typesetting/tex/auctex { };
* Gnome: use GTK 2.4. svn path=/nixpkgs/trunk/; revision=1671
2004-11-03 22:28:03 +01:00
Added beep to top-level.
2014-01-25 10:28:54 +01:00
beep = callPackage ../misc/beep { };
upgrade some packages to libusb1 on my systems, I can now override "libusb = libusb1" in all of nixpkgs so perhaps we can soon drop libusb 0.1 support?
2013-06-28 23:04:28 +02:00
cups = callPackage ../misc/cups { libusb = libusb1; };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Add pdftops CUPS filter I've packaged this as a separate expression because it depends on poppler (why don't they look for pdftops on runtime?..). svn path=/nixpkgs/trunk/; revision=25124
2010-12-14 14:30:17 +01:00
cups_pdf_filter = callPackage ../misc/cups/pdf-filter.nix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gutenprint = callPackage ../misc/drivers/gutenprint { };
adding gutenprint (former gimp-print) and gutenprintBin. I still haven't found the source of the binary package containing the .ppd files Still impure but works. See comment. svn path=/nixpkgs/trunk/; revision=16881
2009-08-28 01:32:13 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gutenprintBin = callPackage ../misc/drivers/gutenprint/bin.nix { };
adding gutenprint (former gimp-print) and gutenprintBin. I still haven't found the source of the binary package containing the .ppd files Still impure but works. See comment. svn path=/nixpkgs/trunk/; revision=16881
2009-08-28 01:32:13 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
cupsBjnp = callPackage ../misc/cups/drivers/cups-bjnp { };
cups-bjnp driver svn path=/nixpkgs/trunk/; revision=16880
2009-08-28 01:32:10 +02:00
Adding two NES emulators. Because of them, I made allegro build the allegrogl library. I also added the HawkNL library. svn path=/nixpkgs/trunk/; revision=26517
2011-03-25 23:15:48 +01:00
darcnes = callPackage ../misc/emulators/darcnes { };
Added i3wm. Added newer version of file. (this time tested, I screwed up a patch by garbas) svn path=/nixpkgs/trunk/; revision=33952
2012-04-30 16:34:57 +02:00
dbacl = callPackage ../tools/misc/dbacl { };
dblatex: purify and add dblatexFull attribute imagemagick, transfig, inkscape, fontconfig and ghostscript are missing dependencies of dblatex. Instead of adding all those dependencies to the existing dblatex attribute, make a new dblatexFull attribute for that. Also pass --use-python-path at install time so that script shebangs end up with #!/path/to/python instead of #!/path/to/env python (which is impure when not run in a wrapper).
2013-09-28 00:38:28 +02:00
dblatex = callPackage ../tools/typesetting/tex/dblatex {
enableAllFeatures = false;
};
dblatexFull = appendToName "full" (dblatex.override {
enableAllFeatures = true;
});
* Added dblatex, a DocBook -> PS/PDF/DVI converter. svn path=/nixpkgs/trunk/; revision=9569
2007-11-01 15:37:23 +01:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dosbox = callPackage ../misc/emulators/dosbox { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
dpkg = callPackage ../tools/package-management/dpkg { };
added freestyle (non photorealistic renderer) and dependencies libQGLViewer, lib3ds svn path=/nixpkgs/trunk/; revision=12009
2008-06-08 05:56:32 +02:00
glib and gtk are now in top-level namespace svn path=/nixpkgs/trunk/; revision=33084
2012-03-14 20:59:41 +01:00
ekiga = newScope pkgs.gnome ../applications/networking/instant-messengers/ekiga { };
Adding Ekiga svn path=/nixpkgs/trunk/; revision=23653
2010-09-06 01:37:54 +02:00
add: emulationstation 1.0.2
2014-08-21 20:51:38 +02:00
emulationstation = callPackage ../misc/emulators/emulationstation { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
electricsheep = callPackage ../misc/screensavers/electricsheep { };
* Electric Sheep, a screensaver. svn path=/nixpkgs/trunk/; revision=15415
2009-04-30 19:41:19 +02:00
Adding two NES emulators. Because of them, I made allegro build the allegrogl library. I also added the HawkNL library. svn path=/nixpkgs/trunk/; revision=26517
2011-03-25 23:15:48 +01:00
fakenes = callPackage ../misc/emulators/fakenes { };
fceux: Add package for a NES emulator.
2014-06-08 00:08:57 +02:00
fceux = callPackage ../misc/emulators/fceux { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
foldingathome = callPackage ../misc/foldingathome { };
Adding a folding-at-home client. svn path=/nixpkgs/trunk/; revision=15122
2009-04-17 22:36:54 +02:00
Trying to add foomatic-filters and foo2zjs svn path=/nixpkgs/trunk/; revision=25712
2011-01-28 09:44:31 +01:00
foo2zjs = callPackage ../misc/drivers/foo2zjs {};
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
Trying to add foomatic-filters and foo2zjs svn path=/nixpkgs/trunk/; revision=25712
2011-01-28 09:44:31 +01:00
foomatic_filters = callPackage ../misc/drivers/foomatic-filters {};
Adding a folding-at-home client. svn path=/nixpkgs/trunk/; revision=15122
2009-04-17 22:36:54 +02:00
gcc-4.1: Remove No longer used and doesn't build.
2013-01-28 16:28:27 +01:00
freestyle = callPackage ../misc/freestyle { };
added freestyle (non photorealistic renderer) and dependencies libQGLViewer, lib3ds svn path=/nixpkgs/trunk/; revision=12009
2008-06-08 05:56:32 +02:00
gajim: Clean up and rewrite package expression. This should clean up the package expression significantly by actually using explicit input attributes and setting PYTHONPATH and GST_PLUGIN_PATH from environment variables in the builder. In addition, this adds a small patch from the upstream Mercurial repository to add an index.theme to the icons, so Gajim is able to load them correctly from the store. With this change, I'm adding myself to the maintainers list as well, because I'm switching over from TKabber to Gajim. Signed-off-by: aszlig <aszlig@redmoonstudios.org>
2013-05-25 05:18:08 +02:00
gajim = callPackage ../applications/networking/instant-messengers/gajim { };
Added Gajim XMPP client in nearly full-feature configuration with all dependencies svn path=/nixpkgs/trunk/; revision=15001
2009-04-12 21:34:20 +02:00
Add gammu version 1.33.0 - a library and command line utility for interfacing phones
2013-12-27 22:33:52 +01:00
gammu = callPackage ../applications/misc/gammu { };
* Gens/GS doesn't build on 64-bit systems. svn path=/nixpkgs/trunk/; revision=23390
2010-08-24 11:57:57 +02:00
gensgs = callPackage_i686 ../misc/emulators/gens-gs { };
* Added Gens/GS, a Mega Drive emulator. svn path=/nixpkgs/trunk/; revision=23377
2010-08-23 22:28:14 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
ghostscript = callPackage ../misc/ghostscript {
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
x11Support = false;
Do not build CUPS support for ghostscript on Darwin
2014-04-16 07:15:30 +02:00
cupsSupport = config.ghostscript.cups or (!stdenv.isDarwin);
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
gnuFork = config.ghostscript.gnu or false;
* Added Dosbox, a DOS (x86) emulator. svn path=/nixpkgs/trunk/; revision=4331
2005-12-03 03:32:02 +01:00
};
pkgs/top-level/all-packages.nix: removed lowPrio modifier from ghostscriptX By default, "nix-env -i ghostscript" used to install a version of Ghostscript that didn't support X11. IMHO, this was the wrong choice for a user profile. svn path=/nixpkgs/trunk/; revision=23829
2010-09-17 16:46:55 +02:00
ghostscriptX = appendToName "with-X" (ghostscript.override {
* added gv (ghostscript-with-X is a dependency) svn path=/nixpkgs/trunk/; revision=9122
2007-08-14 16:09:58 +02:00
x11Support = true;
pkgs/top-level/all-packages.nix: removed lowPrio modifier from ghostscriptX By default, "nix-env -i ghostscript" used to install a version of Ghostscript that didn't support X11. IMHO, this was the wrong choice for a user profile. svn path=/nixpkgs/trunk/; revision=23829
2010-09-17 16:46:55 +02:00
});
added: dnsmasq, uisp, fltk libixp_for_wmii, acerhk kernel module, reiserfsprogs, radeontools, msmtp, procmail, pstree, gxemul changed: umlutilities to also support building tunctl optionally (needing kernel header files) wmii updated and wmiimenu added svn path=/nixpkgs/trunk/; revision=9242
2007-09-03 14:10:57 +02:00
add GNU Guix
2013-07-03 15:33:02 +02:00
guix = callPackage ../tools/package-management/guix { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
gxemul = callPackage ../misc/gxemul { };
jack added - compiles - haven't done any testing yet svn path=/nixpkgs/trunk/; revision=9403
2007-10-04 00:38:09 +02:00
Add hatari Atari St emulator.
2013-04-22 22:10:15 +02:00
hatari = callPackage ../misc/emulators/hatari { };
State qt version (3/4) in packages, not in all-packages.nix svn path=/nixpkgs/trunk/; revision=31406
2012-01-07 18:06:49 +01:00
hplip = callPackage ../misc/drivers/hplip { };
jack added - compiles - haven't done any testing yet svn path=/nixpkgs/trunk/; revision=9403
2007-10-04 00:38:09 +02:00
hplip: add binary plugin
2014-05-11 00:33:46 +02:00
hplipWithPlugin = hplip.override { withPlugin = true; };
Uncommented mkDerivationByName. Now it doesn't break everything svn path=/nixpkgs/trunk/; revision=9415
2007-10-06 20:17:47 +02:00
# using the new configuration style proposal which is unstable
jack: change package and attr names to 'jack1' and 'jack2' Currently, we have a 'jack' package with attrname 'jack1d' and a 'jackdbus' package with attrname 'jackaudio'. Make it consistent 'jack1' and 'jack2' in both package name and attrname. This aligns the naming with what can be found on the JACK homepage. Q: what's the difference between jack1 and jack2? A: http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2
2014-07-22 22:06:44 +02:00
jack1 = callPackage ../misc/jackaudio/jack1.nix { };
Replacing JACK1 with JACK2 (also jackdbus instead of jackd), this works much better for me svn path=/nixpkgs/trunk/; revision=27205
2011-05-09 22:49:51 +02:00
jack: change package and attr names to 'jack1' and 'jack2' Currently, we have a 'jack' package with attrname 'jack1d' and a 'jackdbus' package with attrname 'jackaudio'. Make it consistent 'jack1' and 'jack2' in both package name and attrname. This aligns the naming with what can be found on the JACK homepage. Q: what's the difference between jack1 and jack2? A: http://trac.jackaudio.org/wiki/Q_differenc_jack1_jack2
2014-07-22 22:06:44 +02:00
jack2 = callPackage ../misc/jackaudio { };
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
keynav = callPackage ../tools/X11/keynav { };
Added gnuplotX - gnuplot with X11 on. svn path=/nixpkgs/trunk/; revision=9047
2007-08-04 17:12:14 +02:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
lazylist = callPackage ../tools/typesetting/tex/lazylist { };
* modified tetex to support extra .sty's from other packages * added lazylist and polytable (both tetex packages) * added lhs2tex ebuild, depending on the two above svn path=/nixpkgs/trunk/; revision=4609
2006-01-27 21:51:41 +01:00
lilypond: Update to 2.16.2, fix guile.
2013-04-21 09:24:55 +02:00
lilypond = callPackage ../misc/lilypond { guile = guile_1_8; };
adding lilypond svn path=/nixpkgs/trunk/; revision=17028
2009-09-10 18:57:56 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
martyr = callPackage ../development/libraries/martyr { };
* Sorted the contents of all-packages.nix. svn path=/nixpkgs/trunk/; revision=6535
2006-09-15 17:28:53 +02:00
Remove old maven versions, aliased maven to maven3. Updated maven 3 to 3.0.4
2012-08-25 19:43:54 +02:00
maven = maven3;
maven3 = callPackage ../misc/maven { jdk = openjdk; };
maven 2 binary (don't have time for source built right now) svn path=/nixpkgs/trunk/; revision=9953
2007-12-19 01:17:40 +01:00
Get rid of most references to gtkLibs svn path=/nixpkgs/trunk/; revision=33088
2012-03-14 22:57:32 +01:00
mess = callPackage ../misc/emulators/mess {
inherit (pkgs.gnome) GConf;
};
* Added MESS, the Multi Emulator Super System. svn path=/nixpkgs/trunk/; revision=23126
2010-08-11 21:47:05 +02:00
Added Mupen64 Plus, a nintendo 64 emulator svn path=/nixpkgs/trunk/; revision=27902
2011-07-22 16:03:23 +02:00
mupen64plus = callPackage ../misc/emulators/mupen64plus { };
Adding back the 1.5 expression of mupen64plus It has a GUI, for example.
2013-03-28 18:16:40 +01:00
mupen64plus1_5 = callPackage ../misc/emulators/mupen64plus/1.5.nix { };
Updating mupen64plus, and adding a GUI for it. I can't say the GUI works very well... it doesn't find the core properly, but I couldn't find why.
2013-03-28 18:12:27 +01:00
* Nix 0.16. svn path=/nixpkgs/trunk/; revision=23208
2010-08-17 17:21:42 +02:00
nix = nixStable;
Make `nixUnstable' the default. svn path=/nixpkgs/trunk/; revision=21616
2010-05-05 21:48:32 +02:00
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
nixStable = callPackage ../tools/package-management/nix {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
storeDir = config.nix.storeDir or "/nix/store";
stateDir = config.nix.stateDir or "/nix/var";
* Use it. svn path=/nixpkgs/trunk/; revision=5248
2006-05-01 21:16:41 +02:00
};
all-packages: remove trailing spaces svn path=/nixpkgs/trunk/; revision=22907
2010-08-02 23:40:34 +02:00
nixUnstable = callPackage ../tools/package-management/nix/unstable.nix {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
storeDir = config.nix.storeDir or "/nix/store";
stateDir = config.nix.stateDir or "/nix/var";
* Revive nixUnstable. svn path=/nixpkgs/trunk/; revision=7060
2006-11-17 13:49:46 +01:00
};
* Add a Nix expression for the Nix SQLite branch (temporarily). svn path=/nixpkgs/trunk/; revision=20377
2010-03-04 15:39:47 +01:00
Add nixops
2013-06-25 13:21:35 +02:00
nixops = callPackage ../tools/package-management/nixops { };
nix-prefetch-scripts: new expression
2014-06-10 17:36:41 +02:00
nix-prefetch-scripts = callPackage ../tools/package-management/nix-prefetch-scripts { };
Addnig a package to copy nix-prefetch-* to bin/. Hopefully fixes #1130
2014-06-08 23:11:03 +02:00
nix-repl: Add
2013-09-17 11:24:41 +02:00
nix-repl = callPackage ../tools/package-management/nix-repl { };
Add NUT package. svn path=/nixpkgs/trunk/; revision=27448
2011-06-14 04:41:01 +02:00
nut = callPackage ../applications/misc/nut { };
solfege: new package Solfege is an ear training application. This patch is based on the work of @mornfall.
2013-06-05 23:12:16 +02:00
solfege = callPackage ../misc/solfege {
pysqlite = pkgs.pythonPackages.sqlite3;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
disnix = callPackage ../tools/package-management/disnix { };
xlock: fixed build and updated to version 5.24 svn path=/nixpkgs/trunk/; revision=17356
2009-09-22 22:16:38 +02:00
disnix: push to latest 0.3 development release
2013-06-27 15:32:11 +02:00
dysnomia = callPackage ../tools/package-management/disnix/dysnomia {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
enableApacheWebApplication = config.disnix.enableApacheWebApplication or false;
enableAxis2WebService = config.disnix.enableAxis2WebService or false;
enableEjabberdDump = config.disnix.enableEjabberdDump or false;
enableMySQLDatabase = config.disnix.enableMySQLDatabase or false;
enablePostgreSQLDatabase = config.disnix.enablePostgreSQLDatabase or false;
enableSubversionRepository = config.disnix.enableSubversionRepository or false;
enableTomcatWebApplication = config.disnix.enableTomcatWebApplication or false;
- Renamed DisnixService => DisnixWebService - Updated to latest unstable version svn path=/nixpkgs/trunk/; revision=24559
2010-11-01 18:33:24 +01:00
};
openssh: Let $NIXPKGS_CONFIG determine whether OpenSSH supports PAM or not. PAM is enabled by default, as before. To disable it, set openssh { pam = false; }; or simply pam = false; in ~/.nixpkgs/config.nix. svn path=/nixpkgs/trunk/; revision=12312
2008-07-08 01:11:13 +02:00
Updated Disnix packages and added disnixos svn path=/nixpkgs/trunk/; revision=25181
2010-12-17 19:42:02 +01:00
disnixos = callPackage ../tools/package-management/disnix/disnixos { };
esniper 2.24.0 is a simple, lightweight tool for sniping eBay auctions. svn path=/nixpkgs/trunk/; revision=26086
2011-02-24 12:25:16 +01:00
- Renamed DisnixService => DisnixWebService - Updated to latest unstable version svn path=/nixpkgs/trunk/; revision=24559
2010-11-01 18:33:24 +01:00
DisnixWebService = callPackage ../tools/package-management/disnix/DisnixWebService { };
openssh: Let $NIXPKGS_CONFIG determine whether OpenSSH supports PAM or not. PAM is enabled by default, as before. To disable it, set openssh { pam = false; }; or simply pam = false; in ~/.nixpkgs/config.nix. svn path=/nixpkgs/trunk/; revision=12312
2008-07-08 01:11:13 +02:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
latex2html = callPackage ../tools/typesetting/tex/latex2html/default.nix {
applying patches provided by griswold svn path=/nixpkgs/trunk/; revision=19707
2010-01-27 13:12:35 +01:00
tex = tetex;
};
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
lkproof = callPackage ../tools/typesetting/tex/lkproof { };
Add tex macro lkproof for making proof figures. svn path=/nixpkgs/trunk/; revision=25277
2010-12-25 19:06:36 +01:00
pkgs/top-level/all-packages.nix: strip trailing whitespace svn path=/nixpkgs/trunk/; revision=24045
2010-10-04 11:49:25 +02:00
mysqlWorkbench = newScope gnome ../applications/misc/mysql-workbench {
MySql-Workbench: packaged Patch by Karn Kallio svn path=/nixpkgs/trunk/; revision=23983
2010-09-28 11:33:56 +02:00
lua = lua5;
inherit (pythonPackages) pexpect paramiko;
};
Add robomongo, a GUI for exploring mongodb data and building queries.
2013-11-25 03:29:37 +01:00
robomongo = callPackage ../applications/misc/robomongo { };
Added opkg package svn path=/nixpkgs/trunk/; revision=27554
2011-06-28 11:45:51 +02:00
opkg = callPackage ../tools/package-management/opkg { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
pgadmin = callPackage ../applications/misc/pgadmin { };
pgadmin3 added svn path=/nixpkgs/trunk/; revision=10369
2008-01-29 02:24:54 +01:00
* PGF 2.00 (keeping the old one so that I can still build old documents). svn path=/nixpkgs/trunk/; revision=12999
2008-10-08 16:03:44 +02:00
pgf = pgf2;
# Keep the old PGF since some documents don't render properly with
# the new one.
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
pgf1 = callPackage ../tools/typesetting/tex/pgf/1.x.nix { };
* PGF 2.00 (keeping the old one so that I can still build old documents). svn path=/nixpkgs/trunk/; revision=12999
2008-10-08 16:03:44 +02:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
pgf2 = callPackage ../tools/typesetting/tex/pgf/2.x.nix { };
all-packages.nix: stripped trailing whitespace svn path=/nixpkgs/trunk/; revision=33452
2012-03-28 15:49:16 +02:00
OOPS: typo svn path=/nixpkgs/trunk/; revision=33068
2012-03-14 18:25:49 +01:00
pgfplots = callPackage ../tools/typesetting/tex/pgfplots { };
* Added pgf/tikz. * runLaTeX: allow additional TeX packages to be specified. * teTeX setup hook: TEXMFNIX doesn't seem to work, use TEXINPUTS. svn path=/nixpkgs/trunk/; revision=8261
2007-03-11 00:51:59 +01:00
Enabled access to binaries of needed tools, and worker daemons can be enabled for phabricator #3306
2014-07-17 12:51:17 +02:00
phabricator = callPackage ../misc/phabricator { };
Adding pjsip (pjproject-1.8) svn path=/nixpkgs/trunk/; revision=25531
2011-01-13 10:23:40 +01:00
pjsip = callPackage ../applications/networking/pjsip { };
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
polytable = callPackage ../tools/typesetting/tex/polytable { };
add cups svn path=/nixpkgs/trunk/; revision=4114
2005-10-21 15:06:43 +02:00
PPSSPP: 0.9.8
2014-05-27 05:22:24 +02:00
PPSSPP = callPackage ../misc/emulators/ppsspp { };
Added UAE: Ultimate Amiga Emulator svn path=/nixpkgs/trunk/; revision=27541
2011-06-26 21:49:51 +02:00
uae = callPackage ../misc/emulators/uae { };
* Add "gtk" to the top-level scope (just like "glib") and remove all those "inherit (gtkLibs) gtk" lines. svn path=/nixpkgs/trunk/; revision=23699
2010-09-09 18:48:13 +02:00
putty = callPackage ../applications/networking/remote/putty { };
nixpkgs dir: nvidia and libsrvg svn path=/nixpkgs/trunk/; revision=8785
2007-05-28 16:10:46 +02:00
add retroarch 0.9.9
2013-06-26 13:25:09 +02:00
retroarch = callPackage ../misc/emulators/retroarch { };
add retroarchMaster package
2014-09-02 09:55:19 +02:00
retroarchMaster = callPackage ../misc/emulators/retroarch/master.nix { };
add retroarch 0.9.9
2013-06-26 13:25:09 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
rssglx = callPackage ../misc/screensavers/rss-glx { };
* add busybox * uclibc needs mktemp svn path=/nixpkgs/trunk/; revision=4969
2006-03-02 19:17:45 +01:00
xlockmore: dropped support for obsolete getConfig mechanism If you want to build xlockmore without support for PAM, override { pam = null; } instead. svn path=/nixpkgs/trunk/; revision=27891
2011-07-21 22:58:41 +02:00
xlockmore = callPackage ../misc/screensavers/xlockmore { };
Add XLockmore, a screen locker for X11. Currently, password authentication doesn't work. svn path=/nixpkgs/trunk/; revision=10701
2008-02-15 11:40:20 +01:00
Package Samsung unified printer driver. i686 only but apparently can be improved to support x86_64. Based on patch by James Cook <james.cook[NOSPAM]@utoronto.ca>
2012-12-05 04:37:44 +01:00
samsungUnifiedLinuxDriver = import ../misc/cups/drivers/samsung {
inherit fetchurl stdenv;
inherit cups ghostscript glibc patchelf;
gcc = import ../development/compilers/gcc/4.4 {
gcc: use texinfo4, fix bad mpfr reference
2013-06-30 22:25:30 +02:00
inherit stdenv fetchurl gmp mpfr noSysDirs gettext which;
texinfo = texinfo4;
Package Samsung unified printer driver. i686 only but apparently can be improved to support x86_64. Based on patch by James Cook <james.cook[NOSPAM]@utoronto.ca>
2012-12-05 04:37:44 +01:00
profiledCompiler = true;
};
};
SANE: switch snapshot version of the backends to git (and general cleanup)
2012-11-26 16:17:31 +01:00
saneBackends = callPackage ../applications/graphics/sane/backends.nix {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
gt68xxFirmware = config.sane.gt68xxFirmware or null;
sane: add support for Epson snapscan scanners The firmware file needs to be downloaded or extracted from the windows driver file and configured in nixpkgs.config e.g.: sane.snapscanFirmware = /firmware/esfw41.bin;
2013-08-25 21:19:21 +02:00
snapscanFirmware = config.sane.snapscanFirmware or null;
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
hotplugSupport = config.sane.hotplugSupport or true;
upgrade some packages to libusb1 on my systems, I can now override "libusb = libusb1" in all of nixpkgs so perhaps we can soon drop libusb 0.1 support?
2013-06-28 23:04:28 +02:00
libusb = libusb1;
Various.. Added ircd-hybrid. Added USB support in SANE. Added Xsane. Added gt68xx firmware support. svn path=/nixpkgs/trunk/; revision=9070
2007-08-08 22:33:36 +02:00
};
SANE: switch snapshot version of the backends to git (and general cleanup)
2012-11-26 16:17:31 +01:00
saneBackendsGit = callPackage ../applications/graphics/sane/backends-git.nix {
Remove getConfig helper function An expression like ‘getConfig [ "cabal" "libraryProfiling" ] false’ can be written more concisely as ‘config.cabal.libraryProfiling or false’.
2012-09-19 19:56:56 +02:00
gt68xxFirmware = config.sane.gt68xxFirmware or null;
sane: add support for Epson snapscan scanners The firmware file needs to be downloaded or extracted from the windows driver file and configured in nixpkgs.config e.g.: sane.snapscanFirmware = /firmware/esfw41.bin;
2013-08-25 21:19:21 +02:00
snapscanFirmware = config.sane.snapscanFirmware or null;
SANE: switch snapshot version of the backends to git (and general cleanup)
2012-11-26 16:17:31 +01:00
hotplugSupport = config.sane.hotplugSupport or true;
Various.. Added ircd-hybrid. Added USB support in SANE. Added Xsane. Added gt68xx firmware support. svn path=/nixpkgs/trunk/; revision=9070
2007-08-08 22:33:36 +02:00
};
sane: add mkSaneConfig
2014-05-11 20:30:33 +02:00
mkSaneConfig = callPackage ../applications/graphics/sane/config.nix { };
SANE: switch snapshot version of the backends to git (and general cleanup)
2012-11-26 16:17:31 +01:00
saneFrontends = callPackage ../applications/graphics/sane/frontends.nix { };
add libpcap, ethereal, sane-backends svn path=/nixpkgs/trunk/; revision=4213
2005-11-03 21:00:43 +01:00
Dashify seafileShared and seafileClient
2014-02-05 18:25:43 +01:00
seafile-shared = callPackage ../misc/seafile-shared { };
Add packages for libzdb, libsearpc, ccnet, seafile-shared, and seafile-client
2014-02-04 20:02:46 +01:00
misc/screensavers/slock: New nixpkg. svn path=/nixpkgs/trunk/; revision=29326
2011-09-17 19:40:07 +02:00
slock = callPackage ../misc/screensavers/slock { };
put all source with tags stuff into its own file, now appends tag files to TAG_FILES env var using nix-support updated myEnvFun svn path=/nixpkgs/trunk/; revision=12097
2008-06-15 13:54:22 +02:00
sourceAndTags = import ../misc/source-and-tags {
moved hasktags to ghc68executables, updated url to new location svn path=/nixpkgs/trunk/; revision=12680
2008-08-21 13:07:44 +02:00
inherit pkgs stdenv unzip lib ctags;
drop myhasktags, current hackage version has everything my version had
2014-01-23 14:44:21 +01:00
hasktags = haskellPackages.hasktags;
put all source with tags stuff into its own file, now appends tag files to TAG_FILES env var using nix-support updated myEnvFun svn path=/nixpkgs/trunk/; revision=12097
2008-06-15 13:54:22 +02:00
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
splix = callPackage ../misc/cups/drivers/splix { };
Add splix cups driver svn path=/nixpkgs/trunk/; revision=21078
2010-04-14 21:27:15 +02:00
New package: Streamripper: Record MP3 radio streams.
2014-01-17 01:13:57 +01:00
streamripper = callPackage ../applications/audio/streamripper { };
New package: sqsh. An SQL query tool/shell for Sybase/MSSQL
2014-06-20 18:38:05 +02:00
sqsh = callPackage ../development/tools/sqsh { };
svn merge ^/nixpkgs/trunk svn path=/nixpkgs/branches/libpng15/; revision=32099
2012-02-07 10:38:20 +01:00
tetex = callPackage ../tools/typesetting/tex/tetex { libpng = libpng12; };
add linuxwacom. Now, this is still without the driver for X (even though I don't know how that has to be used in X) svn path=/nixpkgs/trunk/; revision=4640
2006-01-31 16:18:27 +01:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
tex4ht = callPackage ../tools/typesetting/tex/tex4ht { };
Add tex4ht. svn path=/nixpkgs/trunk/; revision=19739
2010-01-31 13:13:33 +01:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texFunctions = import ../tools/typesetting/tex/nix pkgs;
* Added rss-glx, a collection of nice OpenGL screensavers. svn path=/nixpkgs/trunk/; revision=4614
2006-01-28 03:10:26 +01:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texLive = builderDefsPackage (import ../tools/typesetting/tex/texlive) {
Add potrace to texLive dependencies
2014-06-10 09:25:03 +02:00
inherit builderDefs zlib bzip2 ncurses libpng ed lesstif ruby potrace
Updating TeXLive to 2013 using updated Debian snapshots. Kept the old hacks where they don't break the build in case they things they fix are still relevant. I checked that the upgrade doesn't break: 1) Asymptote and EProver builds. 2) My XeLaTeX demo from configurations/ repository. 3) Some of my own files. The upgrade fixes problems with simultaneous use of 3D and LaTeX labels in Asymptote. Please provide a test that worked previously and is broken now if you need to revert this update or its parts.
2013-10-14 08:36:39 +02:00
gd t1lib freetype icu perl expat curl xz pkgconfig zziplib texinfo
texlive: upgrade to 20140528
2014-06-10 03:51:54 +02:00
libjpeg bison python fontconfig flex poppler libpaper graphite2
makeWrapper;
all-packages.nix changes for previous commits svn path=/nixpkgs/trunk/; revision=11217
2008-03-20 10:52:40 +01:00
inherit (xlibs) libXaw libX11 xproto libXt libXpm
Minor fix of "inherit"s. svn path=/nixpkgs/trunk/; revision=12708
2008-08-25 16:52:53 +02:00
libXmu libXext xextproto libSM libICE;
all-packages.nix changes for previous commits svn path=/nixpkgs/trunk/; revision=11217
2008-03-20 10:52:40 +01:00
ghostscript = ghostscriptX;
Updating TeXLive to 2013 using updated Debian snapshots. Kept the old hacks where they don't break the build in case they things they fix are still relevant. I checked that the upgrade doesn't break: 1) Asymptote and EProver builds. 2) My XeLaTeX demo from configurations/ repository. 3) Some of my own files. The upgrade fixes problems with simultaneous use of 3D and LaTeX labels in Asymptote. Please provide a test that worked previously and is broken now if you need to revert this update or its parts.
2013-10-14 08:36:39 +02:00
harfbuzz = harfbuzz.override {
graphite2: fix #2800 by setting INSTALL_NAME_DIR
2014-06-01 07:51:16 +02:00
withIcu = true; withGraphite2 = true;
Updating TeXLive to 2013 using updated Debian snapshots. Kept the old hacks where they don't break the build in case they things they fix are still relevant. I checked that the upgrade doesn't break: 1) Asymptote and EProver builds. 2) My XeLaTeX demo from configurations/ repository. 3) Some of my own files. The upgrade fixes problems with simultaneous use of 3D and LaTeX labels in Asymptote. Please provide a test that worked previously and is broken now if you need to revert this update or its parts.
2013-10-14 08:36:39 +02:00
};
all-packages.nix changes for previous commits svn path=/nixpkgs/trunk/; revision=11217
2008-03-20 10:52:40 +01:00
};
all-packages.nix: added texLiveFull attribute, which is a working TexLive installation with all supported packages enabled svn path=/nixpkgs/trunk/; revision=31717
2012-01-19 21:45:17 +01:00
texLiveFull = lib.setName "texlive-full" (texLiveAggregationFun {
paths = [ texLive texLiveExtra lmodern texLiveCMSuper texLiveLatexXColor
all-packages.nix: remove redundant texinfo5 overrides Texinfo 5.x is the default version now.
2014-01-21 20:29:34 +01:00
texLivePGF texLiveBeamer texLiveModerncv tipa tex4ht texinfo
Add moderntimeline extension for moderncv.
2013-06-15 12:58:21 +02:00
texLiveModerntimeline ];
all-packages.nix: added texLiveFull attribute, which is a working TexLive installation with all supported packages enabled svn path=/nixpkgs/trunk/; revision=31717
2012-01-19 21:45:17 +01:00
});
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
/* Look in configurations/misc/raskin.nix for usage example (around revisions
where TeXLive was added)
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
(texLiveAggregationFun {
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
paths = [texLive texLiveExtra texLiveCMSuper
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
texLiveBeamer
];
Big breaking change. I have radically reduced number of nulls used in all-packages.nix and generally switched to composedArgsAndFun which simply adds .meta.function to everything that has come through it.. I have not tested the build, because OO.o has to be updated... svn path=/nixpkgs/trunk/; revision=12625
2008-08-15 00:04:30 +02:00
})
Some more details about texLiveAggregation in comment svn path=/nixpkgs/trunk/; revision=11832
2008-05-16 06:52:47 +02:00
You need to use texLiveAggregationFun to regenerate, say, ls-R (TeX-related file list)
Just installing a few packages doesn't work.
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
*/
texliveAggregationFunction: fix eval vcunat edited to fix all cases (not just asymptote), and a two "licnese" typos :-)
2013-09-02 23:53:36 +02:00
texLiveAggregationFun = params:
builderDefsPackage (import ../tools/typesetting/tex/texlive/aggregate.nix)
Updating TeXLive to 2013 using updated Debian snapshots. Kept the old hacks where they don't break the build in case they things they fix are still relevant. I checked that the upgrade doesn't break: 1) Asymptote and EProver builds. 2) My XeLaTeX demo from configurations/ repository. 3) Some of my own files. The upgrade fixes problems with simultaneous use of 3D and LaTeX labels in Asymptote. Please provide a test that worked previously and is broken now if you need to revert this update or its parts.
2013-10-14 08:36:39 +02:00
({inherit poppler perl makeWrapper;} // params);
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texDisser = callPackage ../tools/typesetting/tex/disser {};
all-packages.nix entry for disser svn path=/nixpkgs/trunk/; revision=29231
2011-09-12 22:50:32 +02:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texLiveContext = builderDefsPackage (import ../tools/typesetting/tex/texlive/context.nix) {
Added font building support to builder-defs; made realCurl configurable; added Linux Libertine font; added ConTEXt svn path=/nixpkgs/trunk/; revision=11739
2008-04-28 12:10:44 +02:00
inherit texLive;
};
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texLiveExtra = builderDefsPackage (import ../tools/typesetting/tex/texlive/extra.nix) {
TeXLive: update to 2012 snapshot from Debian
2012-07-13 16:18:52 +02:00
inherit texLive xz;
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
};
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texLiveCMSuper = builderDefsPackage (import ../tools/typesetting/tex/texlive/cm-super.nix) {
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
inherit texLive;
};
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texLiveLatexXColor = builderDefsPackage (import ../tools/typesetting/tex/texlive/xcolor.nix) {
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
inherit texLive;
};
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texLivePGF = builderDefsPackage (import ../tools/typesetting/tex/texlive/pgf.nix) {
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
inherit texLiveLatexXColor texLive;
};
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texLiveBeamer = builderDefsPackage (import ../tools/typesetting/tex/texlive/beamer.nix) {
TeXLive. Now more configurable, and more options included. Beamer class for conference slides added. Before asking questions, look in configurations/misc/raskin.nix or in all-packages.nix . svn path=/nixpkgs/trunk/; revision=11257
2008-03-22 14:04:04 +01:00
inherit texLiveLatexXColor texLivePGF texLive;
};
all-packages.nix changes for previous commits svn path=/nixpkgs/trunk/; revision=11217
2008-03-20 10:52:40 +01:00
Moved all LaTeX expressions into tools/typesetting hierarchy. svn path=/nixpkgs/trunk/; revision=32028
2012-02-04 10:31:07 +01:00
texLiveModerncv = builderDefsPackage (import ../tools/typesetting/tex/texlive/moderncv.nix) {
moderncv: cleanup the build instructions Just add this package to texLiveAggregationFun to install it. svn path=/nixpkgs/trunk/; revision=27765
2011-07-13 18:23:48 +02:00
inherit texLive unzip;
Added moderncv package to texlive. svn path=/nixpkgs/trunk/; revision=27762
2011-07-13 17:00:59 +02:00
};
Add moderntimeline extension for moderncv.
2013-06-15 12:58:21 +02:00
texLiveModerntimeline = builderDefsPackage (import ../tools/typesetting/tex/texlive/moderntimeline.nix) {
inherit texLive unzip;
};
Add thermald: Linux Thermal Daemon
2014-08-14 02:17:55 +02:00
thermald = callPackage ../tools/system/thermald { };
add thinkfan package
2013-04-06 00:34:50 +02:00
thinkfan = callPackage ../tools/system/thinkfan { };
libX11 is not in vice's rpath. this fixes it
2013-09-04 22:34:08 +02:00
vice = callPackage ../misc/emulators/vice {
libX11 = xlibs.libX11;
Use old giflib for packages which lack new versions/compatibility patches for giflib5
2013-12-08 11:36:46 +01:00
giflib = giflib_4_1;
libX11 is not in vice's rpath. this fixes it
2013-09-04 22:34:08 +02:00
};
all-packages.nix: add adns library This commit also adds the combinator 'getPkgConfig', which ADNS uses to let the user enable/disable static linking of the library. The behavior of the adns expression can be customized in ~/.nixpkgs/config.nix by setting, i.e., "adns = { version = "1.4"; static = true; };". svn path=/nixpkgs/trunk/; revision=12155
2008-06-19 00:48:34 +02:00
viewnior: Add viewnior, GTK image viewer program
2013-03-12 20:43:37 +01:00
viewnior = callPackage ../applications/graphics/viewnior { };
Allow nix-env recurse into vimPlugins
2014-06-16 23:37:37 +02:00
vimPlugins = recurseIntoAttrs (callPackage ../misc/vim-plugins { });
vim: supporting multiple sources: - vim-nox: client-server implementation without X - latest: latest mercurial sources (still very stable) - default: latest release vim-plugins: Introduce an area to put vim plugins which are worth adding to nix because they need more effort than just "unpacking". Document that
2013-05-27 18:29:35 +02:00
Adding vimprobable2. Patch by Alexander Forenmy. svn path=/nixpkgs/trunk/; revision=31303
2012-01-04 23:12:43 +01:00
vimprobable2 = callPackage ../applications/networking/browsers/vimprobable2 {
get rid of old webkit and webkit_gtk2 packages
2014-03-30 03:02:07 +02:00
webkit = webkitgtk2;
Adding vimprobable2. Patch by Alexander Forenmy. svn path=/nixpkgs/trunk/; revision=31303
2012-01-04 23:12:43 +01:00
};
Adding wrapFirefox for midori and vimprobable2, so they can enjoy the flash plugin. OTH, I'd prefer naming the attributes like "midoriWrapped" instead of "midoriWrapper". But I chose the 2nd to follow the example of those already in all-packages. svn path=/nixpkgs/trunk/; revision=33406
2012-03-25 15:59:17 +02:00
vimprobable2Wrapper = wrapFirefox
{ browser = vimprobable2; browserName = "vimprobable2"; desktopName = "Vimprobable2";
};
New package: The vimb web browser
2014-02-12 19:42:39 +01:00
vimb = callPackage ../applications/networking/browsers/vimb {
get rid of old webkit and webkit_gtk2 packages
2014-03-30 03:02:07 +02:00
webkit = webkitgtk2;
New package: The vimb web browser
2014-02-12 19:42:39 +01:00
};
vimbWrapper = wrapFirefox {
browser = vimb;
browserName = "vimb";
desktopName = "Vimb";
};
Added VisualBoy advance; a gameboy/gameboy color/gameboy advance emulator svn path=/nixpkgs/trunk/; revision=27904
2011-07-22 20:31:42 +02:00
VisualBoyAdvance = callPackage ../misc/emulators/VisualBoyAdvance { };
all-packages.nix: stripped trailing whitespace svn path=/nixpkgs/trunk/; revision=27924
2011-07-24 22:26:33 +02:00
* Use callPackage_i686 for i686-only packages. svn path=/nixpkgs/trunk/; revision=23113
2010-08-11 15:25:30 +02:00
# Wine cannot be built in 64-bit; use a 32-bit build instead.
Merge remote-tracking branch 'origin/master' into stdenv-updates. Conflicts: pkgs/top-level/all-packages.nix
2013-10-26 18:28:05 +02:00
wineStable = callPackage_i686 ../misc/emulators/wine/stable.nix {
wine: doesn't build with bison3
2013-10-09 11:48:54 +02:00
bison = bison2;
};
Remove comment
2014-03-10 15:26:06 +01:00
Merge remote-tracking branch 'origin/master' into stdenv-updates. Conflicts: pkgs/top-level/all-packages.nix
2013-10-26 18:28:05 +02:00
wineUnstable = lowPrio (callPackage_i686 ../misc/emulators/wine/unstable.nix {
bison = bison2;
});
Remove comment
2014-03-10 15:26:06 +01:00
Make 1.6 the default Wine version and call 1.7.4 wineUnstable
2013-10-21 19:25:56 +02:00
wine = wineStable;
Added xmove - proxy X server which can move its clients to another one. Useful with Xvfb - so you can save your X session during needed reload of X. svn path=/nixpkgs/trunk/; revision=8917
2007-06-25 23:46:18 +02:00
add winetricks, modified by vcunat@gmail.com Originally from #89.
2013-02-03 19:06:51 +01:00
winetricks = callPackage ../misc/emulators/wine/winetricks.nix {
inherit (gnome2) zenity;
};
Adding back the 1.5 expression of mupen64plus It has a GUI, for example.
2013-03-28 18:16:40 +01:00
wxmupen64plus = callPackage ../misc/emulators/wxmupen64plus { };
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
x2x = callPackage ../tools/X11/x2x { };
Adding x2x. Patch by Oleksandr Kozachuk svn path=/nixpkgs/trunk/; revision=21796
2010-05-16 18:23:17 +02:00
xboxdrv: 0.8.5
2014-05-29 04:22:34 +02:00
xboxdrv = callPackage ../misc/drivers/xboxdrv { };
added xinput_calibrator v0.7.5
2014-08-24 22:16:24 +02:00
xinput_calibrator = callPackage ../tools/X11/xinput_calibrator {
inherit (xlibs) libXi inputproto;
};
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
xosd = callPackage ../misc/xosd { };
added xosd svn path=/nixpkgs/trunk/; revision=11340
2008-03-29 01:49:26 +01:00
SANE: switch snapshot version of the backends to git (and general cleanup)
2012-11-26 16:17:31 +01:00
xsane = callPackage ../applications/graphics/sane/xsane.nix {
Updating xsane, and making it build with the old libpng. The previous url is gone. svn path=/nixpkgs/trunk/; revision=32862
2012-03-07 22:59:48 +01:00
libpng = libpng12;
SANE: switch snapshot version of the backends to git (and general cleanup)
2012-11-26 16:17:31 +01:00
saneBackends = saneBackends;
Updating xsane, and making it build with the old libpng. The previous url is gone. svn path=/nixpkgs/trunk/; revision=32862
2012-03-07 22:59:48 +01:00
};
Various.. Added ircd-hybrid. Added USB support in SANE. Added Xsane. Added gt68xx firmware support. svn path=/nixpkgs/trunk/; revision=9070
2007-08-08 22:33:36 +02:00
* Use callPackage for most packages in all-packages.nix. `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
2010-08-02 18:26:58 +02:00
yafc = callPackage ../applications/networking/yafc { };
Adding yafc-1.1.1 svn path=/nixpkgs/trunk/; revision=13846
2009-01-25 15:31:51 +01:00
yandex-disk: add the Yandex.Disk cloud storage client Details: http://help.yandex.com/disk/cli-clients.xml
2013-11-18 11:00:13 +01:00
yandex-disk = callPackage ../tools/filesystems/yandex-disk { };
update my_env. Hopefully does a better job now svn path=/nixpkgs/trunk/; revision=13037
2008-10-10 00:57:20 +02:00
myEnvFun = import ../misc/my-env {
inherit substituteAll pkgs;
inherit (stdenv) mkDerivation;
};
put all source with tags stuff into its own file, now appends tag files to TAG_FILES env var using nix-support updated myEnvFun svn path=/nixpkgs/trunk/; revision=12097
2008-06-15 13:54:22 +02:00
simplify env-patoline and circumvert the bug with libgcc_s.so.1
2013-06-08 09:25:34 +02:00
# patoline requires a rather large ocaml compilation environment.
# this is why it is build as an environment and not just a normal package.
# remark : the emacs mode is also installed, but you have to adjust your load-path.
PatolineEnv = pack: myEnvFun {
name = "patoline";
buildInputs = [ stdenv ncurses mesa freeglut libzip gcc
Add moderntimeline extension for moderncv.
2013-06-15 12:58:21 +02:00
pack.ocaml pack.findlib pack.camomile
all-packages.nix: use blanks instead of tabs
2013-06-15 17:13:00 +02:00
pack.dypgen pack.ocaml_sqlite3 pack.camlzip
pack.lablgtk pack.camlimages pack.ocaml_cairo
pack.lablgl pack.ocamlnet pack.cryptokit
pack.ocaml_pcre pack.patoline
];
simplify env-patoline and circumvert the bug with libgcc_s.so.1
2013-06-08 09:25:34 +02:00
# this is to circumvent the bug with libgcc_s.so.1 which is
Add moderntimeline extension for moderncv.
2013-06-15 12:58:21 +02:00
# not found when using thread
simplify env-patoline and circumvert the bug with libgcc_s.so.1
2013-06-08 09:25:34 +02:00
extraCmds = ''
LD_LIBRARY_PATH=\$LD_LIBRARY_PATH:${gcc.gcc}/lib
export LD_LIBRARY_PATH
'';
adobe-reader: Update to 9.5.5
2013-11-04 18:42:28 +01:00
};
simplify env-patoline and circumvert the bug with libgcc_s.so.1
2013-06-08 09:25:34 +02:00
adobe-reader: Update to 9.5.5
2013-11-04 18:42:28 +01:00
patoline = PatolineEnv ocamlPackages_4_00_1;
simplify env-patoline and circumvert the bug with libgcc_s.so.1
2013-06-08 09:25:34 +02:00
Adding ZNC, irc bouncer.
2013-06-06 23:08:24 +02:00
znc = callPackage ../applications/networking/znc { };
znc: add support for modules, add fish and push module Close #1148.
2013-10-30 09:54:40 +01:00
zncModules = recurseIntoAttrs (
callPackage ../applications/networking/znc/modules.nix { }
);
zsnes: patches for modern gcc & libpng builds fine on stdenv-updates now needs gcc 4.8+, so keep this commit on stdenv-updates until merge
2013-10-09 08:15:39 +02:00
zsnes = callPackage_i686 ../misc/emulators/zsnes { };
Added ZSNES emulator package svn path=/nixpkgs/trunk/; revision=27539
2011-06-26 00:25:50 +02:00
added snes9x-gtk with pulseaudio support
2014-07-20 10:39:42 +02:00
snes9x-gtk = callPackage ../misc/emulators/snes9x-gtk { };
Higan - new package (alpha stage!) Higan is a cycle-accurate Nintendo multi-system emulator It is a preliminary release for Nix - I need to investigate some issues about install process and hardcoded paths...
2014-08-08 21:34:41 +02:00
higan = callPackage ../misc/emulators/higan { };
adding cdtEnv symlinking deps into one $out/cdt-env/{lib,include} directory and collection which let's you install and update a set of derivations at once svn path=/nixpkgs/trunk/; revision=16224
2009-07-07 22:53:16 +02:00
misc = import ../misc/misc.nix { inherit pkgs stdenv; };
Updated CMake to version 2.6.3. svn path=/nixpkgs/trunk/; revision=15114
2009-04-17 15:48:22 +02:00
Adding bullet. Patch by Alexander Foremny. svn path=/nixpkgs/trunk/; revision=32393
2012-02-19 11:51:04 +01:00
bullet = callPackage ../development/libraries/bullet {};
Now using callPackage.
2013-04-17 19:38:02 +02:00
dart = callPackage ../development/interpreters/dart { };
Added Dart SDK M4
2013-04-17 16:35:40 +02:00
Added httrack, website copier tool
2013-07-25 10:21:22 +02:00
httrack = callPackage ../tools/backup/httrack { };
MicroGNUEmacs, a.k.a. MG
2013-07-30 15:53:00 +02:00
mg = callPackage ../applications/editors/mg { };
Added httrack, website copier tool
2013-07-25 10:21:22 +02:00
adobe-reader: Update to 9.5.5
2013-11-04 18:42:28 +01:00
# Attributes for backward compatibility.
adobeReader = adobe-reader;
asciidoc-full: rename attribute from asciidocFull But keep asciidocFull attribute for backwards compatibility (with a timestamp so we can later decide when to finally remove the old attribute).
2014-06-22 22:24:27 +02:00
asciidocFull = asciidoc-full; # added 2014-06-22
lttng: align attribute name with package name lttngModules => lttng-modules lttngTools => lttng-tools lttngUst => lttng-ust But keep the old attributes around for backward compatibility.
2014-07-31 15:48:06 +02:00
lttngTools = lttng-tools; # added 2014-07-31
lttngUst = lttng-ust; # added 2014-07-31
adobe-reader: Update to 9.5.5
2013-11-04 18:42:28 +01:00
Remove uses of __overrides feature In addition to replacing use of a feature with IMO confusing semantics, this will also let us cleanly separate out all-packages.nix into category-specific files without changing the structure of the pkgs attrset. Signed-off-by: Shea Levy <shea@shealevy.com>
2013-12-30 17:04:45 +01:00
}; in self; in pkgs
Reference in a new issue Copy permalink