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
This is the C::Blocks Advent Calendar, in which I release a new treat each day about the C::Blocks library. At the time of writing, we are actually in the season of Christmas, not Advent. I hope you'll forgive these late posts. :-)
Yesterday I used C::Blocks to play around with Perl's C API and mess with keywords. Today I will focus on a couple of neat C tricks that can help clean up the C-end of your library API.
As part of the MetaCPAN hackathon, meta::hack, I was invited to work on the CPAN Testers integration. CPAN Testers is a community of CPAN users who send in test reports for CPAN modules as they are uploaded. MetaCPAN adds a summary of those test reports to every CPAN distribution to help you determine which module you'd most like to use. For quite a few months, this integration was broken, and the nature of the current integration (a SQLite database) means it is not as generally useful as it could be.
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.
This was not just a bad year for musicians. Unfortunately not. And the last three months were busy, with lot of (mostly bureaucratic) work. I was expecting the Christmas day to have some extra-time and do, at least one, a decent PR, but I got sick and the will to program just passed by.
So, this semester we had:
October, Perl-Critic-StricterSubs: my patch was to define the minimum required Perl version, as requested by CPANTS.
November, Net-SFTP-Foreign: following CPANTS suggestions, set the same module version for all distribution modules, and declare minimum required Perl version.
December, WWW-Pastebin-PastebinCom-API: generate META.json when building the dist.
I know, not proud of any of these PRs. I said to Neil I want to continue, but I really hope to start being more useful to module authors, or I will just quit...
Silver Gold Bull is your trusted silver and gold dealer. It provide you with competitive, up-to-minute pricing and make sure your precious metals are delivered to your door discreetly and fully insured.
SilverGoldBull::API provides with the following functionality:
- get all product/order list;
- get full information about product/order;
- or even create and sell your own product;
- and etc.
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
…
This is the C::Blocks Advent Calendar, in which I release a new treat each day about the C::Blocks library. Yesterday I compared C::Blocks to other TinyCC-based Perl libraries. Today I will focus on a fun diversion: hacking on the parser with a bit of C::Blocks code.
I must admit that some of yesterday's results have me a bit depressed. I've put a lot of work into this library, and I am really surprised and worried about the performance cliffs I illustrated yesterday. Today, though, we're going to have some fun.
Your early holiday gift from the Dancer Core Team has arrived - Dancer2 0.204002 is on its way to your favorite CPAN mirror. This release provides the following:
A fix for public_dir: When using public_dir , Dancer2 now waits for the configuration to be read before deciding where static content should be served from
A new plugin helper method, find_plugin(), that lets you import another plugin’s DSL for use in your own custom plugin
A variety of documentation fixes and enhancements
Make sure to check out the Dancer Advent Calendar! It features a number of great articles not only from the Dancer Core Team, but a number of our community members too.
The Dancer Core Team would like to thank all of our contributors and community members for another great year. Simply put, you are the reason we keep working hard at Dancer, and we are grateful to have such a great community of users and developers around us. Here’s to a great 2017… Hope you all have a safe and happy holiday season!
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
After almost 3 years of development and more than 2 years in production, 2 talks at YAPC::EU (Granada and Cluj) and one talk at the Dancer conference last year in Vienna, I think it's time to announce Amusewiki on blogs. perl.org as well, as I consider it more or less feature complete and robust enough for a larger audience.
Amusewiki is basically a CMS, but it's not "yet another one". Its main feature is that it creates for each published text various PDF (via LaTeX) and EPUB (for e-readers and mobile devices) files, along with an HTML version. It's also able to produce slides. Also the bookbuilder provides a way to extract, merge and customize the texts stored in the archive. You may want to give amusewiki a try if you're interested in publishing and distributing texts. If you just need a wiki or a blog for posting code snippets and lolcats, you probably want to look elsewhere. Amusewiki is suitable for publishing whole books as well.
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
This is the C::Blocks Advent Calendar, in which I release a new treat each day about the C::Blocks library. Yesterday I explained how to use C::Blocks in multithreaded Perl code. Today I will compare C::Blocks to other TinyCC-based Perl libraries.
After a couple of years of more or less "maintenance mode" on DBD::mysql - we had a hand full of people contributing occasional fixes and a whole slew of drive-by contributors - we now have a prolific contributor again: Pali Rohár.
It's great to see some more long-standing issues taken care of!
This time around, in the new development release 4.041_01 that is on CPAN now, there are some important fixes for some Unicode-related issues that I would like to point out. The sections below I have distilled based on the descriptions made by Pali.
Automatically converting to UTF-8 for bind parameters
Before this release perl scalars (statements or bind parameters) without UTF8 status flag were not encoded to UTF-8 even if mysql_enable_utf8 was enabled. This caused perl scalars with internal Latin1 encoding to be sent to the mysql server as Latin1 even if mysql_enable_utf8 was enabled.
This is the fourth article in a series about MetaCPAN. The first article described the two main parts that make up the MetaCPAN project: the API and the search interface. The second article gave a high level overview of how the API uses Elasticsearch to hold and search information about CPAN distributions and authors. The third article showed how MetaCPAN fits into the rest of the CPAN ecosystem.
In this article we'll show how you can use the MetaCPAN API to get information about releases to CPAN. We'll start off with a very simple query, then gradually refine it to narrow down which releases are returned, and what information you request for each release.
This article is brought to you by Elastic, who were a Gold sponsor for meta::hack. We were very happy to have their support, especially given the central role that Elasticsearch plays in MetaCPAN.
.svg?q=202)
