At 17:29 -0700 2001.07.20, Peter Prymmer wrote:
>> http://dev.macperl.org/
>
>So much for URL stability.
The old URL still works, and will continue to as long as we are using
SourceForge. But this one is more stable; if we decide to move the site
from SourceForge, then it will still be OK. It's also a lot shorter and a
lot better. Thanks to Rich and Vicki for helping me get it up (along with
cvs.macperl.org, too).
>A quick question for anyone up to it: does the installperl script in the
>main perl distribution work at all on Mac OS.
I've never used it. Looking at it, I can tell it wouldn't, for the reasons
you suspect.
>I have recently been
>studying it for use in an ivp build procedure and noticed that it seems to
>make use of File::Find and liberal use of '/' path separators hence my
>suspicion is that it will not work at all on Mac OS. I've also uncovered
>some problems in t/harness (er, :t:harness) that indicate problems (catdir
>used for MANIFEST when catfile ought to have been, multiple * globbing
>etc).
* globbing should work fine in MacPerl (via File::Glob), although <*/*>
won't. I actually patched t/harness for that globbing problem (just
changing all the foo/* to :foo:*), but I never included it. The main
problem with t/harness is an insurmountable problem: some of the perl test
scripts have call other perl scripts, and MPW can't handle three running
processes at once. It can only handle two, with the help of ToolServer.
So harness -> test script -> other test script breaks.
So that's why I wrote MacPerlTests.cmd; it is a little shell (er, MPW :)
script to run all the test and report the results. It has to be a shell
script that runs each test, I think. That said, there is plenty of room
for improvement in the current script. It is pretty dumb right now, but it
gets the job done.
Thanks,
--
Chris Nandor [EMAIL PROTECTED] http://pudge.net/
Open Source Development Network [EMAIL PROTECTED] http://osdn.com/
