I spent another day of prosaic adjustments to my CPAN distributions. For quite awhile the chaos of the Changes
files have bothered me, so I wanted to think about those. And, many of the files I scheduled for deletion disappeared from PAUSE today.
I’d like Changes
to have structured information that a program can turn into a data structure (and query, such as “What version fixed GitHub issue #137?”. We don’t quite have that, but there is the start of a specification in CPAN::Changes::Spec
and a test module, Test::CPAN::Changes
to check it. There’s even a Changes Kwalitee
at CPAN HQ. I’m not doing so well at the moment. Dave Rolsky has some thoughts on Changes files too
. Of course, Neil has already written about it in A convention for Changes files
, and Jonas covers many of the same things
file is a different story and I haven’t decided what I want to do about that. This file used to be the thing you would look at before you wasted your modem time download those large, 15k distributions. Then, they weren’t so useful. Now, however, GitHub displays their contents. I want to make mine prettier and to evaluate the information I put in them.
There’s a Test::CPAN::README
, but it checks for merely a name and version. I don’t particularly care about the version since I envision a file with stable information such as the summary of its use, the basics of finding the source, and how to contribute. I expect those to stay the same almost forever. Whatever I put in there, I want it to look good for GitHub. I might even consider using GitHub Pages
like I did for Perl Power Tools
. I had fun playing with that at Saint Perl 6