David.Comay at Sun.COM wrote:
>> o We (or someone) needs to be able to easily and quickly create a new
>> packaged version of the component for OpenSolaris any time the upstream
>> community releases new versions (so that this second class of user is
>> satisfied), and
>
> I could understand a desire to do this but that's not the intent of
> this project. The intent is to integrate a stable (to some extent)
Understood and agreed
> By providing a directory hierarchy like Perl, I believe it can be
> leveraged in the future *if* we decide to do that future release. It
Great - this is why I was pushing the BestPractice - lets design this
so that we /can/ do that in the future. As I mentioned to Gina a few
minutes ago, I'm relatively content with how this is playing out, and
have no desire to derail or further impede this case.
>> o We need to allow our users/admins to select which version(s) that they
>> wish to install and/or use (so the more conservative ones are not left
>> in the dust).
>
> That might be a nice thing to offer but seems outside this case. We
> don't currently do that for any of our other components except perhaps
> for their choice of shell or their window system.
In this case it is clear that users place specific value on the particular
version being used, and that, once installed, are reluctant to upgrade/change.
Forcing them to change will either alienate them or keep them from upgrading,
neither of which seems desirable. I think we have to acknowledge that including
externally created components like AMPP is significantly different from CDE,
GNOME and ksh93.
> The proposed directory structure though does allow different versions
> to exist...
... and, as I said, I'm happy. Thanks for working to make this happen!
-John
