Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Re: Packaging perl modules for installation

by jZed (Prior)
on Sep 27, 2004 at 20:50 UTC ( #394347=note: print w/replies, xml ) Need Help??

in reply to Packaging perl modules for installation

If some of the modules you are using are XS modules and the machines have different perl versions, then you may not be able to simply copy files even if you knew the @INC locations.

Since production is a locked down environment PPM is out of the question.

Do you mean that using PPM to retrieve remote files is out of the question or that using PPM at all is out of the question? Assuming all your machines are the same platform and can all use binary compatible XS modules, and assuming it's just the remote access that is stopping you, you can download the .ppds onto your development machine, write a script that successively calls PPM on all of the local .ppds, then distribute the script + .ppds to all the production machines. Running the script on each machine will use that machine's perl and @INC to do the local install but won't have to connect to the internet.

You could also do something similar with, but that would assume that is configured on all of the production machines.

  • Comment on Re: Packaging perl modules for installation

Replies are listed 'Best First'.
Re^2: Packaging perl modules for installation
by Anonymous Monk on Sep 27, 2004 at 20:55 UTC
    I can use PPM on a non-production machine so I think your solution will work. Thanks jZed.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://394347]
[choroba]: Maybe it's the other way round?
[Discipulus]: ?
[Discipulus]: him refusing the job?
marto waves

How do I use this? | Other CB clients
Other Users?
Others wandering the Monastery: (5)
As of 2018-03-22 09:09 GMT
Find Nodes?
    Voting Booth?
    When I think of a mole I think of:

    Results (273 votes). Check out past polls.