Dist::Zilla Moose Weaver

So it is Moose day here in the Dist-Pen

So I am finally back to Moose after many many days with Dist::Zilla and Pod::Weaver as to today I am going to see how I can use the Moose::MOP, Dist:Zill and Pod::Weaver all together.

What I am look at today is the [Consumes] section plug-in which is suppose to run out read the meta-classes of my Moose objects and then print out all the Roles that a class consumes. I am not sure what results I will get but is should be fun to see.

So all I need to do is add this in my 'weaver.ini'

[Generic / OVERVIEW]
++[Consumes]
[Collect / ATTRIBUTES]
and after I install it with cpan and do the old clean and build with dzil I get

=head1 CONSUMES
=over 4
=item * L<Database::Accessor::Types>
=back
in my Accessor.pm which is perfectly correct as in that file I have

 use Moose;
    with qw(Database::Accessor::Types);

Dist::Zilla In C

It is C round up day today in the Dist-Pen.

In my last post I had a look at [Contributors] section plug-in and today I am going to look at not one but three plug-ins

  • CommentString
  • CollectWithAutoDoc and
  • CollectWithIntro

CommentString
This simple plug-in lets you do your own 'Comment' sections like we have seen with [Name] and [Contributors]. It works in much the same way as the [Collect] plug-in, you supply the 'name' for the section and then a 'key' to match on.

For example if I want to have a section for 'Notes' for any comments I may make I could do that by adding this into my 'Weaver.ini' file

[Region  / postlude]
++[CommentString / Notes]
++comment = Note
[Authors]
and then in my POD files I could add a comment like this

# Note: Bob's Bargain Basement of Floppies it the best place to get these
=pod=cut 
anywhere outside the POD comment and after the usual insall of the plug-in and the dzil clean and build I get

Smoking Perl

Sawyer X's March 5-25 2018 Perl 5 Porters Mailing list summary put out a call for macOS smoke testers. I thought I would see how far I could get putting one together from the Test-Smoke docs.

The following is not a blow-by-blow (painful and uninteresting to read), but rather what I came up with after a few false starts, with emphasis on what I did over and above the Test-Smoke README documentation, and (sometimes) why.

Environment:

  • macOS 10.13 High Sierra
  • Custom-built Perl installed system-wide in custom directory
  • CPAN client (not cpanp or cpanm) configured to sudo

Procedure:

Perl 5 Porters Mailing List Summary: March 26th - April 2nd

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past week.

Enjoy!

YAML::PP Grant Report March 2018

Hello readers,

I hope you had a nice easter weekend.

I had another busy month and worked about 25 hours on YAML.

Dist::Zilla Gives Back

Still stuck in Section mode here at the Dist-Pen

Carrying from my last post today I am going to look at the [Contributors] section plug-in. This particular plug-in is of little value so for to my 'Database::Accessor' project as I have no other people working on it with me but one can always dream big that I may have some helpers as time goes on. So it is is work a look.

I wanted to see if anyone else is using this plug-in so I did a Reverse Dependency look up and found that there are thirty-six other distributions that use this so I have few places where I can go an peek and see how it is being used.

Dist::Zilla Hates PEEPS

It boy scout day here in the Dist-Pen.

In may last post I had final look the various [Bug] section plug-ins so today I am going to look at Merit-badges. I am really talking about that great feeling you had when you earned your first badge in Cubs, Brownies or Young Pioneers. You know the ones I mean the ones for learning to build a fire, sew on a badges, help an old man across the street or showing true will in conforming with the collective.

You can get the same feeling all over again in the programming world as well. All joking aside the [Badge] section plug-in is a quick way to get visual display information to potential users of your software such as this;

perl510.png

So at a glace you know it is passing its testing and you need at least perl 5.10 to use it.

Dist::Zilla Still Stuck on Bugs

It is the big bug round up day here at the Dist-Pen

In my last post I had a look at the [Bugs] section plug-in for Pod::Weaver, following along that line I am going to look at a three similar ones;

