Armijn Hemel 0e6b2045ea we actually *do* have patchelf available and we want to use it to patch ... our freshly built glibc, otherwise we get weird blah errors svn path=/nixpkgs/branches/nixos-pkgs/; revision=2021		2005-01-14 11:45:16 +00:00
..
bash-static	don't let bash depend on tar and gzip	2004-10-19 11:50:04 +00:00
binutils-static	oops, don't forget binutils	2004-10-19 15:49:15 +00:00
bzip2-static	add quotes for tarball variable	2004-10-19 15:32:53 +00:00
coreutils-static	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
curl-static	our 7.12.0 was not resolving (thank you glibc!), replaced with statically linked (with uclibc) 7.12.2	2004-11-29 14:36:29 +00:00
diffutils-static	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
findutils-static	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
gawk-static	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
gcc-static	also add a statically linked gcc	2004-10-19 15:17:29 +00:00
gnugrep-static	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
gnumake-static	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
gnused-static	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
gnutar-static	work around Nix "logics" >-)	2004-10-19 12:15:22 +00:00
gzip-static	actually use $src instead of "bin", sigh	2004-10-19 14:52:59 +00:00
patchelf-static/bin	move patchelf in a directory, so it can play nice along with things	2005-01-14 11:41:26 +00:00
scripts	remove all other occurences of old glibc path	2004-12-06 19:20:15 +00:00
tools	add (refactored) static stuff	2004-11-04 12:20:54 +00:00
default.nix	move patchelf in a directory, so it can play nice along with things	2005-01-14 11:41:26 +00:00
path.nix	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
pkgs.nix	commit a whole bunch of statically linked packages. In the builder we add gzip to the PATH, because tar expects it to be there. This *should* be enough to bootstrap a whole new environment inside UML, give or take one or two packages I might have forgotten :)	2004-10-19 15:16:14 +00:00
prehook.sh	we actually *do* have patchelf available and we want to use it to patch	2005-01-14 11:45:16 +00:00