On Sun, Feb 27, 2011 at 10:05 AM, Don Stewart wrote:
> The problem -- after I refreshed my memory -- isn't that cabal-install can't
> handle itself as a tool dep.
Correct. But the haskell-platform.cabal file, as it is used to build
the source tarball, and then to the installers, is never fed to
The problem -- after I refreshed my memory -- isn't that cabal-install
can't handle itself as a tool dep. It is that we need a new release of
cabal-install to have a satisfiable package set in the HP in the first
place. Current cabal-install depends on old containers, preventing
everything from bui
All -
Don and I talked a bit about this at BayHac: The .cabal file for
Haskell Platform can't include cabal-install because (if I recall)
cabal can't handle cabal-install as a build-tool dependency. This
normally doesn't matter (I suppose) because if someone is using
haskell-platform.cabal to inst
