Some modules only have Build.PL, others have both Build.PL and Makefile.PL

If there's no Makefile.PL, then it seems you're stuck with building the module using Module::Build - and therefore perllocal will not be updated. (I suppose you could always hack your way around the issue, but that might be tedious.)
OTOH, if there is a Makefile.PL, then perllocal should be updated if (and only if) you build the module using ExtUtils::MakeMaker,

Annoyingly, my cpanm installation will use the Build.PL if both Makefile.PL and Build.PL are available.
Maybe it's possible to reconfigure cpanm to default to using the Makefile.PL when both Makefile.PL and Build.PL are available. (I don't know.)
I haven't checked to see how the cpan utility handles distros that contain both Makefile.PL and Build.PL.

Modules that I author have never contained a Build.PL. And, for as long as I have control over them, I intend that they never will contain a Build.PL.

Cheers,
Rob

---

---

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