you don't have to do anything. SQLite is in public domain. You can cook with it, make castles with it, become a billionaire (although, if you do, remember to give some money to your favorite open source project), or roll pancakes with it.
If you make and modifications to SQLite AND if you want those modifications to be included in future versions of SQLite, then you have to -- 1. convince Richard that your mods are all that, and 2. put your mods in the same license as SQLite. Other than that, do what you wish with it. On 4/26/07, Pavan <[EMAIL PROTECTED]> wrote:
Hi, I have gone through this link http://www.sqlite.org/copyright.html and here are few more practical queries related to commercial usage:- 1. If i develop a wrapper module around sqlite(without taking explicit license) to store some private data in the db, should the wrapper module be made public ? 2. If i develop a wrapper module around sqlite(taking explicit license) to store some private data in the db, should the wrapper module be made public ? 3. If i take explicit license from hawci, will the license apply for subsequent upgrades of the sqlite ? 4. Anyother information which someone wants to share related to license. Thanks in advance, Pavan. -- '**************************************************************** Always finish stronger than you start *****************************************************************
-- Puneet Kishor http://punkish.eidesis.org/ Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/ Open Source Geospatial Foundation http://www.osgeo.org/education/ --------------------------------------------------------------------- collaborate, communicate, compete ===================================================================== ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
