>> Isn't cpan a wrapper for MakeMaker...

Sure. I've got Module::Build created modules which can do a whole bunch of things, but are at the single module level. You can build, test, and install. The equivalent of "make" built C tarballs in the unix world.

The problem comes at the next level, which have to do with module/dependency and repository. You want to do things like update a server with a single command, based on, say a bundle (and have the package system do the minimal work). MakeMaker and Module::Build are below this level. So we're talking about something that fulfills the role that yum/rpm and apt-get/debian pkgs, does. It's a dependency/repository engine that may be used from a UI or programmatically.

Since cpanp is the newest, and seems to be the anointed replacement to CPAN.pm, it seemed logical to try to master the UI first as this is the driver for the underlying dependency/repository engine. It's a fast way to play around with the underlying technology it is built on. If I can't get that working, then I'd be a little hesitant about the technology (not the Build system, but the dependency/repository system). I'm pretty confident I could do something on Build as this seems solid. The question is whether I'd have to write my own "rpm like tool". This seems absurd considering cpanp's existence.

Note I'd used cpan a lot, but just to install things, and so I was familiar with how fairly robust that was, and at least new the places where things would occasionally break. It was this experience that gave me confidence this would be a "piece of cake."

Plus this is such a basic problem for module systems that I would assume this is a completely solved problem (considering how well cpan has worked).

Note, I don't know a lot about MakeMaker, but assume Module::Build is equivalent.

In reply to Re^2: CPANPLUS broken custom sources by zerohero
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.