On Wed 22 Aug 2001 23:12, Paul Johnson <[EMAIL PROTECTED]> wrote:
> On Wed, Aug 22, 2001 at 12:42:38PM -0400, Michael G Schwern wrote:
> > The last smoke.tgz has syntax errors and other mistakes in it. This
> > patches.
> >
> > I think the "Configure" vs "./Configure" problem was mentioned before.
> > I don't have . in my PATH, and that's pretty common.
> >
> > And sitting here on Debian, it's /bin/sh, not /usr/bin/sh. I think
> > that's the more common setup.
>
> What's the recommended way to get this all running? The scripts can't
> be in the same directory as the source because of the rsync --delete.
Completely true. That's why /I/ do not have the --delete in the rsync at all,
but do the --delete in a --dry-run call and filter the deletes for files I
want to keep.
Just put the thre files /somewhere/ in your $PATH
> You could put them somewhere else, but then I think they need to be on
> the path, and I had problems with output files not being found. I ended
Why can't they be found? --delete only deletes once *before* smoke starts, and
reports are to be created *after* smoke ends (intermediate smoke results are -
og course - created *during* the smoke)
> up copying the scripts to the source dir after the rsync, but I'm sure
> that's not what others do.
That'll do too, but it would then be easier to extend your $PATH in smoke.sh
to the location where mktest.pl and mkovz.pl can be found.
> Is there a README somewhere, or a recommended directory structure and
Not yet. We're waiting for the Win32 env to fit in.
Dir structure: only one top level dir where the smoke will take place that has
enough disk space to complete
> way of doing things? I know other clueful porters have been put off
> because it doesn't "just work". I've got an alpha sitting here waiting
> - have I just missed something?
tuits? ;-)
Here's a revised situation.
Changes for 1.02
1. mkovz.pl accepts smoke folder as second argument, making only
smoke.sh candidate for editing
2. Michael's changes from Aug 22
3. smoke.sh expands PATH with starting location of smoke.sh
4. added README (just for starters)
5. added Makefile.PL (not ready for use (yet))
6. smoke.sh accepts source dir as argument
7. added ChangeLog
8. added MANIFEST
Open for comments ;)
--
H.Merijn Brand Amsterdam Perl Mongers (http://www.amsterdam.pm.org/)
using perl-5.6.1, 5.7.1 & 628 on HP-UX 10.20 & 11.00, AIX 4.2, AIX 4.3,
WinNT 4, Win2K pro & WinCE 2.11 often with Tk800.022 &/| DBD-Unify
ftp://ftp.funet.fi/pub/languages/perl/CPAN/authors/id/H/HM/HMBRAND/
smoke.tgz
