2014/1/8 Joseph R. Justice <jayare...@gmail.com>:
> Ummm... One other quite possibly naive question. I browsed in the Fossil
> sources briefly related to the tag you mentioned previously, the
> sqlite-min-to-3.7.17 tag, and if I'm understanding what I see correctly,
> you're doing the check for the minimum supported version based on if SQLite
> is reporting if specific capabilities are available, apparently on the
> grounds that if a given capability is available then that means the version
> of SQLite available is at least X.
The reason for this approach is as follows. Although the tag suggests
that "configure" checks for a minimal version of 3.7.17, in reality a check
is done for the availability of the sqlite3_strglob() function. I happen to
know that this function is introduced in SQLite 3.7.17. It might happen
that some OS maintainers discover an unacceptable security risk in
the sqlite3_strglob() function and decide to distribute a patched SQLite
3.7.17 in which the sqlite3_strglob() function is not exported to applications.
In that case an implicit version check in Fossil would succeed, but it
would be a lie. For this reason a real capability check is always better
than an implicit version check.
In other words, "require-sqlite_strglob" would have been a better
name for this Fossil tag.
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
