On Mon, Feb 04, 2008 at 04:57:17PM +0000, Darren J Moffat wrote: > John Plocher wrote: > > > Contract or not, since your team is putting it into Solaris, you > > are already committed to work with them to help avoid problems > > on the upgrade. Changing Committed to Contracted Volatile doesn't > > actually change the amount and type of work that you already are > > going to need to perform... > > Speaking from experience with OpenSSL a Contracted interface has a > HIGHER burden on the supplier because they not only does the supplier > need to do the analysis on wither and when to upgrade they also need to > work with the contractees. It also brings in a management and ARC > member burden to sign all the new contracts. > > For something that does not have a stable ABI and API, like OpenSSL, it > might almost be worth it (I'm starting to doubt even that for OpenSSL > now though); however for something that is known to be very stable and > has explicit goals and past history in this area, like SQLite, Volatile > and thus ARC contracts are an added and unnecessary burden on consumers.
For OpenSSL the DLL hell considerations w.r.t. shipping multiple versions are serious enough, and DLL hell sufficiently likely, that it is reasonable that shipping multiple versions should give us pause. But even so, I tend to agree: just ship multiple versions. Nico --
