in reply to Re: how could use inc::Module::Install ever work? and other M::I questions
in thread how could use inc::Module::Install ever work? and other M::I questions

(perl Makefile.PL && make dist) will create inc/Module/Install.pm and include it in the tarball.
two responses:
  1. perl Makefile.PL failed. That what I stated in the original post of this thread. I dont see how a use for something in a directory which doesnt exist could work.
  2. should my Makefile.PL look any different?




The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development.

-- Terence Parr, "Enforcing Strict Model View Separation in Template Engines"

  • Comment on Re^2: how could use inc::Module::Install ever work? and other M::I questions
  • Download Code

Replies are listed 'Best First'.
Re^3: how could use inc::Module::Install ever work? and other M::I questions
by ikegami (Patriarch) on Aug 30, 2010 at 20:58 UTC

    I thought you meant from the installer's perspective, not the author's. The author needs to install Module-Install which includes inc::Module::Install.

    When the author runs perl Makefile.PL, it will use the system's inc::Module::Install, and it will copy inc/Module/Install.pm locally. The local copy will be included in the distribution when the author runs make dist.

    This differs from ExtUtils::MakeMaker where both the author and the installer need to have ExtUtils::MakeMaker installed.

[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom