On Tue, Nov 25, 2008 at 10:31:32 -0800, Jason Dagit wrote: > > I've done it just using the same cabal file. Advantages > > - simpler > > - no duplication of information
I would add "fewer hoops for the user to jump through" here > > Disadvantages > > - installs darcs for anybody who just wants to have libdarcs Some users might find this one to be a pretty strong disadvantage > I glanced at what you did, but I may not be following it accurately. My > intuition about cabal is that we should be able to specify the bulk of the > darcs source as 'libdarcs' and tell the executable stanza of 'darcs' to use > that. Doing this will hopefully stop the double builds. It looks like that > is more or less what you did, except that I would have expected the > c-sources to need to be part of libdarcs so users of libdarcs may get link > errors unless they link those in. Thanks for the hint! Unless I'm mistaken, we can't avoid the double builds without using a separate cabal file, at least, not until the Cabal team manage to solve http://hackage.haskell.org/trac/hackage/ticket/89 -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
