Jonathan Yu wrote:
On Sun, Aug 2, 2009 at 9:49 AM, Shawn H. Corey<[email protected]> wrote:
Here is a copy of my MANIFEST. Is there anything missing?
Build.PL
Changes
MANIFEST
README
lib/Sub/Starter.pm
script/substarter
t/00-load.t
t/01-parse_usage.t
t/02-usage.t
t/03-sub.t
t/04-pod.t
t/pod-coverage.t
t/pod.t
Why is there both a 04-pod.t and a t/pod.t? Are they the same test?
No. t/00-load.t t/pod-coverage.t and t/pod.t all came from
module-starter aka Module::Starter
I shall rename my tests so that they are more descriptive.
Also, you may want to model those tests after what Alias does with his
distributions (RELEASE_TESTING and AUTOMATED_TESTING) unless you have
already done so. Module::Install is said to have a feature implemented
(at some point in the future) which will help write author tests like
pod-coverage, the Test::MinimumVersion test (to detect the minimum
perl version required to run your code), etc.
You may also wish to supply a Makefile.PL (via Module::Build::Compat)
to support older perls/CPAN.pm's. There is also a list of criteria on
CPANTS (http://cpants.perl.org)
I would definitely suggest replicating Alias' test code, see:
http://cpansearch.perl.org/src/ADAMK/ORDB-CPANMeta-0.10/t/
In particular, the 9*.t series of tests are important/useful.
Sorry, I don't use un-documented code. Here's why:
On https://pause.perl.org/pause/authenquery?ACTION=pause_04about it states:
"There's only one thing you need to know as soon as possible:
Please, make sure the filename you choose contains a version number."
OK, does that mean every file needs a version number or just the tarball?
--
Just my 0.00000002 million dollars worth,
Shawn
Programming is as much about organization and communication
as it is about coding.
My favourite four-letter word is "Done!"
