John,
> This set of cases is explicitly setting precedent WRT how
> to install FOSS components that require the ability to have
> multiple co-installed versions.
Actually, I thought this case was following the precdent that Perl
introduced in PSARC 1999/192. In that case, a directory structure was
introduced along the same exact lines as what was proposed here.
/usr/perl5/[version]/<subdirectory>
> /This/ discussion is happening under the php5 topic, but is
> applicable to the larger SAMPP proposal and all of its
> sub-components.
Isn't this true then of any sort of externally derived open-source? I
guess I'm having diffculty seeing what this applies to the proposed
SAPP/AMP stack and not the general case of having multiple versions of
various open source components.
> The point of my previous messages was simply that
>
> Given that the policy (whatever it is) will be set by this
> review, the action item to write up that policy and publish it
> as a best practice can safely be decoupled from the tasks
> the project team needs to do /this week/.
I think it would be fantastic to publish a policy and best practice on
how to incorporate externally derived open source into OpenSolaris and
I'm more than happy to help create such a document. But I don't see
why it is this case's responsibility to write up this policy as part of
the case.
dsc
