Of course, it's not just perl modules which will break during the upgrade.
The goal (IMNSHO) is to update and test any affected code during the next several months, so that the official Panther release can be accompanied by a suite of compatible code. The unusual difficulty with this goal is that
* only some of us will have access to the Panther seed release
* the Panther seed release may differ from the official Panther release
I don't see any "silver bullet" for these problems, but I can suggest a few resources we can develop:
* a formal description of the (predicted, relevant) changes in the
official Panther release * sets of upgrade notes (or better, upgrade scripts) that will let
a non-seeded developer approximate the predicted configuration* build and regression test suites for Panther-specific changes
* a table of volunteers, indicating their interests, seed status,
and relevant skillsUsing these resources, we should be able to get past the "access" problem. If the build and regression test suites are available, we may be able to get someone within Apple to run them against internal versions of Panther, reporting any problems that arise.
I realize that this is not a perfect solution, but it seems to fit our needs and capabilities. Improvements are, of course, welcome.
-r
P.S. I know of two Perlies in Apple and two seeded outsiders, but I'm
sure that more can be found, with a little effort...
--
email: [EMAIL PROTECTED]; phone: +1 650-873-7841
http://www.cfcl.com/rdm - my home page, resume, etc.
http://www.cfcl.com/Meta - The FreeBSD Browser, Meta Project, etc.
http://www.ptf.com/dossier - Prime Time Freeware's DOSSIER series
