Update Perl to version 5.10.x [PSARC/2009/315 FastTrack timeout 06/02/2009]

[James Carlson]

I. Szczesniak writes:
> On 5/26/09, James Carlson <James.D.Carlson at sun.com> wrote:
> >  I'll be glad to see it go (eventually) for the improvement in build
> >  time,
> 
> Is this the only justification?

It's the only difference, so, yes.

> Bits delivered via SFW commonly have
> substandard quality and are very poorly integrated. I fear that
> putting a critical system component such as perl into SFW will affect
> the quality of Opensolaris as whole piece.

That doesn't make any sense to me, and I object to having aspersions
cast on the supported open source code that delivers through SFW.

With either consolidation, the Perl code that's present is essentially
just what comes from the open source, as it is with _many_ projects
that happen to deliver through ON -- including, incidentally, ksh93,
where we're not doing extensive code or design reviews up to the
normal ON standards, because they'd just be infeasible.

The big difference between the two is in makefiles: you use your own
in SFW, but you generally must use ON's in ON.  That difference is why
I argued (more than once) for delivering ksh93 through SFW.  It'd be
simpler and lower overhead, and there's no necessary entanglement with
the rest of the core OS.

> If there is no other justification build time please keep perl in
> ONNV. Or derail this case and write memo why perl should move to SFW.

Sorry, I disagree.

Perhaps you're thinking of the old Freeware (/opt/sfw) system, where
it really was the wild west, and compiling was enough.  That has
nothing to do with the SFW consolidation, which delivers all sorts of
things into /usr/bin.

If moving Perl to SFW somehow lowers quality, then there's a *MUCH*
bigger problem afoot than just Perl, and derailing this case to write
a memo will not fix it.  If that were somehow true (and I'm fairly
certain it's not), then some systemic defect in SFW itself would need
to be addressed.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677