in reply to Help with new quest to get a module posted to CPAN
It's looks so far good, except that I, as a matter of personal preference, wouldn't include a bare RCS Changelog. Furthermore, a LICENSE that merely states under which license you're publishing your work defeats its purpose - rather include it within the POD (License or Copyright section) of your main module.
And, you shouldn't be creating the compat Makefile.PL by hand, rather let Build.PL (à la Module::Build) create it for you (I suggest, create_makefile_pl => 'traditional', because it gives the user the freedom to choose between Module::Build or ExtUtils::MakeMaker (enforcing a peculiar installer is not recommended)).
Module::Starter is also a great choice for building the skeleton of a distribution.
Don't miss perlmodlib, perlmodstyle & perlnewmod.
For convenient uploading, I recommend cpan-upload.
The code looks promising (from a brief glance), so go ahead.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^2: Help with new quest to get a module posted to CPAN
by afresh1 (Hermit) on Jan 29, 2007 at 03:31 UTC | |
|
Re^2: Help with new quest to get a module posted to CPAN
by afresh1 (Hermit) on Jan 29, 2007 at 03:57 UTC | |
|
Re^2: Help with new quest to get a module posted to CPAN
by afresh1 (Hermit) on Jan 30, 2007 at 05:33 UTC |