logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

[Module::Build] Module::Pack: msg#00224

Subject: [Module::Build] Module::Pack
Hi there

I noticed in some sort of Module::Build docs there is reference to being able to specify that your module dependencies are bundled into the /inc directory (as dist tarballs I presume) and installed using those instead of from CPAN (unless CPAN is newer?).

I have an application builder that tracks the dependencies of the applications it builds.

Currently this results in a MODULES.txt file that lists the module and (optionally) it's minimum version, so the admin has a fairly straight forward list of stuff to install.

Now, for most admins on bigger stuff it's fine, but for the smaller or firewalled or whatever cases, I'd like to be able to build a "module pack".

Rather than contain the application, it would just contain a packed up set of all the dependencies (and recursively so on?) which could be installed using Module::Build.

This "module pack" would be released seperately to the main application pack.

Can anyone suggest if a) it is possible b) it is easy...

The docs are a little confusing... I had thought about creating some kind of one-off uniquely named bundle module, but that seems a little
workaroundy.

Adam K


-------------------------------------------------------
This SF.Net email is sponsored by: InterSystems CACHE
FREE OODBMS DOWNLOAD - A multidimensional database that combines
robust object and relational technologies, making it a perfect match
for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8


<Prev in Thread] Current Thread [Next in Thread>