I was poking around the source for cabal-install while investigating a
(hopeful) GSoC product. One thing seems a little odd to me: is there a
reason that, for example, getAvailablePackages isn't in a separate library?
Or is similar functionality in a different package than Cabal already and I
just
On 22 March 2011 17:42, Frank Murphy wrote:
> I was poking around the source for cabal-install while investigating a
> (hopeful) GSoC product. One thing seems a little odd to me: is there a
> reason that, for example, getAvailablePackages isn't in a separate library?
> Or is similar functionality
#818: cabal sdist warns about optimization levels
-+--
Reporter: guest |Owner:
Type: defect | Status: new
Priority: normal |Milestone:
#819: Pass extra parameters of 'configure' to user hooks
+---
Reporter: guest |Owner:
Type: enhancement| Status: new
Priority: normal |Mile
On http://hackage.haskell.org/trac/hackage/ticket/447, it's suggested that
during parallel builds the output from child jobs simply shouldn't be
displayed at all. When it comes to dealing with concurrent logging, why not
have children write all log lines via queue to a master thread, then have
the
