On Mon, Aug 28, 2006 at 05:56:52PM -0400, David Fang wrote:
> > There are also several different standards for even what command runs
> > the tests. I guess 'make check' is the autotools standard, but lots of
> > auto*-using packagers don't know that and have custom-written 'make
> > test'. And the perl world long ago standardized on 'make test' (and we
> > have a specific NoPerlTests flag to control that). Plus who knows what
> > other custom variants there are...have to cd somewhere first?
> >
> > Given the variety of commands needed to run tests and the different
> > ways those results might need to be interpretted and the desire to be
> > able to have this togglalble at the level of fink itself, it sounds
> > like we're headed for a TestScript or MaintainerScript field.
> 
> Don't forget the fact that test-suites can add more dependencies, e.g.
> gcc requiring dejagnu and expect.  A TestDepends/MaintainerDepends field
> might be useful.

I haven't heard people wanting to do the testing except "immediately
after the build", and I don't think it even *could* be done without
the build dir. Therefore, BuildDepends seems sufficient to me.

dan

-- 
Daniel Macks
[EMAIL PROTECTED]
http://www.netspace.org/~dmacks


-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Fink-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Reply via email to