>>
>> web/server/apache-22/plugin/apache-php5
>>
>> OR
>>
>> web/server/apache-22/plugin/apache-php52
> This makes more sense to me.
>>
>> Note that the mod_php5.so is delivered as a link to mod_php5.2.so
>> although the conf file is php5.2.conf. If we ever needed to support
>> two PHP releases, will Apache likely require different plugins to
>> support both?
> Though, we might, in future, deliver 2 versions, both of them are
> mutually exclusive . So, a user can have either apache-php52 or
> apache-php53 loaded but having both these php versions loaded in the
> same process doesn't make much sense (at least to me)
Just to be a contrarian...
When I wrote up some file layout thoughts way back when I suggested that
if the upstream project promises to be compatible across minor releases,
we should trust them until that trust is violated. This makes things a
lot simpler for end users who already consider Solaris/OpenSolaris odd
for having file layouts which are too-future proofed. I know it's not
OpenSolaris, but case in point:
ingenthr at andromeda$ ls /usr/perl5/5.8.4/bin/
a2p h2ph perlbug pl2pm podchecker splain
c2ph h2xs perlcc pod2html podselect xsubpp
cpan instmodsh perldoc pod2latex prove
dprofpp libnetcfg perlgcc pod2man psed
enc2xs perl perlivp pod2text pstruct
find2perl perl5.8.4 piconv pod2usage s2p
ingenthr at andromeda$ ls -l /usr/bin/perl
lrwxrwxrwx 1 root root 23 Jul 23 2006 /usr/bin/perl ->
../perl5/5.8.4/bin/perl
ingenthr at andromeda$ which cpan
no cpan in /usr/bin /usr/sbin
ingenthr at andromeda$ cat /etc/release
Solaris 10 6/06 s10x_u2wos_09a X86
It would be possible to use "php5" for now, and move to "php53" or
"php5.3" if there were something that were so incompatible with the old
"php5" that you wanted to support both concurrently.
Incidentally, what would happen if they suddenly decided to make the
next release version 10.0?
Regards,
- Matt
