|Pathologically Eclectic Rubbish Lister|
Spliting own program distribution intoi several modules.by vsespb (Chaplain)
|on Dec 27, 2012 at 08:35 UTC||Need Help??|
vsespb has asked for the
wisdom of the Perl Monks concerning the following question:
I want to distribute perl command line program (say myscript.pl in myscript.zip), which split into several modules. Some modules are really useful and I am going to publish it in CPAN (for example one of them is Net::MyModule).
myscript.zip can come with installer (or have myscript.deb/myscript.rpm in it) which installs all modules into global location.
I am wondering how to deal with possible conflict of Net::MyModule from CPAN and Net::MyModule from myscript.zip ( myscript.deb ) ?
Obvious solution is 1) distribute myscript.zip without Net::MyModule 2) Publish Net::MyModule on CPAN 3) Ask/force users to install Net::MyModule from CPAN
But I don't want' to do that currently as myscript.zip works without external dependencies (except Core modules) with any perl version higher that 5.8.8. So I don't want bother non-Perl users to install something using CPAN ( I wan't easier deploy ). Another reason is that I might want to fix something it Net::MyModule and make it immediatelly available with new version of myscript.zip
What are options here?