Re: Perl install problems OSX 10.4.11

Hi Doug,

Just before I create the file I would like to check a few points.

> but you should edit that so that the first directory, before the  
> first separating colon, is the one that perl 5.10 is in

I am not quite sure which is the main Perl folder.  /usr/local/bin  
contains two Unix executable Perl files — Perl and
Perl 5.10.1. I assume that this should be the first directory.

Which files is PERL5LIB. All the installed modules are stored in /usr/ 
local/lib/perl5/5.10.1/. Is this the location of
the PERL5LIB. If so, do I need the full path /usr/local/lib/ 
perl5/5.10.1/ or can I use /usr/local/lib/.

If the above is correct, then the following is what I think I should  
write to a plist file.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http:// 
www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
         <key>PATH</key>
         <string>/usr/local/bin:/usr/local/lib:/opt/local/bin:/opt/ 
local/sbin</string>
         <key>PERL5LIB</key>
         <string>/usr/local/lib/perl5</string>
</dict>
</plist>

opt/local/bin and /opt/local/sbin is taken from a .profile created by  
MacPorts which
I hope will preserve the links for MacPorts.

Thanks,

Terrence


On 15 Sep 2009, at 04:18, Doug McNutt wrote:

> At 01:10 +0100 9/15/09, Mine wrote:
>> Hi Doug,
>>
>> Thanks for the info, but I think this possibly way out side my  
>> level  of experience.
>> Would what you have suggested allow get_iplayer find the path to  
>> Perl  5.10.1
>> when I try to run get_iplayer from the terminal?
>>
>> If it does then I don't fully understand your instructions.
>> I assume mkdir $HOME/.MacOSX creates a directory. I tried it but   
>> could not
>> find the directory. When I used cat > $HOME/.MacOSX/ 
>> environment.plist  in the
>> Terminal, it seemed to hang.
>>
>> When you say "paste the text of the new file here" what text do  
>> you  mean?
>
> cat, used that way is waiting for you to paste the text onto the  
> Terminal screen.  The text will become the contents of the  
> environment.plist file.
>
> The problem is that Apple takes pleasure in making things difficult  
> for users who might be able to muck something up. Those leading  
> dots typically identify files that are private to the system. You  
> can see dotted files with the unix command  "ls -a" for list all.
>
> cat stands for concatenate which reads standard input, the terminal  
> screen, and writes to standard out which the > directs to a file.   
> You use control-D to terminate the input. I also used cat to  
> display my environment.plist file. You can see the command that  
> immediately precedes the text.
>
> But remember that you do have to edit the copy of my file to meet  
> your needs. It is likely that you need only the PATH part but you  
> should edit that so that the first directory, before the first  
> separating colon, is the one that perl 5.10 is in. You probably  
> don't want my personal bin directory but you might want to have a  
> PERL5LIB directory which could also contain modules that would be  
> found wherever perl came from. The /bin and /usr/bin items are  
> pretty much required. cat, for instance, gets found that way.
>
> The file format is xml. Entries are in pairs of lines <key> defines  
> the name and <string> declares the corresponding value.
>
> You might well have a text editor, bbedit or text wrangler (its  
> free cousin)  come to mind, that would have no problems dealing  
> with directories whose names start with a dot. That would be fine  
> in place of unix tool cat.
>
> You could also use Apple's plist editor but I suspect it would  
> confuse you more than it would help. I dislike it.
> -- 
>
> --> From the U S of A, the only socialist country that refuses to  
> admit it. <--