This package should only install the xmonad manpage but not GHC's (it
doesn't even install GHC in the path). Installing both manpages makes
this package conflict with the GHC derivation.
Fixes #60914
PR #1366
The previous windowManager.xmonad option only starts xmonad and
doesn't make ghc available. This assumes that the user has GHC with
access to the xmonad package in his PATH when using xmonad.
Xmonad in Nix is now patched to accept the XMONAD_{GHC,XMESSAGE}
environment variables which define the path to either ghc or xmessage.
These are set automatically when using xmonad through
windowManager.xmonad.
My (or specific: @aristidb and my) changes make it possible to use
Xmonad without adding GHC to any profile. This is useful if you want
to add a different GHC to your profile.
This commit introduces some options:
- xmonad.haskellPackages: Controls which Haskell package set & GHC set
is used to (re)build Xmonad
- xmonad.extraPackages: Function returning a list of additional
packages to make available to GHC when rebuilding Xmonad
- xmonad.enableContribExtras: Boolean option to build xmonadContrib
and xmonadExtras.
Signed-off-by: Moritz Ulrich <moritz@tarn-vedra.de>
- aeson: updated to version 0.6.0.1
- alex-meta: updated to version 0.3.0.3
- BNFC-meta: updated to version 0.3.0.1
- hakyll: updated to version 3.2.7.1
- happy-meta: updated to version 0.2.0.4
- http-enumerator: updated to version 0.7.3.2
- multiarg: updated to version 0.2.0.0
Disabled Haddock documentation for the following packages, because the
input crashes Haddock:
- BNFC-meta
- alex-meta
Re-enabled Haddock documentation for the following packages, because
previously occurring errors have been fixed:
- ConfigFile
- HDBC-odbc
- Hipmunk
- instant-generics
- RepLib
- type-equality
- xmonad
- xmonad-extras
- yesod-core
svn path=/nixpkgs/trunk/; revision=33559
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
