I am a subscriber to module-authors@perl.org and thought I'd repost something written there for the wider community.
Chris Bogart, a postdoc at Carnegie Mellon, is interested in studying how different language-level package managers and repositories handle breaking changes. He has observed that different package management systems have made "very different design choices from each other," and he would "like to know what the impact of [CPAN's] design choices are on how you negotiate breaking changes among CPAN module developers when the packages depend on each other."
If you have released modules on CPAN, and especially if you have thought about making breaking changes to your module, or have made breaking changes to your module, I'm sure you're ideas would be helpful. If you have had to deal with an upstream author's breaking changes, I'm sure that would be helpful, too.
http://breakingapis.org/survey
Hey everyone,
A bit late but... following is the p5p (Perl 5 Porters) mailing list summary for last week. Enjoy!
CPAN Day marks the day when the first distribution was recorded as being uploaded to CPAN. That was 16th August 1995, so we've been uploading modules for 21 years now!
On CPAN Day you could release something to CPAN, send a pull request on someone else's distribution, blog about Perl, or just head to the pub with fellow Perl hackers.
HI!
This time I want to tell you how to manage services and processes using sparrowdo.
Before this post a following list of topics was written by me:
As services are highly coupled with processes we will investigate them in one post.
Let's have an nginx web server gets installed on your system:
$ cat sparrowfile
use v6;
use Sparrowdo;
task_run %(
task => 'install nginx server',
plugin => 'package-generic',
parameters => %( list => 'nginx' )
);
We talked about package-generic plugin at this post.
We use this plugin to install system packages.
Ok. This is very logical now having installed an nginx to make it "bootable", so next reboot of our system
will pickup an nginx and make it sure it runs too. Some people call this autoload:
By Lee J
on
August 10, 2016 2:06 PM
Mojolicious::Plugin::OpenAPI is close to being stable so i figured it was time to migrate from our use of Mojolicious::Plugin::Swagger2. Here's the differences i found, with the observation that perhaps some of these were down to having an older version of Swagger2 (0.79, although Changes log suggests that might not be the case):
Geekuni provides Perl training for professionals
and joins us as bronze sponsor.
A lot of thanks for helping us turn the Perl Dancer Conference into a
truly amazing event!
Need your team to tune into the Dancer beat? Enrol them at Geekuni!
More sponsors are welcome, please see more details on our Homepage.
Long-time Perlista hfb reports from a sadly regressive DEFCON:
https://plus.google.com/+ElaineAshton/posts/Eh9vDGFhy7w
I like to keep my perl modules lean when it comes to dependencies. But then again, CPAN is just so wonderful with all the helpful packages available. So there are always dependencies.
When writing perl modules, more often than not a few dependencies creep in … which makes it a whee bit awkward when developing the module, because I then have to somehow install these dependencies, and I would rather not get them all over the place but neatly in the module directory so that I have at least a semblance of a stable development environment.
So here goes my solution: A little postamble method for my Makefile.PL.
Details on Medium
