Your manifest looks like it's only got pure Perl stuff in it, no XS, right? I'm not quite sure I understand the reason for needing to make several modules out of it - why not just one distribution with everything in it, and let the code decide which of the modules to load (and test during installation)? The only downside I see is having a few extra unused files lying around on your disk (and perhaps the minor runtime overhead of choosing which module to load, but it sounds like you need to do that anyway)... Don't know much about rpms, is there some reason that wouldn't work?

In reply to Re: Makefile.PL: Howto make OS dependent modules by Anonymous Monk
in thread Makefile.PL: Howto make OS dependent modules by vicdan

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.