develooper Front page | perl.perl5.porters | Postings from March 2014

Re: Wanted: program that makes working on "Bleadperl breaks" bugs easy

Thread Previous | Thread Next
From:
David Golden
Date:
March 6, 2014 14:58
Subject:
Re: Wanted: program that makes working on "Bleadperl breaks" bugs easy
Message ID:
CAOeq1c_1fsTxkYHKiCc6iwx5mAcGL-ODdAGZbJ3XfRcvnKxjJg@mail.gmail.com
On Sat, Dec 21, 2013 at 3:54 PM, James E Keenan <jkeen@verizon.net> wrote:
> I emphasize that I want a *turnkey* solution to this
> problem.  In the hackathon context I described above, I
> don't want to have to say to the hacker, "Learn about
> perlbrew, cpanm, etc. *before* you walk in the door."

That's a fair point, but at the same time, you have so assume they
have some skills and ability to figure things out for *their*
environment.  Even things like perlbrew mean mucking with PATH and the
like and hiding that from them is potentially going to be more
confusing.  E.g. using cpan and "look" to open a shell needs to ensure
the right PATH is set up there, too.

> Under the hood, such a turnkey solution may well use tools
> like perlbrew and cpanm.

I think if you're not letting them learn about such tools, you're
doing them a disservice.  They come out of the hackathon not knowing
much more than what they did going in.

My recommendation would be a cookbook, possibly backed up by a
screencast →  "Watch this 5 minute video. It will show you what to
do."

> Now, I suspect that some p5p-ers have already invested a lot
> of time over the years to get something which is 90%+ of
> this turnkey solution already.

My thoughts on a cookbook:

Assume linux/unix/bash and use of perlbrew.  Use cpan not cpanm
because it's one less thing to install and you get to see the test
output as it goes instead of needing to go look at the log afterwards.
 (Which is what *I* do with a handy bash alias, but not what I'd tell
a newbie to do)

* curl -L http://install.perlbrew.pl | bash
* remind them to actually set up perlbrew in .bashrc or whatever
* perlbrew install -j 9 -D man1dir=none -D man3dir=none perl-blead
* perlbrew use perl-blead
* cpan -t Bad::Module  (maybe with | tee bad-module.log)
* use cpan and "look" to dig in more if needed

Perlbrew offers installing "perl-blead" which is a snapshot, but
snapshots can be broken as Jenkins tells us, so I wouldn't necessarily
recommend only that.  They might need to fall back to the last blead
release.  Hopefully with the freeze it won't.

For more advanced digging, I would recommend a git checkout and a tool
like App::grindperl probably with the --install option.

David

-- 
David Golden <xdg@xdg.me> Twitter/IRC: @xdg

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About