Hello All, > > > Obtaining An Explicit License To Use SQLite > > Even though SQLite is in the public domain and does not require a > license, some users want to obtain a license anyway. Some reasons for > obtaining a license include: > > * You are using SQLite in a jurisdiction that does not recognize > the public domain. > * You are using SQLite in a jurisdiction that does not recognize > the right of an author to dedicate their work to the public domain. > * You want to hold a tangible legal document as evidence that you > have the legal right to use and distribute SQLite. > * Your legal department tells you that you have to purchase a > license. > > If you feel like you really have to purchase a license for SQLite, > Hwaci <http://www.hwaci.com/>, the company that employs the architect > and principal developers of SQLite, will sell you one > <http://www.hwaci.com/cgi-bin/license-step1>. > Could somebody explain to me this paragraph?
I also need clarification on the below quote : > using SQLite in a jurisdiction that does not recognize the public domain. Thanks & Regards, Sen On 4/26/2010 10:39 AM, Simon Slavin wrote: > On 26 Apr 2010, at 5:43am, Navaneeth Sen B wrote: > > >> I just have some doubts on the licensing issues of SQLite. >> >> 1. Being open-source, is my company liable to post back >> changes/modifications to >> SQLite? What are the licensing terms& conditions? >> 2. As our present development is on a Linux variant, are there any >> present >> feature/functionality that need to be posted back? >> > The operative page for licensing terms and conditions is > > <http://www.sqlite.org/copyright.html> > > Have someone read and understand that page. SQLite is Public Domain. That > basically means you can do anything you like with SQLite apart from pretend > you invented it or stop other people from using it. However, I am not a > lawyer in India and if you are unsure about your legal situation you should > consult a qualified lawyer. > > Your company can modify SQLite however it likes for its own purposes. Doing > this does not mean that your company 'owns' SQLite in any way: the licensing > terms remain the same. Your company is not required to reveal what it has > changed or how it has done so. It can if it wants, but there's no > requirement to do so. If it does want to contribute changes back to SQLite, > these changes must be released as Public Domain, or they will not be > incorporated into future versions of SQLite. > > There is nothing special about compiling SQLite for use with any version of > Linux. The facilities for all operating systems are equivalent, or as close > as they reasonably can be given how each operating system works. > > Simon. > _______________________________________________ > sqlite-users mailing list > [email protected] > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > > _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
