Going through old list mail and found this one ... don't know if it's still relevant, but ... I have "identical" OS X 10.3.8 installs on two different machines ... identical that is except one has Xcode Developer Tools installed on it, and the other doesn't.

perldoc -f will not work on the Xcode-less machine, and contrary to what is said below, I don't see perlfunc.pod anywhere on the Xcode machine (where perldoc -f works).

any idea what am i missing here (besides the Xcode install)?

Thanks so much.

-Richard

On Nov 11, 2004, at 2:01 PM, Michael G Schwern wrote:

It was suggested that the macosx list might be interested in this
discussion.


----- Forwarded message from Edward Moy <[EMAIL PROTECTED]> -----

From: Edward Moy <[EMAIL PROTECTED]>
Date: Thu, 11 Nov 2004 09:36:54 -0800
To: Michael G Schwern <[EMAIL PROTECTED]>
Cc: [email protected]
Subject: Re: Suggestions to better ship Perl on OS X.
X-Mailer: Apple Mail (2.619)

Yes, I'm still the person.  The splitting of the perl (and other
projects) into different distributions has been a sore point for a long
time.  The historical reason for it was to make a minimum system
installation fit on the minimum number of CDs.  This is of less
importance now that DVDs are being used for distribution, but still a
consideration.

So thanks for reporting the perldiag.pod problem.  The problem of pure
perl modules failing to install because the CORE header files are
missing (which I assume is still a problem) was on my list to get
fixed, but I've busy on so many other things.

Are there any other issues along these lines that I can use as an
argument to keep perl together?  I need to convince the group that does
the actual packaging of the distributions.

Edward Moy
Apple

On Nov 11, 2004, at 1:19 AM, Michael G Schwern wrote:

Hi Ed. I've just gone through putting together a fresh OS X installation
and was reminded of the little nits in Apple's Perl installation that could
use fixing when next they do an upgrade (with Tiger?) I forget who handles
this at Apple, if not you could you please forward this on to whom it
may concern?



1) perldiag.pod is missing from default, diagnostics.pm breaks.

This causes "use diagnostics" to fail. Any code which uses
diagnostics.pm will fail. I tend to notice this when installing Inline.pm.


perldiag.pod is available in the Developer Documentation part of XCode
I believe. I tend to not bother installing that because its nearly a gig
which seems a little silly to get one file.


Recommendation:  Since some code will not run without it, move
perldiag.pod into the default Perl installation.

Typical work around:  Copy perldiag.pod from 5.8.1 source.


2) perlfunc.pod is missing from default, perldoc -f breaks.

Without perlfunc.pod, perldoc -f will not work.

perlfunc.pod, like perldiag, is available in the very large Developer
Documentation part of XCode.  Same problem with perldiag, its silly to
install a gig of docs just to get one file.

Recommendation:  Since perldoc is installed by default and it requires
perlfunc.pod to be fully functional, perlfunc.pod should be installed
by default.

Typical work around:  Copy perlfunc.pod from 5.8.1 source.


-- Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/ the chair. it wants to die. oh no! she sees me! she attacks!




----- End forwarded message -----

--
Michael G Schwern [EMAIL PROTECTED] http://www.pobox.com/~schwern/
Once is a prank. Twice is a nuisance. But NINE TIMES is a TRADITION.
-- Mark-Jason Dominus in <[EMAIL PROTECTED]>





Reply via email to