Smylers wrote:
Eric Wilhelm writes:
PERL_TEST_HARNESS_DUMP_TAP="$(test_dir_for_this_dist)"
If that isn't enough, I suppose you could do "if the env var is an
executable, run it and capture the output"?
Nice -- so that if you manage to trick somebody into setting that
environment variable y
That assumes that what is in svn is what is in the tarball.
In practice, the packaging system needs to do various things.
For example, copying in the LICENSE file, checking newlines are all
unix, adding ppport.h if needed, and so on.
Adam K
Nik Clayton wrote:
Adam Kennedy wrote:
Since I mov
Adam Kennedy wrote:
Since I moved to SVN, one of the things I've been doing is commiting my
release tarballs into a /releases/ directory.
One side-effect of this is that even before I've uploaded it to CPAN,
ever release already has a URI.
Eugh.
Have you considered using SVN::Notify::Snapsh
On 22 Jan 2007, at 13:14, David Landgren wrote:
Andy Armstrong wrote:
On 21 Jan 2007, at 13:28, Abe Timmerman wrote:
I see now that on OpenVMS you also use IPC::Open3, that in turn
uses fork(). fork() is not implemented on OpenVMS, so this will
not work.
Although I'm not a VMS expert, I do
David Landgren wrote:
Try perldoc vmsperl for more details.
*snort* Try perldoc perlvms for any details :)
Andy Armstrong wrote:
On 21 Jan 2007, at 13:28, Abe Timmerman wrote:
I see now that on OpenVMS you also use IPC::Open3, that in turn uses
fork(). fork() is not implemented on OpenVMS, so this will not work.
Although I'm not a VMS expert, I do have a testdrive account, and can
test some stuff
On 22 Jan 2007, at 06:24, Matisse Enzer wrote:
Here's an experimental script that uses Test::Harness::Straps and
XML::Generator to run perl test files and get the sort of XML
created by the ant task - I want to have CruiseControl run
my Perl tests and see the test results:
http://twoalp
Eric Wilhelm writes:
> PERL_TEST_HARNESS_DUMP_TAP="$(test_dir_for_this_dist)"
>
> If that isn't enough, I suppose you could do "if the env var is an
> executable, run it and capture the output"?
Nice -- so that if you manage to trick somebody into setting that
environment variable you can get
Ovid wrote in perl.qa :
> In trying to get runtests to run against the core Perl test suite on a
> freshly built download, I'm having a few difficulties. 'make test' says
> this:
>
> u=5.02 s=4.72 cu=297.54 cs=98.73 scripts=934 tests=117325
>
> This implies to me that we have 934 .t files i
