Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Further tweaks to the look of the Download page. |
|---|---|
| Timelines: | family | ancestors | descendants | both | 3.7.17 |
| Files: | files | file ages | folders |
| SHA1: | c90897b38c784f0bd6be56e165244738 |
| User & Date: | drh 2013-07-19 20:41:26 |
Context
|
2013-07-23
| ||
| 13:45 | Add a missing "not" to the text in the download page. check-in: 53bc857d09 user: drh tags: 3.7.17 | |
|
2013-07-19
| ||
| 20:41 | Further tweaks to the look of the Download page. check-in: c90897b38c user: drh tags: 3.7.17 | |
| 20:22 | Put a yellow background on the prerelease snapshots on the download page. check-in: c032a10b8b user: drh tags: 3.7.17 | |
Changes
Changes to pages/download.in.
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
...
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
|
<u>not</u> recommended. Use one of the amalgamation packages above
unless you have a compelling reason not to.
}
</tcl>
</table>
<tcl>hd_fragment encoding {build product names}</tcl>
<h3>Build Product Names</h3>
<p>Beginning with SQLite [version 3.7.4], the names of the build products
have changed to be more consistent. (Prior to version 3.7.4, the
names of build products were seemingly random.) Build products are named
using one of the following templates:
<ol>
<li> <b>sqlite-</b>product<b>-</b>version<b>.zip</b>
<li> <b>sqlite-</b>product<b>-</b>version<b>.tar.gz</b>
<li> <b>sqlite-</b>product<b>-</b>os<b>-</b>cpu<b>-</b>version<b>.zip</b>
<li> <b>sqlite-</b>product<b>-</b>date<b>.zip</b>
</ol>
................................................................................
filename encoding is 3XXYY00. For branch version 3.X.Y.Z, the encoding is
3XXYYZZ.
<p>The <i>date</i> in template (4) is of the form: YYYYMMDDHHMM
<a name="cvs"></a>
<a name="fossil"></a>
<h3>Canonical Source Code</h3>
<p>
The canonical SQLite source code is maintained in three self-synchronizing
[http://www.fossil-scm.org/ | Fossil] repositories that are
available for anonymous read-only access. Anyone can
view the repository contents and download historical versions
of individual files or ZIP archives of historical check-ins.</p>
<p>Note that a unix-like development environment, including a recent
version of <a href="http://www.tcl.tk/">Tcl</a>, is required in order to
build from the canonical sources.</p>
<blockquote>
<a href="http://www.sqlite.org/cgi/src">http://www.sqlite.org/cgi/src</a> (Dallas)<br>
<a href="http://www2.sqlite.org/cgi/src">http://www2.sqlite.org/cgi/src</a> (Newark)<br>
<a href="http://www3.sqlite.org/cgi/src">http://www3.sqlite.org/cgi/src</a> (Fremont)<br>
</blockquote>
|
>
|
<
<
|
|
|
>
|
>
|
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
...
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
|
<u>not</u> recommended. Use one of the amalgamation packages above unless you have a compelling reason not to. } </tcl> </table> <hr> <tcl>hd_fragment encoding {build product names}</tcl> <h3>Build Product Names</h3> <p> Build products are named using one of the following templates: <ol> <li> <b>sqlite-</b>product<b>-</b>version<b>.zip</b> <li> <b>sqlite-</b>product<b>-</b>version<b>.tar.gz</b> <li> <b>sqlite-</b>product<b>-</b>os<b>-</b>cpu<b>-</b>version<b>.zip</b> <li> <b>sqlite-</b>product<b>-</b>date<b>.zip</b> </ol> ................................................................................ filename encoding is 3XXYY00. For branch version 3.X.Y.Z, the encoding is 3XXYYZZ. <p>The <i>date</i> in template (4) is of the form: YYYYMMDDHHMM <a name="cvs"></a> <a name="fossil"></a> <h3>Source Code Repositories</h3> <p> The SQLite source code is maintained in three geographically-dispersed self-synchronizing [http://www.fossil-scm.org/ | Fossil] repositories that are available for anonymous read-only access. Anyone can view the repository contents and download historical versions of individual files or ZIP archives of historical check-ins.</p> <p>Note that a unix-like development environment, including a recent version of <a href="http://www.tcl.tk/">Tcl</a>, is required in order to build from the repository sources. The [amalgamation] source code files (the "sqlite3.c" and "sqlite3.h" files) are contained in the repository.</p> <blockquote> <a href="http://www.sqlite.org/cgi/src">http://www.sqlite.org/cgi/src</a> (Dallas)<br> <a href="http://www2.sqlite.org/cgi/src">http://www2.sqlite.org/cgi/src</a> (Newark)<br> <a href="http://www3.sqlite.org/cgi/src">http://www3.sqlite.org/cgi/src</a> (Fremont)<br> </blockquote> |