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.