... | ... | @@ -218,7 +218,7 @@ role in which a library gets a big boost by being in the "blessed set" |
|
|
shipped with GHC.
|
|
|
|
|
|
|
|
|
Increasingly, therefore, we are trying to un-couple GHC from big
|
|
|
Increasingly, therefore, we are trying to decouple GHC from big
|
|
|
libraries. We ship GHC with a set of "boot" libraries, without which
|
|
|
GHC will not function at all, and "extra" libraries, which just happen
|
|
|
to come with some binary distributions of GHC, and which can be upgraded
|
... | ... | @@ -228,7 +228,7 @@ smaller packages, and expect to further split it up for GHC 6.10. |
|
|
This has led to lots of pain, because old programs
|
|
|
that depended on 'base' now need to depend on other packages too;
|
|
|
see [ upgrading packages](http://www.haskell.org/haskellwiki/Upgrading_packages) for details. But
|
|
|
it's good pain, and matters should improve too as Cabal matures. We
|
|
|
it's good pain, and matters should improve too as Cabal matures. We have been exploring possibilities for [lessening the pain](package-compatibility) in 6.10. We
|
|
|
have also devised a
|
|
|
[ package versioning policy](http://www.haskell.org/haskellwiki/Package_versioning_policy)
|
|
|
which will help future library upgrades. |
|
|
which will help future library upgrades. |