Including cabal-install in the platform source tarball
dons00 at gmail.com
Sun Feb 27 18:05:16 GMT 2011
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 building.
As soon as the new release goes up, we can add the explicit dep,
making everything work.
On Sun, Feb 27, 2011 at 7:45 AM, Mark Lentczner
<mark.lentczner at gmail.com> wrote:
> 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 install the platform, then they already must
> have cabal-install installed (though perhaps not the right version?)
> However, seems to me this make a glaring omission in the source
> tarball, since cabal-install isn't there. As i build the Mac OS X
> installer from that, cabal-install isn't showing up.
> I have a patch to src/generic/prepare.sh that uncomments
> cabal-install in a copy of haskell-platform.cabal before it is fed to
> Build.hs. This is (gack) done with sed. It would probably be better
> for the "OFFICIAL" haskell-platform.cabal file to include
> cabal-install, and then have some script comment it out for the "use
> this to cabal install the platform" .cabal file.
> Thoughts? In particular, is there any problem including cabal-install
> in the source tarball?
> - Mark
> Haskell-platform mailing list
> Haskell-platform at projects.haskell.org
More information about the Haskell-platform