Markus Mottl <markus.mottl@gmail.com> said by email to me that
``Note that this link is served by a Mercurial Apache module, i.e. this
is not static content. It's likely that e.g. tar or bzip2 produce
slightly different output, which would explain changing hashes.
So I guess we shouldn't worry too much about the change in hash?
svn path=/nixpkgs/trunk/; revision=33419
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
- cabal2nix: updated to version 1.30
- cmdargs: updated to version 0.9.5
- derive: updated to version 2.5.6
- hlint: updated to version 1.8.25
- io-choice: added version 0.0.1
svn path=/nixpkgs/trunk/; revision=33411
This expression can now be generated by cabal2nix. Note that it doesn't
propagate Emacs and haskell-mode, though, these dependencies must be
installed by the user in addition to ghc-mod.
To active ghc-mod, add the following snippet to your ~/.emacs file:
(autoload 'ghc-init "ghc" nil t)
(add-hook 'haskell-mode-hook (lambda () (ghc-init)))
svn path=/nixpkgs/trunk/; revision=33410
Linking these libraries makes sure that they can be found at run-time,
because a proper rpath into the Nix store is added to the generated
executable. Without that rpath, nbd-server will try to load the system's
libpthread.so.0, which may not be what we want.
svn path=/nixpkgs/trunk/; revision=33408
You can now set the forwardX11 config option for the ssh client and server separately.
For server, the option means "allow clients to request X11 forwarding".
For client, the option means "request X11 forwarding by default on all connections".
I don't think it made sense to couple them. I might not even run the server on some machines.
Also, I ssh to a lot of machines, and rarely want X11 forwarding. The times I want it,
I use the -X/-Y option, or set it in my ~/.ssh/config.
I also decoupled the 'XAuthLocation' logic from forwardX11.
For my case where ssh client doesn't want forwarding by default, it still wants to set the path for the cases I do need it.
As this flag is the one that pulls in X11 dependencies, I changed the minimal profile and the no-x-libs config to check that instead now.
svn path=/nixos/trunk/; revision=33407
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
- LambdaHack: updated to version 0.2.1
- OpenAL: updated to version 1.4.0.1
- cabal2nix: updated to version 1.29
- unbound: updated to version 0.4.0.1
svn path=/nixpkgs/trunk/; revision=33394
By now, it happened twice that a commit broke GHC and thus all Haskell packages
we have in Nixpkgs. On such an occasion, I receive well in excess of 3000
notification e-mails from Hydra, and then I receive another 3000 e-mails after
the bug has been fixed. Under these circumstances, subscribing to these
notifications makes no sense for me.
svn path=/nixpkgs/trunk/; revision=33392
delete routes and addresses when it quits. This causes those routes
and addresses to stick around forever, since dhcpcd won't delete
them when it runs next (even if it acquires a new lease on the same
interface). This is bad; in particular the stale (default) routes
can break networking.
The downside to removing "persistent" is that you should never ever
do "stop dhcpcd" on a remote machine configured by dhcpcd.
svn path=/nixos/trunk/; revision=33388
Russell O'Connor