More platform packages

[Thomas Schilling]

What if you wanted to use a package outside of the platform?  If a
platform package depends on it you have to use the version that came
with the platform, otherwise you get diamond dependency issues.
Therefore, if one of the platform packages depends on a package with a
less stable API you, in practise, have to use the platform version.

I agree with Mark, platform packages must only depend on other
platform packages (perhaps, there may be exceptional cases, but
they'll be rare).

On 24 January 2013 07:29, Roman Cheplyaka <roma at ro-che.info> wrote:
> * Mark Lentczner <mark.lentczner at gmail.com> [2013-01-23 19:35:25-0800]
>> I'm with Chris on this: Once you've included it, it's in. That is - people
>> will code against those packages - because, well, there they are! "levels
>> of warranty" as listed on some web page aren't really going to imply much!
>
> What is bad, exactly, about the fact that people will code against those
> packages?
> Once again, people can code against those packages anyway by installing
> them from hackage.
> It's hard to imagine anyone who would restrain themselves to HP.
>
> (Not that I want to argue much about this, just trying to understand your
> concerns better.)
>
> By the way, it is possible to hide those packages (in the sense of
> ghc-pkg hide) by default. But first of all — what problem are we
> solving?
>
> Roman
>
> _______________________________________________
> Haskell-platform mailing list
> Haskell-platform at projects.haskell.org
> http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform