in reply to How to install self written modules

You can put both modules under 1 distribution by putting them under a lib directory.
> h2xs -AX ABC::Test > cd ABC/Test > mkdir lib > mkdir lib/ABC > mv Test.pm lib/ABC > cp lib/ABC/Test.pm lib/ABC/Test1.pm

--

Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)

Replies are listed 'Best First'.
Re^2: How to install self written modules
by jeanluca (Deacon) on Mar 04, 2006 at 12:05 UTC
    I like this approach, but what should you change inside the Makefile.PL:
    use 5.008007; use ExtUtils::MakeMaker; # See lib/ExtUtils/MakeMaker.pm for details of how to influence # the contents of the Makefile that is written. WriteMakefile( NAME => 'ABC::Test', VERSION_FROM => 'lib/ABC/Test.pm', # finds $VERSION PREREQ_PM => {}, # e.g., Module::Name => 1.1 ($] >= 5.005 ? ## Add these new keywords supported since 5.005 (ABSTRACT_FROM => 'lib/ABC/Test.pm', # retrieve abstract from m +odule AUTHOR => 'A. U. Thor <calje@knmi.nl>') : ()), );
    Howto include Test1.pm ?

    Luca

      There's no need to put anything about Test1.pm in the Makefile.PL, as MakeMaker globs the entire lib tree. You can use this to add other modules as dependencies to PREREQ_PM if you need any others packaged separately, or indeed CPAN modules.

      You probably want to take out the line use 5.008007; that h2xs put in, as you are not really dependent on this version of Perl.

      --

      Oh Lord, won’t you burn me a Knoppix CD ?
      My friends all rate Windows, I must disagree.
      Your powers of persuasion will set them all free,
      So oh Lord, won’t you burn me a Knoppix CD ?
      (Missquoting Janis Joplin)