OK, after looking at this information, it seems like the much saner thing would be to adhere to the CPAN standard for packaging (e.g. using Module::Starter), and then do a local cpaninject, and use cpan to deploy all my (local) perl packages. This has the slight downside that perl will be "an end in itself". But then again, I'm not going to use perl as base libraries for other programs (e.g. GUI apps).

The basic issue seems to be mixing packaging systems, and the usual problems having two standards causes. Note, however, that there have been people doing auto RPM builds as early as 2003. I stumbled upon this guy's site...http://rpmpan.sourceforge.net/, in addition to the ref you gave.

In reply to Re^2: Using RPMs to package and install your own perl libs by zerohero
in thread Using RPMs to package and install your own perl libs 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.