Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I use the following perlall-maketest and symlinked perlall-makeinstall simple script, and store its results in t/$version/ as simple test files for most of my modules.
    This is much better than relying on the cpantesters results.
    I do this in most of my vmware machines.
    d is for debug, -nt for non-threaded builds.


    $ cat ~/bin/perlall-maketest
    #!/bin/sh
    arch="cygwin"
    bad="5.00558 5.8.7 "
    export perlall="5.6.0 5.6.1 5.6.2 5.8.0 5.8.1 5.8.2 5.8.3 5.8.4 5.8.5 5.8.6 5.8.8 5.8.9 5.8.9d 5.9.5 5.10.0 5.10.0d 5.10.0-nt 5.10.0d-nt 5.11.0 5.11.0d 5.11.0-nt 5.11.0d-nt"
    base=$(basename $0)

    test -e Makefile.PL || exit 1
    for p in $perlall
    do
        log="log.test-$arch-$p"
        rm $log 2>/dev/null
        echo perl$p Makefile.PL
        perl$p Makefile.PL 2>&1 >$log && \
        ( make 2>&1 >>$log && \
            rm $log 2>/dev/null
            (make test 2>&1 | tee $log) && \
            if [ "$base" = "perlall-makeinstall" ]
            then
                    make install
            fi
            ( echo >> $log
                echo "----" >> $log
                echo >> $log
                perl$p -V >> log.test-$arch-$p) )
        make clean
    done