Did I form a misimpression or jump to a false conclusion about something because of my brief experience?

Yes. One simple example However, it is inherently less portable because it assumes that make is installed.

make has been a prerequisite to build perl/modules for a very long time, and the newest versions of cpan/cpanp(or is it Module::Install/Module::Build/ExtUtils::MakeMaker) will install make if its missing (on win32).

But they start much earlier, with the first paragraph

The last day or two I've been learning how to prepare a module for CPAN distribution. There doesn't seem to be a good tutorial anywhere explaining how this all works. The two tutorials I found on Perl Monks are quite old. One was written in 2002 and the other in 2005. Neither discusses newer tools like Module::Build. Nor do they explain how CPAN works, let alone discuss how this process can be safely and reliably customized.

Well, the two tutorials you linked to are good, they're more comprehensive than your apparent rebuttal, they mention

• http://cpan.org/misc/cpan-faq.html
• perlnewmod
• perlmod
• perlmodlib
• perlmodinstall
• http://cpants.perl.org/kwalitee.html

I believe you intended to write a tutorial and not rebuttal, so its best to avoid invoking other tutorials :)

Also, this link https://pause.perl.org/pause/authenquery?ACTION=pause_namingmodules requires a PAUSE account.

These do not

http://www.cpan.org/modules/04pause.html#namespace

On The Naming of Modules

You should definitely check out Module::Install.

Keep up the good work, I'm sure this will eventually make a good addition to Tutorials: Modules: How to Create, Install, and Use: Creating and Distributing Modules

---

---

• 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.