Of course, `make manifest` *assumes* a bunch of not be accurate.. I
:have modules with test files that I don't want in the distribution,
:since hey only run in my machine, for instance.
:
This is what I do folks in regards to MANIFEST file. First off, I don't keep it
in CVS
repository. But I do keep MANIFEST.skip file in CVS. This file keeps rules
governing
MANIFESTation process.
Whenever I want to distribute the work to CPAN I
* tag the current sandbox:
$ cvs tag rel-4_00_01-cpan
* release the sandbox:
$ cvs release CGI-Session
* export it:
$ cvs export -r rel-4_00_01-cpan CGI-Session
* prepare the distribution:
$ perl Makefile.PL
$ make manifest
$ make metafile
$ make dist
$ cpan-upload CGI-Session-4.00_01.tar.gz
If you release too frequently to CPAN that typing above over and over again is
painful,
then you can edit Makefile.PL to introduce new targets to the generated
"Makefile" then do (for instance):
$ make prepare_distro
Voila. Consult ExtUtils::MakeMaker for details
--
Sherzod B. Ruzmetov <[EMAIL PROTECTED]>
<URL: http://author.handalak.com >
