Documentation Source Text

Check-in [e538d8674b]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix the build-product name recipe at the bottom of the download page.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: e538d8674b57c5a805d3383f50e8afdeaf3bc1d8
User & Date: drh 2011-04-06 15:26:05.284
Context
2011-04-06
19:40
Fix a typo in the change log for 3.7.6. (check-in: 055d224c39 user: drh tags: trunk)
15:26
Fix the build-product name recipe at the bottom of the download page. (check-in: e538d8674b user: drh tags: trunk)
2011-04-05
22:22
Change the target release date for 3.7.6 to April 12. (check-in: 76d31b952b user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/download.in.
︙︙
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226


<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>sqlite3-</b>product<b>-</b>version<b>.zip</b>
<li> <b>sqlite3-</b>product<b>-</b>version<b>.tar.gz</b>
<li> <b>sqlite3-</b>product<b>-</b>os<b>-</b>cpu<b>-</b>version<b>.zip</b>
<li> <b>sqlite3-</b>product<b>-</b>date<b>.zip</b>
</ol>

<p>Templates (1) and (2) are used for source-code products.  Template (1) is
used for generic source-code products and templates (2) is used for source-code
products that are generally only useful on unix-like platforms.  Template (3)
is used for precompiled binaries products.  Template (4) is used for
unofficial pre-release "snapshots" of source code.








|
|
|
|








209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226


<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>

<p>Templates (1) and (2) are used for source-code products.  Template (1) is
used for generic source-code products and templates (2) is used for source-code
products that are generally only useful on unix-like platforms.  Template (3)
is used for precompiled binaries products.  Template (4) is used for
unofficial pre-release "snapshots" of source code.
︙︙