Joseph Kowalski wrote:
> 
> I'm skipping the nested inclusion method in replying to David for the 
> moment. I somehow think there is a disconnect which needs to be resolved 
> first.
> 
>  From David's mail, I'm led to believe that only a small number of PHP 
> versions will be on the system.  Initially, only PHP5, perhaps joined by 
> PHP4 (or 6) in the future.  As I said in other mail, I suspect a 
> workable support plan can be worked for this model. (If this works out 
> to be the case, I would like to see a paragraph or two about it in the 
> materials rather than "like Perl".  We need to write this down sometime 
> to avoid the "Ground Hog Day" effect.)
> 
> However, if this is that case, I don't understand the benefit or use of 
> the [version] directory level *under* PHP5:
> 
>     2.3.    Directory Naming and Structure
>     
>     The proposed directory layout for PHP5 is:
>         /usr/php5/
>             bin -> [version]/bin
>             doc -> [version]/doc
> 
>        ....
> 
>     /usr/php5/[version]/bin/php    Uncommitted    Executable location
>     /usr/php5/bin/php        Uncommitted    Symbolic link
>     /usr/bin/php            Uncommitted    Symbolic link
> 
> This seems only designed to allow support for multiple, co-resident 
> versions of PHP5.
> 
> The only way I can reconcile David's statement with this structure is 
> that Sun Solaris would only ever deliver one version of PHP5 and the 
> [version] field's only purpose is to give a structure to allow SA's to 
> download other versions directly from the community. The OpenSolaris 
> reference build would also be so resticted. Other OpenSolaris distros 
> could do what they want, but would be encouraged to do the same.
> 
> What is the model here?

This is the directory structure currently in existence with Perl5:

/usr/perl5/5.6.1/
/usr/perl5/5.8.4/

[ ... ]

/usr/perl5/bin -> /usr/perl5/5.8.4/bin
/usr/perl5/man -> /usr/perl5/5.8.4/man

/usr/bin/perl -> /usr/perl5/5.8.4/bin/perl

The PHP5 model is a clone.

--Stefan

-- 
Stefan Teleman
Sun Microsystems, Inc.
Stefan.Teleman at Sun.COM


Reply via email to