Re: [MacPerl-Porters] Identifying Ported Modules

[Matthew Langford <langfml [at] eng [dot] auburn [dot] edu>]

On Fri, 7 Jan 2000, Paul Schinder wrote:

> If after all these changes you still think there's a problem, then 
> maybe we should do something.  Personally I think that it'd be wasted 
> effort at this time.

Okay, these arguments sound pretty convincing for case 2, the Bundle
Problem and Unport-Wiping-Out-Good-Port.  It should go away sometime in
the next two years, or at least the next five.  (One year 'til MacOS X is
bundled on machines, and one year 'til a critical mass of owners builds
up.) 

But Case 1 may not go away:  as I understand it, the standard MacOS X
install won't include egcs/gcc.  Has this changed?

CPAN.pm/installme _should_ recognize this obvious and somewhat common
breaking point on MacOS:  an XS file but no Mac build.  Even after MacOS X
arrives, CPAN.pm/installme can test for the existence of a compiler
(maybe it should be an ENV var set by the MacPerl/Perl install?). If
one is not available, the same error is applicable.



--
MattLangford 




==== Want to unsubscribe from this list?
==== Send mail with body "unsubscribe" to macperl-porters-request@macperl.org