I'm using the Module::Build approach which seems to do a decent job of the basics. However, at the module level I would expect some things were a little easier. Like installing files to a custom place, like /var/www/html.
It's even harder with ExtUtils::MakeMaker. That's probably the reason I'm going to switch to Module::Build.

"When we finally get to the stage where nearly everyone is using CPAN/CPANPLUS (or some similar system of automatically dealing with dependencies, e.g. Debian's debs via apt-get), then life will get much easier for CPAN authors..." Aren't you already there? Who isn't using package systems that automatically know how to resolve things?
Yes I am certainly already there, but if you release some modules on CPAN you'll discover that not everyone is. There's just enough set-up hassles for CPAN/CPANPLUS (e.g. finding a good set of mirror sites to use) that a lot people haven't done this -- I don't know how many, but clearly quite a few haven't.

The biggest unsolved problem with CPAN.pm and CPANPLUS.pm, in my opinion, would be the occasional breakage of deps, and almost as bad, asking the user irritating questions. I don't care if it needs to chug for an hour, I don't want it to chug for an hour and then to hang-up on something.

And further, it's a little hard to see how these problems can be fixed without a centralized agency in charge of cleaning them up (e.g a distro centered on perl?). Possibly the perl world needs to borrow a page from Debian and get a little more fanatic about defining and demanding adherence to Policy.

In reply to Re^4: CPANPLUS broken custom sources by doom
in thread CPANPLUS broken custom sources by zerohero

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.