The only Perl modules that shouldn't be architecture-independent for the purpose of RPM are ones that use XS. But it's pretty clear from how the question was asked that there's no XS involved here. Your script could depend on modules that use XS, and hence are architecture-specific, but that's no reason to make your script architecture-specific unless you bundle those modules with your script's distribution.

Labelling those dependencies is another problem. It seems like older perl RPMs provided things like "XML::Simple" or maybe it was "perl-XML-Simple". Newer ones now seem to instead provide "perl(XML::Simple)".

In reply to Re^2: Can a perl program always be architecture-independent? by sfink
in thread Can a perl program always be architecture-independent? by ghenry

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.