Stefan Teleman wrote:
> The PHP Group currently has *no interest whatsoever* in Solaris. 

That is too bad, but doesn't really change my suggestion that it
would be good to push these changes upstream so that others could
benefit from it.  Ask yourself how the various OpenSolaris distros
(including pseudo-distros like SunFreeware, Blastwave, ...) could
all benefit from this work?  Could we get to the point in the future
that, no matter where you choose to get your components from, they
all install into a predictable place?

You are right in one aspect - as a /suggestion/, this is NOT intended
to be a predicate for approval of this case.  In formal ARC-eese, I would
like to see:

     TCR - articulate this design pattern ("just like Perl...")
           into a formal BestPractice that can be published on the
           ARC Community pages (I will happily help with the logistics
           of making this part happen), and

     Advice: Push back these changes so that upstream component
           owners affected by this design pattern (not /just/ PHP)
           can take advantage of this best practice.

   -John


David.Comay at Sun.COM wrote:
> However, it's not recommended that they install their versions into
> /usr/php5 or /usr/perl5 since those are OpenSolaris directories.
> Effectively unbundled software should be installed by users in some
> other place in the file system such as /opt.

Why?  These components /ARE/ effectively unbundled.   We are not
really adding any value to this stuff as it passes thru; it is the
packaging and design pattern is what is important.  While we all
wish to make them part of the default install for all the OpenSolaris
distros, these components are certainly not things for which we (the
OpenSolaris community) are the primary content drivers or owners.

Your argument makes sense for a distro - Sun probably does not wish
to have its customers randomly update its Solaris distro, but we are
talking here about OpenSolaris, where there is a need to be able to
refresh and redeliver these components as the upstream source evolves;
how can developers and users  who need a later version take advantage
of this work?.

   -John



Reply via email to