So today in the Dist-pen I am going to add in a few more plugins into my Dist::Zilla just to see how bad my Kwalitee is.
One of the things that has always caused me problems when creating a perl module distribution are the 'required' modules that sometimes may be unknowingly buried in the code or just forgotten when the distro was created. My Database::Accessor package has a large number of required mods so I will have to be careful when creating my Dirstro
Just of the top of my head I have some ten or eleven in the Data::Accessor class and then there are my test cases where there are some more. Now with Dist::Zilla I can add a simple plugin and get most of them automajickaly so I added in
DBD::mysql is the perl DBI driver for MySQL and the primary way Perl
applications and scripts access MySQL and MariaDB databases. The source
repository is at https://github.com/perl5-dbi/DBD-mysql.
A vulnerability was discovered that can lead to a buffer overflow, possibly
triggered by user supplied data. This vulnerability is present in all releases
at least back to versions 3.0 of the driver, which were released in 2005.
The CVE identifier for this vulnerability is CVE-2016-1246.
Users of DBD::mysql are advised to patch their installations as soon as
possible.
We have already made a pre-announcement for this security release at
the distros security mailing list. People using DBD::mysql installed from their
(linux) distributions can expect to receive an updated version soon.
Many thanks to Pali Rohár for discovering and fixing the vulnerability.
The DBD::mysql maintainers,
Patrick Galbraith
Michiel Beijen
You've been pulled into an impromptu meeting where the client now wants a web calendar tacked onto their application. Grimace. Walk out worried. But most important ...
Don't re-invent the wheel.
FullCalendar.js has most of what's required by default, is extensible and will take a json web feed. Given a list of hash refs, Mojolicious will spit out json. I'll show you a short template for displaying the calendar. Creating all your calendar appointments in json is left as an exercise for the reader.
Hacktoberfest is nearly upon us again. If you sign up and then do 4 pull requests in October, you'll get a free t-shirt. Sadly the list of Featured Projects doesn't include any Perl ones, but last year I created a list of featured Perl projects.
If you've got some issues you'd like to offer as fodder for the fest, all you need to do is add a Hacktoberfest label to the issues
Git::Database is yet another module I wrote to interact with Git. It wraps an OO-layer around Git objects (blobs, trees, commits, tags), in a way that's very similar to what Git::PurePerl does. It has no opinion on the actual means to get the data from the Git object database: that bit is done with the Perl Git wrapper of your choice.
At the moment, there's only one supported wrapper for fetching data from Git: my own Git::Repository. I already have branches with working code (i.e. passing all the relevant tests) for Git::Wrapper, Git::Sub, Git::PurePerl and even the venerable Git.pm, which I'll publish when they are more feature-complete. Git::Class is missing some critical feature I need to get the data from Git, and I couldn't figure out how to get the data using Git::Raw. Patches welcome!
The release is a version 0.001, as I expect the interface to have some rough edges that need some polishing. Depending on the feedback I receive, a version 1.000 should appear in a few months.
So the dilemma today is to decide what to call my next series I guess Dist-Pen would be an apt name and now to come up with some catchy titles and imags.
I spent a good little while looking at the fancy new (at least to me) distribution helpers out there and I have made a decision on which one I am going to use with accessor.
Well I have already abused 'ExtUtils::MakeMaker ' over the years so I will not lear much from playing with that one.
As for Module::Build I did play with that for a bit because it is Pure Perl and I have a Windows box but it did not play out the way I wanted. It will not get ne around the fact that I need an 'nmake' installed on my windows box. So I left this one in the dust.
When ramiroencinas added FileSystem::Capacity::VolumesInfo to Perl 6 ecosystem I've spotted that it has no macOS support. And while trying to contribute to this module I've discovered how less known Perl 6 features can save the day. What FileSystem::Capacity::VolumesInfo module does is parsing output from df command, which looks like this:
Well there comes a time in every playpen where it is time for bed so this will be the last moose-pen for a little while as I am all out of Moose to do on my Accessor project and I have to start getting it ready for CPAN.
So my love affair with Moose is ending, for the time being, and now I start working on the part of creating packages I dread the most 'Distribution'.
Up to this point in my career I have been lucky the only complex CPAN dist I ever worked with, DBD::Oracle, came with an extensive MakeFile.PL that I really only need to tweak every once an a while. At some 2800+ lines of code I was glad for that.
Update: OSCON have supplied us with a discount code for unlimited free Pavillon Plus passes to members of Perl related organisations and the broader community. Just use the code: FREEORG. Use this code when registering for the Pavillion Plus pass and it will zero out the balance. You can register at: http://conferences.oreilly.com/oscon/open-source-eu/public/content/pavilion-pass - thanks to OSCON and O'Reilly for providing this.
This year OSCON, Europe, will be held in London between the 17th-18th October (with a training day on the 19th), the Perl Foundation will once again have a table in the not-for-profit pavilion. As at previous events volunteers will be manning the Perl stand throughout the day on the Monday and Tuesday and they will also be available in the early evening.
Almost a year ago, I wrote CPAN tutorials. It isn't an original work, it's a derivative of RubyGems Guides, only "translated" to Perl world. I failed to publish it anywhere until now. I'll be happy if anyone finds it useful in any way which the license allows. And I'll be even happier if I get any feedback.
Carrying on from where I left off in yesterday's
post
I decided it was time I cleaned up a little more of my code. Seems I do this
use Moose;
with qw(Database::Accessor::Roles::Base
Database::Accessor::Roles::Comparators);
use MooseX::Aliases;
use MooseX::Constructor::AllErrors;
or code similar to it a almost a dozen times in the Accessor.pm file. Now there is nothing wrong with this but I think I can clean it up a bit by a just a little re-factoring or shifting things about (hence the link at the top).
In what is a somewhat mild case of yak-shaving, I need a portable
way of identifying file types in several situations. For example, when
indexing files for Dancer::SearchApp or when handling user uploads, I want to somewhat reliably identify various files.
I want to determine their type without trusting what the user tells me they are, and I also
want to send the appropriate Content-Type header when serving files again.
It is a pleasure to announce that this year the Perl5 Porters Hackathon (http://p5h.org/), held between the 11th to 14th November in Amsterdam, will be hosted by Booking.com and officially supported by The Perl Foundation.
The P5P Hackathon is a seeding event for the essential work done inside the Perl core. It functions as a symposium where current, and future, Perl5 hackers can meet and cross-pollinate ideas that may develop into significant future evolution.
This year the Hackathon has three major aims:
The sharing of knowledge. This will be facilitated by talks of up to twenty minutes to share information about any field with which the speaker is intimate.
To facilitate open discussion. Free participation in conversations regarding important topics you or someone else suggests.
Hacking the Code: Working on specific problems in order to reach tangible results.
The Hackathon will take place within two different locations in Amsterdam at Booking.com offices, both locations are within a short walk of each other.
