in reply to Makefile.PL: Howto make OS dependent modules

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?
  • Comment on Re: Makefile.PL: Howto make OS dependent modules

Replies are listed 'Best First'.
Re^2: Makefile.PL: Howto make OS dependent modules
by vicdan (Novice) on Jan 07, 2015 at 21:30 UTC

    Yes, youīre right, thereīs only Perl stuff in it.

    And as you assumed, the base module as well as the binary do test the OS and decide what they need (and complain if they donīt find it).

    The reasons why wanted to be able to split it up are rational reasons like to make the rpms smaller and fit to the underlying OS, and that this also could be some kind of template for bigger projects.

    On the other hand maybe there are some irrational reasons like: It looks like a wonderful, ordering, esthetic thing to me to do it that way. I know there must be some way to do it and it really iches me that I donīt know how...