On Wed, Feb 29, 2012 at 08:02:11PM -0500, Albert Y. C. Lai wrote: > > It is possible to fish the output of "cabal install --dry-run -v3 > hoogle" for why array-0.3.0.3 is brought in. It really is fishing, > since the output is copious and of low information density. Chinese > idiom: needle in ocean (haystack is too easy). Example: > > "selecting hoogle-4.2.8 (hackage) and discarding Cabal-1.1.6, 1.2.1, > 1.2.2.0, > 1.2.3.0, 1.2.4.0, 1.4.0.0, 1.4.0.1, 1.4.0.2, 1.6.0.1, 1.6.0.2, 1.6.0.3, > 1.14.0, blaze-builder-0.1, case-insensitive-0.1," > > We see that selecting hoogle-4.2.8 causes ruling out Cabal 1.14.0 > > Similarly, the line for "selecting Cabal-1.12.0" mentions ruling out > array-0.4.0.0
I wonder about the possibility of making a simple tool to parse the output of cabal install -v3 and visualize/organize it in some sort of way to make this process easier. What might such visualization/organization look like? -Brent _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
