Re: [sqlite] understanding the logic of licensing various parts of the sqlite family
On Thu, Jun 24, 2010 at 3:19 PM, Richard Hipp wrote: > On Thu, Jun 24, 2010 at 4:15 PM, P Kishor wrote: > >> >> Right then. That explains #3 above. Are you saying that #5 is >> available for a fee? And, is there a description of #5 and how it >> differs from #4? Not that I will understand the differences, nor will >> I ever need it. I just didn't realize #5 (the "Compleat Tests of >> SQLite") was available. >> >> Thanks for the answer. >> > > http://www.sqlite.org/th3.html > Lovely. Thorough, clear and effective. Like sqlite3 itself. > -- > - > D. Richard Hipp > d...@sqlite.org > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu --- Assertions are politics; backing up assertions with evidence is science === ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] understanding the logic of licensing various parts of the sqlite family
On Thu, Jun 24, 2010 at 4:15 PM, P Kishor wrote: > > Right then. That explains #3 above. Are you saying that #5 is > available for a fee? And, is there a description of #5 and how it > differs from #4? Not that I will understand the differences, nor will > I ever need it. I just didn't realize #5 (the "Compleat Tests of > SQLite") was available. > > Thanks for the answer. > http://www.sqlite.org/th3.html -- - D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] understanding the logic of licensing various parts of the sqlite family
On Thu, Jun 24, 2010 at 3:04 PM, Richard Hipp wrote: > On Thu, Jun 24, 2010 at 3:58 PM, P Kishor wrote: > >> I am simply curious, and want to expand my knowledge of this -- >> >> 1. sqlite3 code is in public domain. >> 2. sqlite mark is trademarked. >> 3. sqlite3 encryption extension is licensed and for a fee, and comes >> with a contract to not distribute it further. >> 4. sqlite code tests are available as long as they are in the >> non-amalgamated source tree. >> 5. other "more complete" code tests are proprietary and closed source. >> >> >> I am curious about the reason for #5 being the way it is. >> > > No mystery there: Sales of licenses for the non-free parts of SQLite is > (one way) that we make money in order to pay people to work full-time on the > free parts. > > Right then. That explains #3 above. Are you saying that #5 is available for a fee? And, is there a description of #5 and how it differs from #4? Not that I will understand the differences, nor will I ever need it. I just didn't realize #5 (the "Compleat Tests of SQLite") was available. Thanks for the answer. > > -- > - > D. Richard Hipp > d...@sqlite.org > ___ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu --- Assertions are politics; backing up assertions with evidence is science === ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
Re: [sqlite] understanding the logic of licensing various parts of the sqlite family
On Thu, Jun 24, 2010 at 3:58 PM, P Kishor wrote: > I am simply curious, and want to expand my knowledge of this -- > > 1. sqlite3 code is in public domain. > 2. sqlite mark is trademarked. > 3. sqlite3 encryption extension is licensed and for a fee, and comes > with a contract to not distribute it further. > 4. sqlite code tests are available as long as they are in the > non-amalgamated source tree. > 5. other "more complete" code tests are proprietary and closed source. > > > I am curious about the reason for #5 being the way it is. > No mystery there: Sales of licenses for the non-free parts of SQLite is (one way) that we make money in order to pay people to work full-time on the free parts. -- - D. Richard Hipp d...@sqlite.org ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
[sqlite] understanding the logic of licensing various parts of the sqlite family
I am simply curious, and want to expand my knowledge of this -- 1. sqlite3 code is in public domain. 2. sqlite mark is trademarked. 3. sqlite3 encryption extension is licensed and for a fee, and comes with a contract to not distribute it further. 4. sqlite code tests are available as long as they are in the non-amalgamated source tree. 5. other "more complete" code tests are proprietary and closed source. I am curious about the reason for #5 being the way it is. Simply curious, not judgmental. Fwiw, I never 'make test' sqlite... I just download and install it. Same with the version that comes with DBD::SQLite other than any tests that the Perl installation might do. -- Puneet Kishor http://www.punkish.org Carbon Model http://carbonmodel.org Charter Member, Open Source Geospatial Foundation http://www.osgeo.org Science Commons Fellow, http://sciencecommons.org/about/whoweare/kishor Nelson Institute, UW-Madison http://www.nelson.wisc.edu --- Assertions are politics; backing up assertions with evidence is science === ___ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
