On Tue, Nov 25, 2008 at 2:32 AM, Eric Kow <[EMAIL PROTECTED]> wrote: > This bundle is meant to generate discussion more than anything else > (I would rather somebody more knowledgeable about Cabal did this for > us).
Thank you Eric! > > > This exposes every darcs module as part of a new library (again, > one whose API is explicitly volatile and unsafe). > > I've done it just using the same cabal file. Advantages > - simpler > - no duplication of information > Disadvantages > - builds darcs twice :-( > - darcs executable has to adhere to package version policy > (which may not be so bad) > - installs darcs for anybody who just wants to have libdarcs 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. > > An alternative is to rename our darcs.cabal to libdarcs.cabal and create a > minimal release/darcs.cabal which depends on libdarcs. I suspect this is the "wrong thing" to do but this is mostly just a guess. Thanks, Jason
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
