On Sat, Mar 13, 2010 at 23:28:02 +0000, Reinier Lamers wrote: > Sat Mar 13 23:14:28 CET 2010 Reinier Lamers <[email protected]> > * Add missing unit test modules to darcs.cabal > > Sat Mar 13 23:54:54 CET 2010 Reinier Lamers <[email protected]> > * Test release tarballs more thoroughly in release.sh > > Sat Mar 13 23:56:11 CET 2010 Reinier Lamers <[email protected]> > * Also add PatchInfo test module to darcs.cabal
I've pushed these. Nothing out of the ordinary there... Add missing unit test modules to darcs.cabal -------------------------------------------- > + -- list all unit test modules not exported by libdarcs; otherwise Cabal > won't > + -- include them in the tarball > + other-modules: Darcs.Test.Email > + Darcs.Test.Patch.Check > + Darcs.Test.Patch.QuickCheck > + Darcs.Test.Patch.Test > + Darcs.Test.Patch.Unit This sort of thing kinda frustrates me about Cabal... or rather, what really gets on my nerves is when I have non-exposed modules in my libraries, and then when building something which depends on my package, it gets a mysterious linker error... -- 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
