Re: MakeMaker, h2xs, and writing CPAN modules

Hi,

if I write some code consisting of several modules which are of no use for CPAN (or don't need it for several scripts), I like to keep them with the scripts in a directory structure like, e.g.

myscript/bin ..... scripts
myscript/lib ..... modules
myscript/lib/build . for building modules with h2xs
myscript/source .. sourcefiles
myscript/log ..... for logfiles
myscript/doc ..... documentation
myscript/work .... working dir(s)
myscript/result .. output dir
....
[download]

or the like.

If I do it this way, I prefer loading modules the following way:

BEGIN {
  use FindBin ();
  use lib "$FindBin::Bin/../lib";
  require ModulXY;
} # BEGIN
[download]

Btw: I could use "use" instead of require, but since I hardly ever do namespace pollution, I somehow quite satisfied with require.

For building modules, I use h2xs if there's just a slight change that I could share it on CPAN, and keep several build directories and keep links (under Unix/Linux) from ./lib to the modules untill they are finished.

So far, my 2 cent...

Best regards,
perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8.8.8.32.11.32"

Comment on Re: MakeMaker, h2xs, and writing CPAN modules Select or Download Code


No such thing as a small change
	PerlMonks