Irrespective of how well (or how badly) you made your point, it is certainly true that I missed it :-)
I can't fault most of what you have written here. My only doubt relates to:

The point is that package managers assume that no compile is needed on the target, and no compiler is necessary

With a properly built Inline::C binary package that's the case. All that the target needs is to have Inline installed - and it's quite possible to install Inline on a machine that doesn't have a C compiler. For the details of one way to construct such a binary package, see "How do I create a binary distribution using Inline?" at http://search.cpan.org/~ingy/Inline-0.44/Inline-FAQ.pod.

Similarly, with Steffen's proposed module, I think it should be possible to create a binary that will work on a target machine that does not have a compiler. As long as the package contains the necesary so/dll, then XSLoader will load it and all should be sweet, so long as the target machine has Module::Inline::C installed. (That's if I understand Steffen's proposal correctly ... which is by no means guaranteed.)

Basically, whether it's a straight out Inline::C module, or a Module::Inline::C module, it will be possible (albeit, perhaps kludgy) to build a package that doesn't need a C compiler on the target machine. On thinking further about it, I suspect that creating the binary package will be less of a kludge with Steffen's module than with Inline::C.

Of course, having written all of this, it now occurs to me that perhaps you were simply wanting to make Steffen aware of the 'packaging' aspect ... to which I can only say "Good point!" :-)

Cheers,
Rob

In reply to Re^4: Making Inline::C modules fit for CPAN by syphilis
in thread Making Inline::C modules fit for CPAN by tsee

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.