Module naming problem

sdetweil has asked for the wisdom of the Perl Monks concerning the following question:

For my multi-platform application I now need to deploy on Solaris 10 x86. I was able to download and install all the extra modules required without problem. The final packaging is done with Perl2exe to get a self contained executable. somewhere between the first Solaris build in 2009 and now some of the modules have been extended (duh!).. and they have different dependencies..

in the version of Perl2exe I need to use, they bundle the module files so they can be used, but .so files only have one directory, and I now have a file name collision problem.

Archive:Zip uses Compress:Raw:Zlib (which creates Zlib.so) and LWP uses Http:Message, which uses Compress:Zlib which has a different Zlib.so.

the last one bundled wins.. which for me is Compress:Zlib's version, which is different, (missing the boot__Compress__Raw__Zlib .. function)

so the Archive modules won't work.

so.. before I go off making a mess, making a new package with a different name and changing the code to use the new package.. is there some perl packaging magic I can do here (change the interface module name under a module, without changing the source)

thanks for your ideas

Comment on Module naming problem

Replies are listed 'Best First'.
Re: Module naming problem by afoken (Chancellor) on Feb 05, 2013 at 18:45 UTC
Get rid of the packer tools. Distribute the source, and include a script to install (or at least list) the required modules. See Bugzilla's checksetup.pl and install-module.pl for a working example. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]
Re: Module naming problem (NOT) by Anonymous Monk on Feb 05, 2013 at 14:46 UTC
What has "Module Naming" got to do with perl2exe? Maybe you should distribute your stuff with http://www.cavapackager.com/ or perlapp or par?	[reply]

Back to Seekers of Perl Wisdom