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
On MacOS X, we used to use the native perl interpreter from /usr/bin.
Unfortunately, that interpreter fails to build a number of packages
(Subversion, Git, etc. ...), because it assumes knowledge about the underlying
C compiler that is not valid for the compiler used by Nix. For example,
/usr/bin/perl assumes that the compiler can build binaries for both the ppc and
the x86 architecture. /usr/bin/FCC can do that, but the gcc from Nix can't.
The solution is to compile Perl 5.10 via Nix so that it can properly configure
itself. However, note that the resulting binary is impure: it will find headers
in /usr/include and libraries in /usr/lib -- something a pure perl binary
wouldn't do. In this respect our Nix-compiled perl binary is not better than
the native one from /usr/bin -- it's just more accurately configured.
svn path=/nixpkgs/trunk/; revision=17618
When building Emacs on MacOS X, the configure script believes that libXaw is
available and tries to link it (even when, in fact, libXaw is not available).
To work around that problem, we make Xaw support mandatory on MacOS X.
svn path=/nixpkgs/trunk/; revision=17610
They removed the url for that package version, I updated to the latest.
I changed the name from 'trueCrypt' to 'truecrypt'
I added an option for it not to have a gui built.
svn path=/nixpkgs/trunk/; revision=17587
The OpenSSH binaries built by the expression by default expect system-wide
configuration files in "/etc/ssh", which is a bit of an impurity (and certainly
inconsistent with the way other package handle --sysconfdir in Nix). Those who
prefer a clean installation, can now configure that directory path.
Adding the line "openssh = { etcDir = null; };" to $NIXPKGS_CONFIG configures
OpenSSH to use the default location, i.e. $out/etc. Setting that attribute to a
string will configure OpenSSH to use that concrete path instead.
svn path=/nixpkgs/trunk/; revision=17570
* Dropped classr.patch; it no longer applies to this version.
* The "configure" script has been renamed to "bootstrap.sh".
* The bootstrapping process generates no Makefile anymore; the build
expression has to call bjam directly to build the libraries.
* Perform build and install phase in one execution of bjam. This is a
lot faster, because bjam won't check the dependencies twice.
svn path=/nixpkgs/trunk/; revision=17471
configure script prints out this ominous warning:
WARNING: PolicyKit is disabled. You need to manually edit the hal.conf
file to lock down the service. Failure to do so allows any
caller to make hald do work on their behalf which may be
a huge SECURITY HOLE. I repeat: YOU NEED TO EDIT THE FILE
hal.conf to match your distro/site to avoid NASTY SECURITY HOLES.
Note that HAL only builds with the old PolicyKit (it looks for
polkit.pc). Reverted ConsoleKit to the last version that used the
old PolicyKit for this reason.
svn path=/nixpkgs/trunk/; revision=17432
a headache. "polkit" is the new, unstable release series.
"policykit" is the old series. (See
http://lists.freedesktop.org/archives/polkit-devel/2009-February/000106.html
for an "explanation" of the name change.) It seems that for HAL we
need to revert to the old "policykit", since it doesn't compile
against "polkit".
svn path=/nixpkgs/trunk/; revision=17425