All are just a variation on the [Bugs] plug-in and none of them have the 'header' attribute. I will give you the .25$ trour;

BugsAndLimitations

This plugin requires that you enter the 'bugtracker' key-value pairs under the 'resources' meta key and you can do that by either using the [Bugtracker] or the [MetaResources] to set these values up for you. With my present 'dist.ini' it will produce the following output

=head1 BUGS AND LIMITATIONS

You can make new bug reports, and view existing ones, through the
web interface at L<https://github.com/byterock/database-accessor/issues> 
…
as you can see it does not care about the email address.


BugsRT

I attended Gotanda.pm

Yesterday, I attended Gotanda.pm, which is a Japanese local pm group organized by karupanerura.

A lot of interesting talks were presented there. I especially enjoyed codehex's talk, where he introduced how to write closures in XS. You can read his blog post for the more detailed explanation.

And I gave my talk about writing perl with w0rp/ale, which is an Asynchronous Lint Engine for vim8. There is already a blog post about it by oalders, so you may notice it.

If you write Perl with vim, why don't you try ale together with my simple syntax checker skaji/syntax-check-perl?

Dist::Zilla Report Bugs

Knocking off another Section here at the Dist-Pen today.

The last few posts I was dealing with the trials and tribulation of the [Availability] section plug-in, today I am going to look at another section plug-in [Bugs].

As the name implies add a 'Bug' blurb to your POD. Like the plug-in from my last posts this one is closely entwined with Dist::Zilla and we are luck this time as the POD for this one is quite extensive and does a good job on explaining how to use it. Hopefully, I will not find another bug.

The gem I found in the POD was you can use this Dist::Zilla plug-in [MetaResources] to add name key-value pairs into the 'repository' key of the meta data. At the present time I have all that the key-values I think I need because I use the [GithubMeta] plug-in to gather that data.

Dist::Zilla Flash Bugs

So it is Dist and a little Pod day here in the Dist-Pen.

In my last post I as have a look at the [Availability] section plug-in and ran at a problem when I was trying to get the content for the 'development' info that was promised by the Plug-in.

There where a few issues with my approach. First what I wanted to see was the link up to my github site. I though that this would do it to the 'dist.ini' file;

...
[Bugtracker]
web = https://github.com/byterock/%l/issues
mailto = test@test.com
…

Dist::Zilla Ready and Available

Sorry to say more Pod today in the Dist-Pen.

In my last post I wrapped up the final section [Legal] found in the [@Default] template for Pod::Weaver. Since I am on such a roll I will go on and look at a number of other 'Sections' that available on CPAN.

The first one I am going to look at is [Availability]. This will add an section to you POD that will contain an Availability blurb depending on what you have configured in your 'dist.ini' file.

This plug-in cannot be used stand alone you will have to use both the 'Dist::Zilla::Plugin::Bugtracker' and the 'Dist::Zilla::Plugin::Homepage plug-in in your 'dist.ini' file. Now I have yet to play with these two plug-ins so I will install and then add them to my '.ini' file

Dist::Zilla Consults the Law

I can see the end soon for POD here in the Dist-Pen but not quite yet.

In my last post I had a real quick look at the [Authors] section plug-in and how the trick to using it is to know that the list of authors comes from your 'dist.ini' file. Today I am going to look [Legal] the last of the sections found in the [@Default] template.

As you can guess this is where Pod::Weaver dumps the legal stuff we all love to add to your PODs. Like the [Authors] plug-in this one gets its info from the 'dist.ini' file. In my file I have

...
author = John Scoles 
license = GPL_3
copyright_holder = John Scoles
…
and that is why I get

=head1 COPYRIGHT AND LICENSE

This software is Copyright (c) 2018 by John Scoles.

This is free software, licensed under:

The GNU General Public License, Version 3, June 2007

Programming the Raspberry Pi with Perl; eBook fundraiser

A few weeks back, it was pointed out to me that Timm Murray was proposing to write an eBook for using Perl on the Raspberry Pi. Due to my extensive work on that platform over the last two-plus years, I had keen interest in the project.

