[u]Quick Notes[/u] The following open issues (detailed in http://www.opensolaris.org/jive/thread.jspa?messageID=153703) were discussed: OPEN: Support for concurrent versions on disk OPEN: libexec location vs. apxs
[b]OPEN Support for concurrent versions on disk[/b] Given the compatibility guidelines from the upstream community, it's agreed that we should support having the provision to carry at most one one additional version for apache2 (i.e. provision for a 2.4.x version concurrently with 2.2.x). It was also felt there would be no reason to have the complexity of multiple micro versions within a minor version (i.e. a future 2.2.8 release should replace 2.2.6). While the upstream community seem to provide the binary compatibility acorss such micro version releases, this project team will test the next micro release and participate in the upstream community to ensure such a binary compatibility is preserved. [b]OPEN: libexec location vs. apxs[/b] I believe the consensus is to modify apxs -i to write elsewhere, in a location suitable for per-user/per-zone write access, such as /var/apache2 (the default shared libraries (mod_* binaries) in /usr/apache2/libexec/). -- Please make any corrections if I don't have this captured right. [There were a number of comments/issues discussed e.g. the need for making it a real simpel for a developer to manage the default stack, as opposed to potentially complex scenario of having multiple versions to go through.] This message posted from opensolaris.org
