On Thu 30 Oct 2003 13:22, Abe Timmerman <[EMAIL PROTECTED]> wrote: > Op een wisselvallige herfstdag (Thursday 30 October 2003 10:07), schreef > H.Merijn Brand: > > > I'd like to test the complete smoke suite with a single environment value > > set > > > > On cygwin, for example try to see the influence of changing $CYGWIN, or > > on *nix setting $UNIX95 and see if all still passes > > > > is there a guide to fit this in the conf, or do I just set it in the > > calling .sh or do I set it in my current shell and call the smoke by hand, > > Hmmm.. depends on how early in the process you want this.
*my* thought was to set it *after* perl build was completed, and *before* the tests start, in order to see if what a porter ports would work in a users (different) environment. > It was my perception that F<Policy.sh> was just for this sort of thing, but if That's if you want to influence the configure/build process > you feel that is too late in the process I suppose one could set this stuff Far too early > from the configsmoke-generated jcl. > > > or do you think it is a bad idea after all ... > > No, I guess people will try to build perl in their own environment, which > might pretty well be completely different from ours. But pumpkings might > think different. > > I believe that we need some sort of API to handle this from Test::Smoke *and* > make it report such information in a generic way. -- H.Merijn Brand Amsterdam Perl Mongers (http://amsterdam.pm.org/) using perl-5.6.1, 5.8.0, & 5.9.x, and 806 on HP-UX 10.20 & 11.00, 11i, AIX 4.3, SuSE 8.2, and Win2k. http://www.cmve.net/~merijn/ http://archives.develooper.com/[EMAIL PROTECTED]/ [EMAIL PROTECTED] send smoke reports to: [EMAIL PROTECTED], QA: http://qa.perl.org
