Hi, Richard Levitte wrote: > In the same vein, the code to display the versions of SQLite, Botan > and so on might be misleading in a shared library environment. Maybe > it should display both the versions it was compiled against and the > versions it's running against (if that's possible to find out, which > isn't always a given).
I've done that for SQLite and botan now. The mtn version --full output now looks like (as an example): monotone 0.41 (base revision: 35c9a1b5661fa713059728bec11204df5d0fe7c4) Running on : Linux 2.6.27-rc6-markus1 #4 SMP Thu Sep 18 13:30:24 CEST 2008 x86_64 C++ compiler : GNU C++ version 4.3.2 C++ standard library: GNU libstdc++ version 20080905 Boost version : 1_34_1 SQLite version : 3.5.9 (compiled against 3.3.8) Lua version : Lua 5.1.3 PCRE version : 7.8 Botan version : 1.6.3 (compiled against 1.6.3) Changes since base revision: format_version "1" new_manifest [84b53d2311043f42fcd55b15e9b548b3b9fb7e48] old_revision [67a5c30e1c38753ca92bda29120299e4872ac34b] Generated from data cached in the distribution; further changes may have been made. The cost for being independent of the actual SQLite library is having to use sqlite3_prepare() instead of sqlite3_prepare_v2(), which exists only since 3.3.14. However, as that's just 1.5 years old and because 3.3.8 is in etch, I'm trying to still support those versions. Regards Markus Wanner _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel