So its great everyone is sharing but this thread was started with a simple discussion point.
The adding of additional dependencies of mtl, haskeline, terminfo (and maybe utf8-string) to GHC and how it's handled by Haskell Platform and other packagers. The outcome I take to be that this is mostly acceptable except for perhaps utf8-stirng which shouldn't be an issue once haskeline 0.7 is released. On 26 March 2012 05:14, Judah Jacobson <judah.jacob...@gmail.com> wrote: > On Sun, Mar 25, 2012 at 3:48 PM, Mark Lentczner <m...@glyphic.com> wrote: >> >> While I think haskeline and terminfo will not have a big effect, utf8-string >> is a sad regression. I don't think that we'll be happy stating that as part >> of the "batteries included", as we feel Text is the long term position. I'm >> assuming that haskeline use of utf8-string is the reason? Any chance we can >> get haskeline rev'd to use text? > > The next release of haskeline (0.7) will not need utf8-string (or > text). Instead, when built with ghc-7.4 and later, it will just use > the base library's I/O encoding functionality. (I should be able to > complete haskeline-0.7 well before ghc-7.6.1 is released.) > > Best, > -Judah > > _______________________________________________ > Haskell-platform mailing list > Haskell-platform@projects.haskell.org > http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform _______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
