The easiest way I found to build stackage recently was to take the cabal.config file [1] and then manipulate it to just install each package in turn.
cabal install package-1 cabal install package-2 This was quite a bit easier than using stackage-curator if you just want to build packages to check that they work [1]: https://www.stackage.org/lts-7.2/cabal.config Matt On Tue, Oct 4, 2016 at 9:38 AM, Simon Peyton Jones via ghc-devs <[email protected]> wrote: > Smoke-testing with Stackage would be a great idea. In the past Michael > Snoyman has kindly done that for us, but ultimately some automation would be > good. > > > > Simon > > > > From: ghc-devs [mailto:[email protected]] On Behalf Of Boespflug, > Mathieu > Sent: 04 October 2016 07:59 > To: Ben Gamari <[email protected]> > Cc: [email protected] > Subject: Re: GHC 8.0.2 status > > > > Hi Ben, > > > > while in the eye of the cyclone, as we're waiting for these last few OS X > issues to clear up... I was wondering, do you currently have a means to > "vet" release candidates before cutting a new release? > > > > More to the point, to check that a point release like these doesn't include > any breaking changes it might be useful to try compiling all of Stackage > with it, even if it's just once, much like the Stackage curators do. As you > may have seen a few hours ago, e.g. singletons doesn't compile using the > current GHC 8.0.2 candidate (tip of ghc-8.0 branch). It did compile just > fine using 8.0.1. And FWIW it also compiles okay with GHC HEAD. > > > > Likely this has been discussed before. So I'm just enquiring about status > regarding adding this item in the workflow. > > > > Best, > > > -- > Mathieu Boespflug > Founder at http://tweag.io. > > > > On 29 September 2016 at 19:54, Ben Gamari <[email protected]> wrote: > > Hello everyone, > > The week before ICFP I was able to get the ghc-8.0 branch ready for an > 8.0.2 release, which I intended to cut this week. In the intervening > time an additional rather serious issue was reported affected Mac OS X > Sierra (#12479). Since this issue affects the usability of GHC on the > new OS X release, we'll be deferring the 8.0.2 release until it has been > resolved. > > While there appears to be an actionable path forward on this ticket, we > will need someone with an affected machine and an understanding of GHC's > use of dynamic linking to step up to implement. Otherwise it looks like > the release will be delayed at least until October 9, when darchon has > time to have a look. > > Sorry to be the bearer of bad news! > > Cheers, > > - Ben > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > > > > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > _______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
