Re: How to make a module ready for public release?

You can use ModuleMaker or the like to create the templates in a different directory, so that you don't overwrite your code, then just place your existing stuff in the right places, and finish up the documentation, tests, etc.

Nothing says that they have to be run before you start writing your module.

Comment on Re: How to make a module ready for public release?

Replies are listed 'Best First'.
Re^2: How to make a module ready for public release? by Cody Pendant (Prior) on Aug 16, 2005 at 04:44 UTC
OK, but, don't they have to read my module, see which other modules it requires, etc., in order to create the correct Makefile.pl and so on? Or is all that done at installation time? As you can see I know very little about the make process. ($_='kkvvttuu bbooppuuiiffss qqffssmm iibbddllffss') =~y~b-v~a-z~s; print	[reply]
Re^3: How to make a module ready for public release? by davorg (Chancellor) on Aug 16, 2005 at 08:14 UTC
OK, but, don't they have to read my module, see which other modules it requires, etc., in order to create the correct Makefile.pl and so on? Or is all that done at installation time? No. You need to edit the created Makefile.PL (or, better, Build.PL) to add in the dependencies and stuff like that. My recommendation would be: Install Module::Starter Start a new module (in a different directory) with the same name as your module - that will give you all of the scaffolding required) Edit the files to add in your code and make any other required changes -- <http://dave.org.uk> "The first rule of Perl club is you do not talk about Perl club." -- Chip Salzenberg	[reply]