just to report there is an issue building Perl (v5.20.2) on Suse
# cat /etc/SuSE-release
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 3
It seems it is an issue open since 2011, how it is possible that Suse devs do not report it and fix it? They build Perl on Suse, right? Why they did not contribute back?
$ git config --global alias.stashed "stash list --pretty=format:'%gd: %Cred%h%Creset %Cgreen[%ar]%Creset %s'"
$ git stashed
stash@{0}: 2d7f38b [19 minutes ago] On variable-travel-times-207: variable station travel times
stash@{1}: 1e4207e [6 weeks ago] WIP on custom-mission-actions-30-2: a00a646 Don't show intelligence since we're not using it.
Typically, git stash just shows you the items in your stash. Now, git stashed shows you how long ago an items was stashed (I had no idea I had a 6 week old stash item) and colorizes the relevant bits to make it easy to read (admittedly not visible in the bit above).
I uploaded File::Finder to the CPAN more than a decade ago. I was using it for a project today, and found a bug that has been in there in the beginning. I forgot to localize $_ in ->contains, which clobbered File::Find's $_, used by just about everything else.
I couldn't even remember where I had put the git repo for the distro source, and once I found that, I couldn't remember how to build and test modules.
I just released 0.30_1 of Net::Amazon::EC2 to CPAN. This test release contains support for AWS4 signatures. It is based on a pseudonymous patch on this RT ticket but I reworked it to support both v2 and v4 signatures because I know some of the people who use this module connect with Eucalyptus or other AWS-compatible-ish APIs which may not fully support v4 yet.
So if you've been itching to get stuff done with EC2 in the eu-central-1 region (which AFAIK only accepts v4 requests), please give this test release a spin. I plan to release it as 0.31 after a couple of weeks if no show stopper(s) pop up.
Ever seince I started using a Chromebook I have been interested in the concept of cloud-based IDEs for development. I am disappointed with Codenvy.com's lack of Perl support in their runtime containers and IDE, but it's technically possible to develop Perl apps on their platform.
I recently heard about Koding.com. I signed up and was delighted to discover native Perl support in both their default runtime container and IDE; with support for syntax highlighting and code completion. I cloned an existing Git repository, and I felt almost like I was working in a normal linux environment (albeit, in the cloud from a web browser).
If you're familiar with Dancer2 (my favorite Perl web framework to date), you know how amazingly easy it is to develop self-describing routes for your web application.
Let's say you have a Dancer2 app that allows your users to manage their phone numbers in a 1:X relationship. You might want to expose a route like...
post '/user/:user_id/phone_numbers/new' => sub {
my $user_id = param 'user_id';
# Do some stuff
};
... to add a new number to their profile. Let's also assume you have a route upstream that prohibits users from accessing routes associated with other users:
I attended Perl MiniConf last saturday and learned a great deal. I have had a pause account since the NYC Perl Hackathon 2015 event ( May 2nd 2015 ) and because of this I decided to take brian d foy's "Become a CPAN author in 3 hours" training. It was a very smooth and eye opening experience ( I was expecting a CPAN Module upload to be a bit more complicated).
Here's a list of things I took from brian's training:
I recently attended Miniconf in New York at which I decided to host a hackathon for my current hobby project, Mojo::Snoo - a Mojo wrapper for the reddit API.
Some hackathon attendees were nice enough to contribute code and give me some great ideas for future development. So, I’d like to briefly mention some changes introduced in the v0.10 release.
Firstly, let’s get one thing out of the way:
What the #$%! is Snoo?
Snoo is the name of reddit’s alien mascot. You know, the white alien at the top of reddit.com:
Not to be confused with “snu-snu” from Futurama.
According to reddit’s most recent license changes, reddit API wrappers cannot contain the word “reddit”.
Thus, Mojo::Snoo was born.
New features and changes
Moving on - I’d like to summarize some changes made recently and share some quick examples:
The web conference software that the Perl community uses mostly (Act) has a nice feature that lets registered users to mark their favourite talks. You just have to choose a talk from the list and then add it to your favourites.
This feature has several benefits that may seem obvious but are important anyway:
The after-story about the Perl Golf contest, which took place during the two-day
YAPC::Russia conferece in Moscow
Perl Golf is a contest, where participants solve the task with the shortest Perl
programme possible. This year's Golf rules were announced by Vadim Pushtaev
right after the conference start.
You can find a formal desciption and all the received solutions in the
YAPC_Russia_2015_perl_golf GitHub repository.
So I just went to investigate switching from perlbrew to plenv.
This has failed before, because I run an old and grungy installation of Perl where I didn’t set up a local lib and just installed whatever without keeping records of which installed modules I need and which are just junk I tried for a few minutes. Unless I carry forward all that junk, I can’t switch perls without breaking all my local scripts – and I have better things to do.
Eventually I want to fix this situation, but no today on which it comes up has been the day for it so far.
Still, I do want to upgrade to 5.22 now that it’s out, and I’ve been wanting to switch to plenv for a while. What to do?
Uhm… *looks around* ln -s ~/perl5/perlbrew/perls/perl-5.16.1 .plenv/versions/5.16.1
La la la… *walks away*
Yup, plenv global 5.16.1 is fine with that and a plenv rehash later, it works.
I threw out the rest of perlbrew, just kept the directory tree for the linked perl installation, and now I happily run this bastard/cuckoo setup. Teehee.
Now for installing 5.22 and making all my stuff work with it…
Here’s a little trick I’ve been using for a while to help ensure that a large
sprawling Catalyst application always generates valid HTML. The idea is to
unit test all your templates: the trick is to make it really easy with
a helper class:
Long time no blog. I posted on reddit about my new module, Mojo::Snoo. I'm shooting for a funky Perl wrapper around the reddit API. Right now, I'm the only one using it (I think), but would like that to change.
So...feedback welcome! Install, break, complain, etc.
Oh, and I will be hosting a hackathon at Miniconf this weekend in NYC. So, feel free to say hi and help me with some development.
Yesterday I had this idea of creating a site where people and companies could offer bounties for fixing specific bugs in a piece of open source code. Then I ran a search and found
Bountysource
.
I wonder, have you or the company where you work ever used it? Would your company be ready to offer bounties for fixing specific issues in a CPAN module or even in core perl? (bugs or new features alike.)
Would such bounties be a better way for TPF to spend their grant-money?
I thought I would share a little trick I use to get these three complex and
idiosyncratic frameworks to play nice with each other.
Catalyst and HTML::FormFu are a powerful combination that allows you to tie
the form displayed by your view to the form processed by your controller.
This direct link means: 1) your field names in your generated HTML will always
match the field names used in form processing, 2) default and redisplay field
values set by your controller will always match up with the values displayed
by the view, and 3) any constraint or validation issues detected by the form
processing logic in your controller can be directly associated with the
fields displayed by your view. Without this link, keeping a form defined in
our view in sync with the form defined by our controller is a large source
of potential bugs.
In this presentation that I gave at MadMongers last month, I show you how to use AngularJS as a front-end to your Perl backends. Presentation files available as well.
