[pm-h] April Talk suggestion: perlall

[G. Wade Johnson]

On Mon, 20 Feb 2012 07:58:57 -0800 (PST)
Mark Allen <mrallen1 at yahoo.com> wrote:

> Speaking of projects... Wade, is there any update about the Cookbook
> refresh?

O'Reilly has been very quiet of late. Some of that should have settled
now that the new Programming Perl is out.

I've got to keep tagging my contacts there to see if it's a go.
Otherwise, I have an alternate plan that I'll announce if nothing else
works.

Stay tuned.
G. Wade

> Sounds like a neat tool, though!  Your own CPAN smoker on a single
> system.
> 
> Mark
> 
> 
> ________________________________
>  From: B. Estrade <estrabd at gmail.com>
> To: "Houston.pm located in Houston, TX." <houston at pm.org> 
> Sent: Monday, February 20, 2012 9:31 AM
> Subject: Re: [pm-h] April Talk suggestion: perlall
>  
> On Sun, Feb 19, 2012 at 07:13:03PM -0600, G. Wade Johnson wrote:
> > Thanks, Reini.
> > 
> > You're now on the schedule for April.
> 
> Sweet.
> 
> Helping Reini mature this tool would be a good project for Houston.pm.
> 
> Brett
> 
> > 
> > G. Wade
> > 
> > On Sun, 19 Feb 2012 18:12:36 -0600
> > Reini Urban <rurban at x-ray.at> wrote:
> > 
> >> I have several talk topics, but I think App::perlall is good for
> >> April.
> >> 
> >> Introducing App::perlall, a better perlbrew and testing tool
> >> 
> >> perlall does something like perlbrew, creating perl's for various
> >> versions and with various features
> >> just the sane way. I.e. if possible it uses the Configure defaults
> >> and does not need messing with
> >> PATH and PERL5LIB and allows having several parallel global perls
> >> at once.
> >> 
> >> With all these perls - and more perls created like this in vm's -
> >> it allows easy testing and
> >> maintenance of your perls.
> >> This way you don't rely on cpantesters to get back with reports on
> >> crazy versions,
> >> perl features or platforms, you test it by yourself before you
> >> upload it to CPAN.
> >> 
> >> .e.g
> >> cd Perl/MyModule
> >> perlall maketest
> >> 
> >> does
> >> for $p in /usr/local/bin/perl5*
> >>   do
> >>   make clean
> >>   $p Makefile.PL # or Build.PL
> >>   make
> >>   make test | tee log.test-$(basename $p)
> >> done
> >> 
> >> "perlall testvm" copies your perl module in cwd to all vm's and
> >> performs "perlall maketest" there and copies the log files back.
> >> "perlall do" runs commands for all your perls.
> >> 
> >> I describe my environment (kvm setup, building tricky perls esp.
> >> with windows, ...)
> >> and show several useful examples and utils, esp. with the logfiles,
> >> which are like your private copy of cpantesters reports.
> > 
> > 
> > -- 
> > There are two ways of constructing a software design: One way is to
> > make it so simple that there are obviously no deficiencies and the
> > other way is to make it so complicated that there are no obvious
> > deficiencies. -- C. A. R. Hoare
> > _______________________________________________
> > Houston mailing list
> > Houston at pm.org
> > http://mail.pm.org/mailman/listinfo/houston
> > Website: http://houston.pm.org/
> 


-- 
If it doesn't have to be right, I can make it arbitrarily fast.
                                                    -- Rick Hoselton