add the data for /etc/services. The reasons for this:

* you want to be able to deploy this sort of configuration. Various packages
will not be able to work correctly without this. The GNU C library has a
dependency on this, but we ignore it. glibc will happily build if this file
is missing, but resolving will sometimes fail if this file is not present
(syslog is one example)

* this information is fairly static and changed about once or twice a year.
It is maintained by IANA and cannot really be considered site-specific
configuration.

The package is not made a dependency for glibc, as a change here would
trigger a full recompilation, even though technically speaking it is a
runtime dependency using a fixed format (as dictated by IANA).


svn path=/nixpkgs/trunk/; revision=5004

2 files changed, 14 insertions, 0 deletions

diff --git a/pkgs/configs/etc/services/builder.sh b/pkgs/configs/etc/services/builder.sh
new file mode 100644
index 000000000000..c99ae258f266
--- /dev/null
+++ b/pkgs/configs/etc/services/builder.sh
@@ -0,0 +1,4 @@
+source $stdenv/setup
+
+ensureDir $out
+cp $src $out/services
diff --git a/pkgs/configs/etc/services/default.nix b/pkgs/configs/etc/services/default.nix
new file mode 100644
index 000000000000..d2d1830fd4cf
--- /dev/null
+++ b/pkgs/configs/etc/services/default.nix
@@ -0,0 +1,10 @@
+{stdenv, fetchurl}:
+
+stdenv.mkDerivation {
+  name = "etc-services-1.42";
+  builder = ./builder.sh;
+  src = fetchurl {
+    url = http://losser.labs.cs.uu.nl/~armijn/.nix/services.gz;
+    md5 = "093dbece9828e5e979081f3722858fb9";
+  };
+}