C amalgamation for different branches?
(1) By tlaverdure on 2022-09-02 19:51:08 [link] [source]
Is there an easy way to download the different branches of SQLite as releases become available? I've been able to download a copy of code from the main branch here:
https://www.sqlite.org/download.html
However, I'm also interested in trying some of the different branches to see if they fit my use case.
Looking at the latest release:
sqlite-autoconf-3390200.tar.gz
Would it be possible to allow the branch name be appended to the file name of a release to download that version of a branch?
sqlite-autoconf-3390200-begin-concurrent.tar.gz
sqlite-autoconf-3390200-wal2.tar.gz
Thanks!
(2.1) By Stephan Beal (stephan) on 2022-09-02 20:02:54 edited from 2.0 in reply to 1 [source]
Would it be possible to allow the branch name be appended to the file name of a release to download that version of a branch?
The most feature-comllete way is to clone the source repository and learn a few fossil commands, starting with:
fossil clone https://sqlite.org/src sqlite3.fossil
But it can also be done without fossil. See:
https://sqlite.org/src/help?cmd=/tar
Edit: that won't download an amalgamation build. Building the amalgamation requires access to the full sources. The amalgamation is not stored in SCM.
(3) By tlaverdure on 2022-09-02 20:18:48 in reply to 1 [link] [source]
Guess for now I'll just be download the full source and build from there:
https://www.sqlite.org/src/tarball/sqlite.tar.gz?r=begin-concurrent
The instructions are found in the root of the project, but were kind of confusing at first glance:
For other check-ins, substitute an appropriate branch name or tag or hash prefix in place of "release" in the URLs of the previous bullet. Or browse the timeline to locate the check-in desired, click on its information page link, then click on the "Tarball" or "ZIP Archive" links on the information page.
(4) By Stephan Beal (stephan) on 2022-09-03 10:06:13 in reply to 3 [link] [source]
Guess for now I'll just be download the full source and build from there:
"For now" is not the extent of it: branches come and go without warning and none but the trunk are "supported deliverables" of the project. There will never be automated builds of the amalgamation for arbitrary branches (with the obligatory caveat of "never say never"). Creating the amalgamation, or working with any non-release builds, requires having and configuring the full source tree.
(5) By tlaverdure on 2022-09-03 13:11:32 in reply to 4 [link] [source]
Good point. Thanks for the feedback.