You can catch errors of the type you mention by doing
before you upload -- or$ make disttest
as the case may be. This makes your tarball if needed, and then unpacks it again into a subdirectory and runs your tests. I do this routinely before releasing, and occasionally catch MANIFEST omissions.$ ./Build disttest
Editorial comments: Perl's testing culture is one of the things that makes me enthusiastic about the language. Any other language could do this, but no other that I know of does so. All hail CPAN testers.
What we do not have (I think -- I would love to be shown that I am in error) is a complete how-to on publishing a module. There are pieces/parts various places: the CPAN FAQ has the basics, the Perl foundation has recommended licensing, PAUSE has something on naming modules, CPANTS (not to be confused with CPAN Testers) recommends and tests for ways to structure modules, but nothing I know of ties it all together in a place where the budding module author is bound to find it.
In reply to Re: CPAN module versioning for slight changes
by Anonymous Monk
in thread CPAN module versioning for slight changes
by jdv
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |