I would like to suggest that the design pattern being hashed out here (i.e., how to have multiple versions of a component installed on a given system) be explicitly called out and approved as part of this set of cases as an ARC best practice.
Furthermore, I would like to see the build/config changes that support such a design pattern pushed back upstream to the various component owners such that anyone could download a newer version of the component, build it, and install it along side whatever existing versions were already there. In the best of all worlds, one would be able to exactly rebuild any of the existing versions as well, making it easy to confidently tweak/optimize the component for site specific needs. -John David.Comay at Sun.COM wrote: >> 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.) > > Yes, I think there will be a small number of PHP versions. But I don't > mean to imply that for a particular major version of PHP that there > will only be one. > > dsc > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc at opensolaris.org
