On Wed, 20 Jan 2010, p sena wrote:
> I am using few cpan modules for cli application/tools to run in a
> server or worksations. Those cpan modules i installed as root in the
> server and use them along with the perl programs which are there in a
> version control. Well, in the server it seema Ok to do so. But those
> tools can be used by users in their workstations also after pulling
> them from the version control. In that case those cpan modules will
> not be availaible to the users readily and thus a tool(s) can fail. I
> dont want let every user donwload the pre-requisite cpan modules and
> then use the tools. Even though i want to make the cpan modules
> available readily to the users also and use the tools Ok. In other
> words, i think i mean, i want to package all of my modules, cpan
> modules and standard modules into one.
>
> What would be the best solution for this? Is it ok to put the
> cpan modules also in version control and keep track? Or any other
> ideas pls.
Yes, I think it is perfectly fine to put additional CPAN modules
into version control to make sure your application always uses
a consistent and compatible set.
It sounds like your users already all have a local Perl installation
available (and access to your version control system). Otherwise it
might also be an idea to wrap your application with a tool like
PerlApp from the ActiveState Perl Dev Kit, which will give you a
single executable that can run even on machines that don't have Perl
installed at all:
http://www.activestate.com/perl_dev_kit/
Cheers,
-Jan
_______________________________________________
ActivePerl mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
