or just build ghc with the 1.18 cabal and keep it all the same :) On Tue, Nov 26, 2013 at 3:08 AM, Ivan Lazar Miljenovic < ivan.miljenovic@gmail.com> wrote:

On 26 November 2013 18:04, Mikhail Glushenkov wrote:

...

Hi,

On Tue, Nov 26, 2013 at 7:28 AM, Ivan Lazar Miljenovic wrote:

...

Hurt, no; but it will make it inconsistent across platforms (as Linux distros typically just have meta-packages for the Platform, rather than an installer that can do this).

You mean that Linux distros will have both 1.18 and 1.16, but 1.16 won't be hidden? Will this affect anything if 1.18 will be always chosen by default anyway?

No, but if the binary installers auto-hide 1.16, then there will be a difference between the various platforms.

-- Ivan Lazar Miljenovic Ivan.Miljenovic@gmail.com http://IvanMiljenovic.wordpress.com _______________________________________________ Libraries mailing list Libraries@haskell.org http://www.haskell.org/mailman/listinfo/libraries

I don't think there is an issue with building GHC: If you build GHC from source for packaging, it will build and use the version of the Cabal package that it is shipped with. This will put Cabal-1.16 in the package database. If you then build all the packages in the platform, that will build Cabal 1.18 and cabal-install 1.18 and add them to the package database as well. This will then exactly match the template of the platform, I think. ​ - Mark