This allows the SheevaPlug to set up the network automatically with
DHCP, if the "ip=dhcp" kernel option is set.
svn path=/nixpkgs/trunk/; revision=34105
* There's a new file called haskell-defaults.nix.
* The new file contains:
- Default package version settings for each compiler version.
- All the stuff that previously still was in all-packages.nix.
* A relatively small part is left in all-packages.nix.
svn path=/nixpkgs/trunk/; revision=34088
- authenticate: updated to version 1.2.1.1
- blaze-html: added version 0.5.0.0 (unused right now because happstack can't deal with it)
- BNFC-meta: updated to version 0.3.0.2
- graphviz: patched build to succeed with transformers 0.3.x
- haskeline: updated to version 0.6.4.7
- http-conduit: updated to version 1.4.1.3
- numeric-prelude: updated to version 0.3.0.2
- pandoc: updated to version 1.9.3
svn path=/nixpkgs/trunk/; revision=34087
DB even in read-only mode. Should probably fix that. Also, "or" no
longer works like this because it's a keyword now.
svn path=/nixpkgs/trunk/; revision=34079
- haskell-src-exts: updated to version 1.13.3
- MemoTrie: updated to version 0.5
- semigroups: updated to version 0.8.3.2
- tagged: updated to version 0.4.2.1
- vector-space: updated to version 0.8.1
- WebBits: updated to version 2.2
svn path=/nixpkgs/trunk/; revision=34060
The new versions of mtl and transformers break many important packages, such as
monad-par, graphviz, pandoc, and all other packages that depend on any of those.
This situation causes serious problems for me, because I depend on some of those
packages for my daily work. IMHO, it is an overreaction to have all those builds
fail, because some day in the future a new version of Haskell Platform *may* be
released that *may* recommend the latest versions of 'transformers' and 'mtl'. As
long as those changes have such profound negative effects on our packages, those
upgrades should be deferred. This approach seems consistent with the way we've
handled these matters things in the past, too. For example, we happily break
conformance with older versions of HP, when those changes are beneficial for
users. In other words, we have usually valued usability over strict conformance
before, and IMHO that is a sensible policy.
I agree that it's nice to test what kind of trouble these upgrades cause, but I
don't believe that 'trunk' is the right place to perform those tests. The breakage
these changes cause affect users who rely on Nixpkgs to provide a stable working
environment.
svn path=/nixpkgs/trunk/; revision=34059
The current versions are the ones being proposed for the
new Haskell Platform. If they cause problems with other
packages, those packages should be fixed, not the defaults.
svn path=/nixpkgs/trunk/; revision=34043
- DSH: updated to version 0.7.8.1
- alex: updated to versino 3.0.2
- certificate: updated to version 1.2.2
- language-c: updated to version 0.4.2
- xhtml: updated to version 3000.2.1
Also, downgraded GHC 7.4.1 environment to use mtl 2.0 and transformers 2.0 to
avoid lots of build errors, i.e. with monad-par.
svn path=/nixpkgs/trunk/; revision=34042
This is supposed to make it easier to create locally modified
version preferences in Haskell package sets, by using override
on the extraPrefs attribute.
svn path=/nixpkgs/trunk/; revision=34031
Therefore I add recent linuxHeaders for it.
It's quite a hack to build it mixed with 2.6.35 headers and 3.3.5, but it builds at least.
svn path=/nixpkgs/trunk/; revision=34021
- abstract-deque: added version 0.1.5
- abstract-par: added version 0.3
- bits-atomic: added version 0.1.3
- blaze-builder-conduit: updated to version 0.4.0.2
- IORefCAS: added version 0.2
- MemoTrie: updated to version 0.4.12
- monad-par: added version 0.3
- monad-par-extras: added version 0.3
- repa: updated to version 3.1.4.2
- texmath: updated to version 0.6.0.6
svn path=/nixpkgs/trunk/; revision=34003