Timm will be writing the bulk of the content using various distributions including my RPi::WiringPi along with all its related distributions, and I will be adding at least one chapter to cover my indoor grow room single-webpage environment controller, as well as performing editing duties and testing of the code.

We've been working together for a couple of weeks now, and today, I'm proud to announce the official launching of the fundraiser for the new book.

Whether you're interested in working on the Raspberry Pi, or just want to donate to a good cause for other Perl hackers, please have a look.

Thanks!

Dist::Zilla Lists Authors

Still plunking away in the POD world today in the Dist-Pen.

In my last post I had a look a the very simple [Leftovers] section plug-in and how it dumps all unaccounted for POD in the that place on your template. Today I am going to look at another simple one from the [@default] template [Authors]

Looking at the POD for the first time is plug-in one would be quite lost at how to use it. I guess the original POD writer though that is was so simple to use it need no explanation. The trick here is this particular plug-in gets all its info from the 'dist.ini' file. In that file there will be a least one 'author' line as in mine;

name = Database-Accessor
author = John Scoles
license = GPL_3
…
To add in more 'authors' simply add in more of the same line like so

author = John Scoles
++author =  Bill Bloggings 
license = GPL_3
…
and after a quick clean and build with 'dzil' I get

Perl 5 Porters Mailing List Summary: March 5th-25th

Hey everyone,

Following is the p5p (Perl 5 Porters) mailing list summary for the past three weeks.

Enjoy!

The Perl Conference Newsletter: 3/25/18

In This Issue:

Keynote Speaker:  VM (Vicky) Brasseur

VM (aka Vicky) spent most of her 20 years in the tech industry leading software development departments and teams, and providing technical management and leadership consulting for small and medium businesses. Now she leverages nearly 30 years of free and open source software experience and a strong business background to advise companies about free/open source, technology, community, business, and the intersections between them.

 

She is the author of Forge Your Future with Open Source, the first book to detail how to contribute to free and open source software projects. Think of it as the missing manual of open source contributions and community participation. The book is published by The Pragmatic Programmers and is now available in an early release beta version. It's available at https://fossforge.com.

 

Dist::Zilla Hates Leftovers

Well POD post-ette day again here in the Dist-Pen

In my last post I had a look at the [Collect] section plug-in and how you can use it to gather up similar parts of your POD in to one section in a document. Useful when you want to keep the POD next to the code but you have a mix of function attributes and subs in the code for other valid reasons.

Today I am looking aI would guess would be the simplest plug-in to use [Leftovers]. As the name implies it dump any Pod that has not been put into another section.

In the case of the [@Default] template it is here;

...
[Leftovers]
[Region  / postlude]
[Authors]
[Legal]
Now in my present POD I only have one left over bit

=head1 Datatbase::Accessor is not an ORM
and with the above default you see it show ups just before the [Authors] section

 Check out older version at ...

=head1 Datatbase::Accessor is not an ORM

London Perl Monger - Tech Meet #1

Last Thursday, I attended the London Perl Mongers Tech Meet at the Zoopla. This was my second time attending tech meet. I must say this was better than the previous meet, in many ways. First there were more people this time than compare to the last one, I attended. Second, this time talk was more Perl-ish. And last but not the least, plenty of food and drinks, thanks to all the sponsors.

Dist::Zilla Collects

Its collection day here at the Dist-Pen.

In my last post I looked at the rather plain but useful [Generic] section plug-in, that lets the Pod writer control where any section of POD that begins with =head1 can be moved to anywhere on the page. Today I am going to look at another of the often used plug-in the [Collect] section or plug-in.

This section is used to gather, group collect or otherwise gather together items under a named '=head1' tag what have the same POD tag. Looking at the [@Default] template again you will see there are three of them;

[Collect / ATTRIBUTES]
command = attr
[Collect / METHODS]
command = method
[Collect / FUNCTIONS]
command = func

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is hosted by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.