On 10 February 2005 07:39, Isaac Jones wrote:
> I have a little collection of programs that use cabal which I use in
> my testing script. It includes:
>
> - a package whose executable depends on the library (not with the
> depend: flag)
>
> - a package with user hooks
>
> - a package where two modules are named Main
>
> - wash2hs
>
> - hunit
>
> - and a handful of random things tested by one packaged called "A"
>
> These should probably go in the examples directory or somehow be
> included in CVS. What's the best way to do this? The Setup files
> should probably be built at least as a sanity check when building
> cabal.
Check them in under libraries/Cabal/tests or examples. I'd put tests in
'make check' or 'make test' rather than the main build, though.
We have a few cabal tests in testsuite/tests/ghc-regress/cabal - I'll
pull any tests you put in libraries/Cabal over into the testsuite so
they get run every night with the GHC builds.
Cheers,
Simon
_______________________________________________
Cvs-libraries mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/cvs-libraries
