See the section on "Installation Prefix" in the INSTALL file that comes with your Perl distribution.
There are several other useful sections in that file:
The documentation that comes with Perl is _very_ comprehensive. It's well worth getting to know it.
--
< http://dave.org.uk>
"The first rule of Perl club is you do not talk about
Perl club."
-- Chip Salzenberg
| [reply] |
Good post, Karlos.
This is something I have done several times, and I feel that the INSTALL document, highlighted by davorg, although useful background reading, does not give the complete picture.
Take a look at my use.perl journal for some relevant entries and a few handy tips.
The main points to bear in mind are that $ENV{PATH} determines which perl your perl command chooses, but the shebang (#!) can point to the other perl if that's what you want. It might be a good idea to leave the perl that came with the operating system alone, as upgrade scripts etc. may be dependent on this working. The convention is to have the default perl in /usr/bin, and your custom one in /usr/local/bin, but in fact you could put it anywhere.
Are you planning to build your own perl? If you are (or if you're using someone else's built with gcc), I seriously recommend using gcc, and having a working gcc for building extensions, as the native C compiler that comes with hp-ux is a pain.
--
Oh Lord, won’t you burn me a Knoppix CD ?
My friends all rate Windows, I must disagree.
Your powers of persuasion will set them all free,
So oh Lord, won’t you burn me a Knoppix CD ?
(Missquoting Janis Joplin)
| [reply] |
I concur with rinceWind regarding leaving the system perl well alone. I once made the fatal error of updating the system perl on a DG/UX box, which promptly broke many of the startup scripts.
I've learnt to leave well alone with vendor installed perls since, >:o)
| [reply] |
I've found these binary distributions of Perl for HP-UX very useful.
Not only are they a quick way to get going, they include a good number of CPAN modules, some of which can be tricky to compile on HP-UX.
If you can't use them directly, they also serve as a template for installing multiple versions and for creating HP-style packages called "depots".
Update: added details
| [reply] |