[darcs-devel] Curl build issues

[David Roundy]

On Wed, Apr 16, 2008 at 9:38 AM, Eric Kow <eric.kow at gmail.com> wrote:
>  I'm guessing the appeal of having a Cabal file (even if what goes on
>  underneath is not very much Cabal) is that
>  (1) it would make it easier for us to say what modules libdarcs
>  exposes (we could still do it the old-fashioned way, but it's no
>  easier than cabal)
>  (2) it makes it easier for us to say what Haskell packages we need and

This, however, is a broken concept in cabal.  We don't need a fixed
set of packages.  The latest cabal allows one to stick conditionals in
the list, but that still doesn't account for the fact that
configuration choices affect the set of packages that are needed.

>  (3) it allows users to do dependency tracking via cabal-install.
>  Maybe this means we can use more third party libraries without
>  worrying about making darcs hard to install (tracking down deps of
>  deps).

This doesn't really work for the above reasons, unless we give up on
the idea of using optional packages.  Also, we might as well wait on
this until we come across a third party library that seems worth
using.

David