The CPAN clients (cpan/cpanp/cpanm) take the following steps:

• Download distribution
• Extract distribution
• Does a META.yml or META.json file exist? Okay, parse and look for configure_requires, resolve all the requirements listed there
• Execute Makefile.PL or Build.PL
• If there is a MYMETA.yml or MYMETA.json, parse and look for build and runtime requirements, resolve these
• No, MYMETA files, okay, if there is a Makefile parse that to resolve requirements
• Oh, its a Module::Build based dist, try running 'Build prereq_data' action, if that fails, poke around in _build/ directory to find the requirements
• Resolve requirements
• Execute 'make' for EUMM or './Build' for M::B
• Execute 'make test' for EUMM or './Build test' for M::B
• Execute 'make install' for EUMM or './Build install' for M::B

---

In reply to Re^3: module needs another module for build by bingos
in thread module needs another module for build by dk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":





---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.