Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Tue, 4 Mar 2003 11:08:38 +0000 (GMT Standard Time) From: Max Bowsher To: Ronald Landheer-Cieslak cc: cygwin AT cygwin DOT com Subject: Re: Testsuite as a package (was: Re: Was that the sound of a snapshot going off?) In-Reply-To: Message-ID: References: X-X-Sender: mob22 AT imap DOT hermes DOT cam DOT ac DOT uk MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/