I think URL like: .../tree?ci=trunk will fail without 3.8.2. Your best bet is to compile without --disable-internal-sqlite and just let Fossil use the built-in version of SQLite. That will definitely be the safest and best tested approach. If you use --disable-interal-sqlite, you never know when you might hit some case where Fossil is using a newer feature of SQLite that is not available in your library version, and which we forgot to warn you about.
On Mon, Jan 27, 2014 at 4:07 PM, James Turner <ja...@calminferno.net> wrote: > OpenBSD currently has SQLite 3.8.0.2 in it's tree. We are coming up to a > release lock and I don't imagine a newer version will be imported before > then. > > We are compiling Fossil with --disable-internal-sqlite in our ports > tree. Fossil compiles without error. I've also relaxed the SQLite > runtime version check to 3.8.0 and all make tests pass. I've been able > to fossil clone, fossil pull, fossil up and run fossil sqlite3 without > error. > > Does anyone see any problem with running Fossil 1.28 against SQLite > 3.8.0.2? I'd really like to see Fossil 1.28 make our 5.5 release. > > Thanks. > > -- > James Turner > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
