Thus said Richard Hipp on Thu, 02 Jan 2014 11:32:22 -0500: > I hate having to support --disable-internal-sqlite, and I hate having > to add silly work-arounds in the code to accommodate distributions > trying to use an older SQLite with a newer Fossil. This impedes > progress and introduces bugs.
I see no reason to accomodate older SQLite libraries in Fossil code workarounds. Shouldn't we just update the following lines of configure detection to have a new requirement of SQLite >= 3.8.2 and be done with it; thus also avoiding the workarounds, bugs and furthering progress? http://www.fossil-scm.org/fossil/artifact/34dd270c8b3c7e4f3de26562f9344f90055620fc?ln=51,52 What is the worst that can come of it? That some OS vendors might lag behind in Fossil versions that they distribute? As for why I used --disable-internal-sqlite in the first place... I did it because I didn't know better (and partly because for whatever reason, modifying a single file requires a recompile of all targets). :-) I still think that Fossil should warn that the system library is not capable of supporting Fossil when the option is used. Clearly it would be best if the option didn't exist, but it does exist. Thanks, Andy -- TAI64 timestamp: 4000000052c762c8 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
