This is the mail archive of the
mailing list for the Cygwin project.
Re: Testsuite as a package (was: Re: Was that the sound of a snapshotgoing off?)
- From: Max Bowsher <maxb at ukf dot net>
- To: Ronald Landheer-Cieslak <ronald at landheer dot com>
- Cc: cygwin at cygwin dot com
- Date: Tue, 4 Mar 2003 11:08:38 +0000 (GMT Standard Time)
- Subject: Re: Testsuite as a package (was: Re: Was that the sound of a snapshotgoing off?)
- References: <Pine.LNX.firstname.lastname@example.org>
On Tue, 4 Mar 2003, Ronald Landheer-Cieslak wrote:
> There is no *need* for a separate package - but it would make life easier
> for those who want to help regression testing.
And it would be extra work for Chris. I don't think performing a CVS
checkout is that hard.
> I never said it was a necessity - or even implied it. I said "wouldn't it
> be great if" (or WIBGI for short). I think it would be a good idea to have
> a separate testsuite that I can just install & run whenever a new snapshot
> gets launched. I think it will be of help to signal regressions and I want
> to be of help if I can. I *know* not having a license disclaimer does not
> deprive me of CVS access - I also know that I don't want to have to
> compile Cygwin every time I want to run the test suite - and the test
> suite as is just happens to depend on new-cygwin1.dll (to test a
> just-compiled Cygwin DLL).
Why *don't* you want to compile Cygwin when you run the testsuite?
"../src/configure && make", wait a while, all done.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html