in reply to CPAN module versioning for slight changes

You can catch errors of the type you mention by doing 

$ make disttest

[download]
before you upload -- or 
$ ./Build disttest

[download]
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.

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.

Replies are listed 'Best First'.
Re^2: CPAN module versioning for slight changes
by choroba (Cardinal) on Jan 05, 2016 at 17:45 UTC
    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.
    We're working on it. Feel free to participate. 
    ($q=q:Sq=~/;[c](.)(.)/;chr(-||-|5+lengthSq)`"S|oS2"`map{chr |+ord
}map{substrSq`S_+|`|}3E|-|`7**2-3:)=~y+S|`+$1,++print+eval$q,q,a,

    [download]
[reply]
[d/l]
Re^2: CPAN module versioning for slight changes
by jdv (Sexton) on Jan 06, 2016 at 17:02 UTC
    Thanks, great tip. After my first MANIFEST mistake I've been basically doing this by hand, but I'll add a disttest before every commit now.
[reply]

In Section Seekers of Perl Wisdom