Suggestion for resolving the Cabal/GHC dependency problems
Johan Tibell
johan.tibell at gmail.com
Wed Sep 11 20:03:07 UTC 2013
On Wed, Sep 11, 2013 at 12:19 PM, Duncan Coutts <
duncan.coutts at googlemail.com> wrote:
> Actually, this is not quite right. Since ghc would still ship Cabal (but
> not depend on it), it would also ship its dependencies including parsec,
> mtl and transformers. So they would need to be up to date and installed,
> it's just that ghc itself would not depend on them.
>
> If that's really inconvenient, it's plausible to have a minimal set
> which is just the things ghc depends on, so long as what gets shipped to
> users is the useful set, including Cabal.
I don't quite like how GHC's dependencies leak out to the rest of the
world. It makes it possible for us to decide what version we want to ship
in the platform of those libraries. I guess we don't have a good technical
solution to this problem though.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/ghc-devs/attachments/20130911/21d50c17/attachment.htm>
More information about the ghc-devs
mailing list