On 2/13/06, James Muir <[EMAIL PROTECTED]> wrote: > Hi, > Hi James. Hemlock? mmm, delicious :)
> I'm working on a module that I hope to place on CPAN in the near future. > I have an account, and a name space, and I've written tests and pod for > my module. My module name space is Gtk2::Ex::MindMapView, and I have > several modules in this name space. For example, > > Question 1) In my Makefile.PL do I specify all the modules or just the > main one (Gtk2::Ex::MindMapView)? How do I specify all the modules? If you mean, when you type make tardist you want certain files in the tarfile which is part of the CPAN distribution, then they should be in MANIFEST... just type make manifest to get all files under the distribution root added. also ExtUtils::ModuleMaker makes making CPAN modules easy and spiffy. > > Question 2) What is the best practice when it comes to creating build > scripts? Should I use Makefile.PL or Build.PL or both? Build.PL is up and coming. Makefile.PL has been old faithful for a long while. Build.PL is based around Module::Build is newer and presumably improved. All my CPAN modules use Makefile.PL and I have had no need for change. But if I were doing a lot of interactive configuration of my build process (like Alzabo does, for instance),then I would maybe go for Build.PL > > Question 3) Are test scripts for all modules required? No, not per se. >I have written 11 > test scripts to test 13 modules. Is this acceptable? Sure. You are aiming for code coverage. And that everything you document as doing something has a test to back it up. Cheers, Terrence (TBONE on CPAN), -- Play me in correspondence chess: http://slowchess.com/profile.php?username=tbrannon
