On Tue, Jun 17, 2003 at 08:23:55AM -0500, Lorin Rivers wrote: > > On Tuesday, June 17, 2003, at 05:13 AM, Michael Maibaum wrote: > > >I would strongly recommend against this approach, or if you use it, > >expect problems if/when you upgrade to Mac OS X 10.3. > > > >The darwinports perl builds fine to the best of my knowledge, and if it > >doesn't I want to know as I maintain the package. (On that note, if > >anyone has any suggestions for package variants that would be useful > >let > >me know, I'm going to add a variant for a debugging perl, threads, > >anything else?) > > What will happen if I use the darwinports perl? Does it automagically > replace the existing perl in terms of the command line and what not? Or > would I have to use "/opt/bin/perl" for 5.8.0 (and just "perl" for 5.6)?
DarwinPorts perl will not touch /usr/bin/perl (ie Mac OS X's standard perl). What I do is replace /usr/bin/perl with a symlink to the 5.8 version of perl, that allows things to work with my 'new' perl, but means it is easy to go back to Apple's 'system' perl by simply deleting that symlink and replacing it with one pointing at /usr/bin/perl5.6.0 > > I'm asking all these questions because I have hosed my perl more than > once out of ignorance (most people find installing and configuring perl > a trivial task, I'm sure) and want it mostly for using prebuilt scripts > and tools, not for writing my own perl (shudder). If you are using prebuilt scripts that need a newer perl, I'd probably use the symlink approach described above, then you can easily back out of the newer pero if you need to, but most scripts etc should, 'just work'. HTH Michael -- Dr Michael A. Maibaum internet: [EMAIL PROTECTED] | http://mike.maibaum.org/ voice: [h] 07958 604025 | [w] (020) 7631 6725
pgp00000.pgp
Description: PGP signature
