| [822] | 1 | SQLite Is Public Domain
|
|---|
| 2 |
|
|---|
| 3 | All of the code and documentation in SQLite has been dedicated to the public
|
|---|
| 4 | domain by the authors. All code authors, and representatives of the companies
|
|---|
| 5 | they work for, have signed affidavits dedicating their contributions to the
|
|---|
| 6 | public domain and originals of those signed affidavits are stored in a firesafe
|
|---|
| 7 | at the main offices of Hwaci. Anyone is free to copy, modify, publish, use,
|
|---|
| 8 | compile, sell, or distribute the original SQLite code, either in source code
|
|---|
| 9 | form or as a compiled binary, for any purpose, commercial or non-commercial,
|
|---|
| 10 | and by any means.
|
|---|
| 11 |
|
|---|
| 12 | The previous paragraph applies to the deliverable code and documentation in
|
|---|
| 13 | SQLite - those parts of the SQLite library that you actually bundle and ship
|
|---|
| 14 | with a larger application. Some scripts used as part of the build process (for
|
|---|
| 15 | example the "configure" scripts generated by autoconf) might fall under other
|
|---|
| 16 | open-source licenses. Nothing from these build scripts ever reaches the final
|
|---|
| 17 | deliverable SQLite library, however, and so the licenses associated with those
|
|---|
| 18 | scripts should not be a factor in assessing your rights to copy and use the
|
|---|
| 19 | SQLite library.
|
|---|
| 20 |
|
|---|
| 21 | All of the deliverable code in SQLite has been written from scratch. No code
|
|---|
| 22 | has been taken from other projects or from the open internet. Every line of
|
|---|
| 23 | code can be traced back to its original author, and all of those authors have
|
|---|
| 24 | public domain dedications on file. So the SQLite code base is clean and is
|
|---|
| 25 | uncontaminated with licensed code from other projects.
|
|---|
