On Thursday, August 15, 2002, at 06:55 , Kay R�pke wrote:
> On Thursday, August 15, 2002, at 03:12 PM, drieux wrote:
>
>> so all I really want to know is
>>
>> "what is the canonical orthodox perl way
>> as executed in the canonical orthodox apple way?"[4]
>
> The orthodox perl way is laid down in the hints file for your favorite
> (most
> despised ... ) type of system.
I use to have prejudices, now I just hate them all....
8-0
I had been trying to avoid becoming 'the perl guy' -
the keeper of the canons of what rev of perl is stable,
what modules we just have to have from the CPAN.... etc...
{ just as once I tried to avoid being the 'gcc guy' - but
you know how that goes - if it is a tool set you need, and
no one else steps up to the plate, one becomes the 'subject
matter expert' by default... }
So this is rather the 'good news and information' set that
comes with using open source solutions.... the good news
is that you have the source and can rebuild it - the
information is that you need to stay on top of the 'good news'....
[..]
> The darwin hints file says:
> If prefix is empty use non-system directories, i.e.:
> # Default install; use non-system directories
> prefix='/usr/local'; # Built-in perl uses /usr
> siteprefix='/usr/local';
> vendorprefix='/usr/local'; usevendorprefix='define';
>
> # Where to put modules.
> privlib='/Library/Perl'; # Built-in perl uses /System/Library/Perl
> sitelib='/Library/Perl';
> vendorlib='/Network/Library/Perl';
>
> If prefix is /usr replace the system perl.
THUNK! why didn't I think about the 'hints'....
thank you! I hope the coffee kicks in...
> If you don't trust automated software updates
I think its more a case of 'trust but verify'....
the problem of course has been the 'transitional periods'.
various 'vendor supplied' versions of perl have come without
the USE_LARGE_FILES definition - which means that things like
if( -f $file ) {
....
}
'fail' if $file happens to be bigger than 2Gigs...
In like manner - on our linux boxes - red hat has been
upgrading with things in the 'i386' "architecture" - so
one can not just blindly take 'the defaults' if your machine
returns i686 - and hence your new build of perl will not,
"by default" have the right sets of paths in @INC...
So one of the obligations is that 'all perl code will work'
hence IF the vendor supplied version is not built, as
the default darwin is built, with
Compile-time options: USE_LARGE_FILES
then we have to rebuild it...
So far the Mac side of the house seems to be reasonable enough.
That I have been able to avoid having to do any specific builds
of perl - but will most likely have to do so with the 5.8.1 release...
So i thought I would just start planning ahead.
[..]
ciao
drieux
---
