Thomas von Eyben wrote:
> Hi Alexander,
>
> Many thanx for you quick and precise reply, it's much appreciated(!)
>
> On Mon, Apr 6, 2009 at 1:44 PM, Alexander Hansen
> <[email protected]> wrote:
>   
>> Thomas von Eyben wrote:
>>     
>>> Hi list,
>>>
>>> Very much inspired by the sideeffects of Security Update 2009-001 and
>>> the need to test http://backuppc.sourceforge.net I am now trying to
>>> use cpan installed via fink. Unfortunetaly I am experiencing (for me)
>>> big difficulties.
>>>
>>> I have tested on two fully updated different (PPC) 10.5.6 testmachines
>>> one Mac OS X Server, the other Mac OS X Client. Both give me the same
>>> problems…
>>> (One test was allowed to use the unstabkle branch, the other only the
>>> stable branch).
>>>
>>> Heres the complete description of my experiences (MAYBE step #9 is the
>>> most relevant one!)?
>>>
>>>
>>> PS.: I am wondering why there is not a fink supplied perl version 588.
>>> I just read on another thread, that fink does not provide the same
>>> version of perl as the OS.
>>>
>>>       
>> Unlike the case of Python, where
>>
>> 1) Historically Apple shipped Python without the requisite headers so
>> that nobody could actually build against it
>> and
>> 2) Many of our python-using packages want an X11-based python, which
>> Apple doesn't provide, so we have to.
>>
>> The system's perl has been usable.
>>     
>>> Due to the sideeffects of the Security Update 2009-001 I wnat/need to
>>> be able to leave Apple's perl installation (well the cpan part)
>>> untouched.
>>> How can I acheive this via fink?
>>> - Maybe my limited perl knowledge is why I can't seem to figure out
>>> how to do this, please enlighten me.
>>>
>>> 1. I installed fink (fink-0.9.0-full.tar.gz as well as
>>> Fink-0.9.0-PowerPC-Installer.dmg)
>>>
>>>
>>> 2. Updated fink
>>> test:~ ladmin$ sudo fink selfupdate
>>>
>>>       
>> You don't need to preface the "fink" command with sudo.
>>     
> Ah, nice (that will save me som typing)
>
>   
>>> (installed Fink 10.5-0.9.0.2)
>>>
>>>       
>> You will not be getting any current stable sources (you're looking at
>> package descriptions from last July right now) without running
>>
>> fink index -f
>>     
>
> Strange - 'man fink' does not have this information it 'only'
> describes 'fink index' (I assume -f = force?)
>   
It's missing that, yes.  -f means "forcibly rebuild package cache"
>> fink selfupdate-rsync
>>     
>
> But the FAQ does:
> http://www.finkproject.org/faq/upgrade-fink.php?phpLang=en
>
> Except that it suggest some more steps:
> fink selfupdate
> fink selfupdate-rsync
> fink index -f
> fink selfupdate
>
>   
(I'm aware of this, having written it)
There's some optimization here that could be done, but I have no time
currently to do so.
>>> test:~ ladmin$ sudo fink update-all
>>> (No packages to install.)
>>>
>>>
>>> 3. Installed perl586 *
>>> sudo fink -b install perl586
>>>
>>> Got one warning - assuming it's not a problem:
>>> WARNING: Fink::Services: Illegal version specification: <= 2.34_01-10
>>> at 'getopt-long-pm581-man (<= 2.34_01-10)' in perl586
>>>
>>>
>>> 4. Verified that I was using the fink supplied perl for my cpan 
>>> configuration
>>> test:~ ladmin$ which perl
>>> /sw/bin/perl
>>>
>>>
>>> 5. Launched cpan
>>> sudo cpan
>>>
>>>
>>>       
>> Apple's sudo doesn't pass Fink's environment on to perl, by default.
>> You can work around this, if needed, by using
>>
>> sudo env PERL5LIB=/sw/lib/perl5:/sw/lib/perl5/darwin cpan
>>     
> I don't think I need/want that - I want to keep the two perl
> distributions as seperate as possible (I also guess that's why fink's
> default is set as it is :)
>
>   
Maybe not; but it is applicable for modules installed via fink for
either Fink's perl or Apple's.  We use that PERL5LIB for either case.
So _if_ you installed any perlmods via Fink, you'd need to use that
sequence when running under sudo to make sure those modules are visible.
>>> Configurering cpan with the default answer except for one parameter:
>>> "Policy on building prerequisites (follow, ask or ignore)? [ask] follow"
>>> (I don't want to have to press OK all the time delaying my TEST 
>>> installation)
>>>
>>> 6. Noting that the fink provided tools are indeed being used as well
>>> as the latest version of xcode (xcode312_2621_developerdvd)
>>> …
>>> Where is your gzip program? [/sw/bin/gzip]
>>> Where is your tar program? [/sw/bin/tar]
>>> Where is your unzip program? [/sw/bin/unzip]
>>> Where is your make program? [/usr/bin/make]
>>> …
>>> commit: wrote /sw/lib/perl5-core/5.8.6/CPAN/Config.pm
>>> Terminal does not support AddHistory.
>>>
>>> cpan shell -- CPAN exploration and modules installation (v1.7601)
>>> ReadLine support available (try 'install Bundle::CPAN')
>>>
>>> 7. Tried to update cpan
>>> cpan> install Bundle::CPAN
>>>
>>>   There's a new CPAN.pm version (v1.9304) available!
>>>   [Current version is v1.7601]
>>>
>>> 8. Getting a lot of errors (showing the relevant ones):
>>> #     Tried to use 'Compress::Raw::Bzip2'.
>>> #     Error:  Can't locate Compress/Raw/Bzip2.pm
>>>
>>>       
>> Since you're using Fink's Perl, you can install fink's compress-bzip2-pm586
>>     
>
> I am not sure if/what the sideeffects / advantages will be using your
> suggestion (I am still getting my feet wet with perl/fink).
> What is the difference (compatibility/performance etc.) between EG
> installing fink's "archive-zip-pm586" or using CPAN to install
> "Archive::Zip"?
> I ask since backuppc specifically states the requirements of the
> beforementioned perl libraries
> (http://backuppc.sourceforge.net/faq/BackupPC.html#requirements) and I
> lack the knowledge to identify the impact of your (most welcom)
> suggestions.
>
>   
There shouldn't be any:  other than installing in a special location,
our Perl modules should be the same as if you installed them from CPAN
or built them yourself.
>>> …
>>> #     Tried to use 'Archive::Zip'.
>>> #     Error:  Can't locate Compress/Zlib.pm in @INC
>>>
>>>       
>> archive-zip-pm586
>>     
>>> …
>>>   CPAN.pm: Going to build E/EW/EWILHELM/Module-Build-0.32.tar.gz
>>>
>>>       
>> You can use fink's module-build-pm586
>>     
>>> # running Build.PL
>>> /sw/bin/perl5.8.6 Build.PL
>>> Checking whether your kit is complete...
>>> Looks good
>>>
>>> Checking prerequisites...
>>>  - ERROR: Test::More (0.47) is installed, but we need version >= 0.49
>>>  - ERROR: File::Temp (0.14) is installed, but we need version >= 0.15
>>>
>>>       
>> file-temp-pm586
>>     
>>> 8 . Quitting cpan and relaunching now no longer posssible due to error:
>>> Can't locate Mac/Files.pm in @INC (@INC contains:
>>> /sw/lib/perl5-core/5.8.6/darwin-thread-multi-2level
>>> /sw/lib/perl5-core/5.8.6
>>> /sw/lib/perl5/site_perl/5.8.6/darwin-thread-multi-2level
>>> /sw/lib/perl5/site_perl/5.8.6
>>> /sw/lib/perl5/site_perl/5.8.6/darwin-thread-multi-2level
>>> /sw/lib/perl5/site_perl /Users/ladmin) at
>>> /sw/lib/perl5/site_perl/5.8.6/File/HomeDir/Darwin.pm line 66.
>>>
>>> 9. Googling for this error finds this interesting articel:
>>> http://www.codeweavers.com/support/wiki/CXOfficeMacPerl
>>> States that my perl configuration may be messed up by fink
>>>
>>>
>>>
>>>       
>> Incorrect.  We don't overwrite anything in the system area.
>> More to the point, you're not using the system's Perl at all.  That was
>> your whole point earlier.    _You_ broke your *Fink-installed* Perl
>> through the incomplete cpan install.
>>     
>>> The test system does indeed have the file
>>> "/Library/Perl/5.8.8/AppendToPath" with the correct content, but I am
>>> sure it not known to the fink supplied version of perl.
>>>
>>>       
>> They're different versions, so we deliberately don't look at it.
>>     
>>> The (Mac OS X provided) Files.pm is indeed also present (as expected :)
>>> /System/Library/Perl/Extras/5.8.8/darwin-thread-multi-2level/Mac/Files.pm
>>>
>>>
>>>
>>>       
>> Nothing from Perl 5.8.8 is relevant here.
>>     
>>> 10. I tried to install Mac:Files manually
>>> http://search.cpan.org/~cnandor/Mac-Carbon-0.77/Files/Files.pm
>>>
>>> perl Makefile.PL
>>> make
>>> make test
>>> make install
>>>
>>> but received also many errors:
>>> Result: FAIL
>>> Failed 1/18 test programs. 0/2800 subtests failed.
>>> make: *** [test_dynamic] Error 255
>>>
>>>
>>>
>>>       
>> (noting that you've followed up with a message that you have now been
>> able to install Mac::Files)
>>     
>>> *
>>> During this installation I get som feedback in my native language (danish):
>>> "Vælger tidligere fravalgt pakke perl586."
>>> I would really like to get all my feedback in english thus making in
>>> easier to debug. I guess that this behavior is due to my choice of
>>> danish mirrors?
>>> Is this correct?
>>> How can I change fink so that it speaks english to me ;-)?
>>>
>>>
>>> BR TvE
>>>
>>>
>>>       
>> "fink" only knows English.    Other tools know how to cope with other
>> languages, and it is they who are giving you output in Danish.
>>     
>
> Great, at least i know which tool is NOT responsible for the
> "incorrect" language ;-)
>   
>> --
>> Alexander Hansen
>> Fink User Liaison
>>
>>
>>     
>
> In retrospect:
> When I start over (to make sure the procedure is correct before
> installing on the "real" live server) could my problems regarding the
> broken cpan installation have been avoided if I had:
>
> A. Updated fink (as described from you) before attempting to update cpan?
>
>   
That'd be a good idea.
> B. Installed these packages via fink before attempting to update cpan?:
> compress-bzip2-pm586
> archive-zip-pm586
> file-temp-pm586
>   
That's optional; I'm biased toward installing via Fink rather than CPAN
because it's easier to remove packages.
> If I had performend A+B (or just one of them…) would I then not need
> to manually install Mac::Files?
>
>   
Apparently, yes.
> I will later wipe my testinstallation to make sure, but any good
> suggestions are much appreciated.
>
>
> BR TvE
>   


-- 
Alexander Hansen
Fink User Liaison


------------------------------------------------------------------------------
_______________________________________________
Fink-beginners mailing list
[email protected]
http://news.gmane.org/gmane.os.apple.fink.beginners

Reply via email to