Re: [fossil-users] Fossil 1.28 and SQLite 3.8.0.2
2014-01-28 James Turner: Thanks for the clarification guys. I'm thinking it's probably safe then to use 1.28 with our 3.8.0.2 version of SQLite. I'll get our in-tree version of SQLite upgraded to the latest after the unlock. Thanks for your feedback. It is highly appreciated! Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil 1.28 and SQLite 3.8.0.2
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
Re: [fossil-users] Fossil 1.28 and SQLite 3.8.0.2
On Mon, Jan 27, 2014 at 5:54 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2014-01-27 Richard Hipp d...@sqlite.org: I think URL like:.../tree?ci=trunk will fail without 3.8.2. This is the url which uses WITHOUT ROWID in trunk, but thanks to the SQLite version check it doesn't depend on it (yet) in Fossil 1.28. Yes, you are correct. I looked only on trunk... FWIW, Fossil 1.29 will very definitely require SQLite 3.8.3 or later in as much as it uses common table expressions to help generate the timeline now. -- 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
Re: [fossil-users] Fossil 1.28 and SQLite 3.8.0.2
2014-01-28 Richard Hipp d...@sqlite.org: FWIW, Fossil 1.29 will very definitely require SQLite 3.8.3 or later in as much as it uses common table expressions to help generate the timeline now. Yes, and I'm looking forward to that! By the time that Fossil 1.29 will be released, SQLite 3.8.3 will be several months (4) old. For Fossil 1.28, requiring SQLite 3.8.2 (dec. 2013) just was a little bit too early. But since changing the initial SQLite version check is easy, it's not really a problem. Actually, I expected this kind of question to arrive ;-) Regards, Jan Nijtmans ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil 1.28 and SQLite 3.8.0.2
On Mon, Jan 27, 2014 at 06:01:42PM -0500, Richard Hipp wrote: On Mon, Jan 27, 2014 at 5:54 PM, Jan Nijtmans jan.nijtm...@gmail.comwrote: 2014-01-27 Richard Hipp d...@sqlite.org: I think URL like:.../tree?ci=trunk will fail without 3.8.2. This is the url which uses WITHOUT ROWID in trunk, but thanks to the SQLite version check it doesn't depend on it (yet) in Fossil 1.28. Yes, you are correct. I looked only on trunk... FWIW, Fossil 1.29 will very definitely require SQLite 3.8.3 or later in as much as it uses common table expressions to help generate the timeline now. -- D. Richard Hipp d...@sqlite.org Thanks for the clarification guys. I'm thinking it's probably safe then to use 1.28 with our 3.8.0.2 version of SQLite. I'll get our in-tree version of SQLite upgraded to the latest after the unlock. -- James Turner ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
