>>>>> "FL" == Federico Lucifredi <[EMAIL PROTECTED]> writes:
FL> Now for the question.... What is the officially sanctioned way to FL> upgrade PERL ? I always build it into a prefix (like /pkg/perl5.8.0) and then symlink /pkg/perl5.8.0/bin/perl back into /usr/bin/perl5.8.0 so I can test things easily by saying perl5.8.0 -e 'foo' perl5.6.1 -e 'foo' etc Then you just change your #! line to point to the more modern perl. FL> I have one complication: the machine in question does not have a c FL> compiler (eh!). I build code for it on another 68k machine (a FL> IIcl, almost the same thing) and then move things over. I am FL> following the instructions in the INSTALL file, but can I build FL> things on the IIcl machine, make a giant tarball with the build FL> environment, and then run make install on the se/30 ? That may work, but you probably don't want to overwrite the system perl. Try building with sh Configure -Dprefix=/some/prefix installing it on the IIcl machine and then tarring the installed directory up and moving it over. I know NetBSD ports for 1.5.1 came with perl5.6.1, but I forget if you can pull a new ports tree in netbsd without doing a whole OS upgrade. -- "The Windows Perl motto: It's just as well there's more than one way to do it because most of them don't work." -- Simon Cozens
