Is there a way to include packages as second-class in the platform? I.e. "this package isn't 'blessed' but for now it's required by a package we really do want." Then we could work later to either bring the dependencies into the platform or rework the platform packages to exclude the non-platform dependency.
On Tue, Nov 26, 2013 at 5:19 AM, Mark Lentczner <mark.lentcz...@gmail.com>wrote: > My view of the conversation so far: > > 1) Aeson option 3 or 4 is desirable - we all want aeson, we don't want > blaze-builder > 2) dlist has generated a fair bit of discussion, but no clear agreement. > 3) no one has weighed in on scientific > > We need to come to rough consensus on these issues soon if we are to get > to aeson in this round. > > My opinion, with my "HP Release Manager" hat on: I'd like to see a version > of aeson-0.7 that didn't use dlist (just, ick, duplicated what it used in > it's innards), and either had the Scientific removed, or as part of aeson > itself (rather than as a separate package). I recognize the > sub-standardness of this solution, though it is forward compatible with > future evolutions (such as exposing dlist, and/or scientific). > > - Mark > > _______________________________________________ > Libraries mailing list > librar...@haskell.org > http://www.haskell.org/mailman/listinfo/libraries > > -- Gregory Collins <g...@gregorycollins.net>
_______________________________________________ Haskell-platform mailing list Haskell-platform@projects.haskell.org http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
