After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 351133 - If we have sqlite3, user is forced to use
If we have sqlite3, user is forced to use
Status: RESOLVED FIXED
Product: beagle
Classification: Other
Component: General
unspecified
Other Linux
: Normal minor
: ---
Assigned To: Kevin Kubasik
Beagle Bugs
Depends on:
Blocks:
 
 
Reported: 2006-08-13 05:54 UTC by Kevin Kubasik
Modified: 2006-09-26 16:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Attachments
Allows --enable-sqlite2 configure time option (519 bytes, patch)
2006-08-13 05:56 UTC, Kevin Kubasik
needs-work Details | Review
Update (1.06 KB, patch)
2006-09-01 01:08 UTC, Kevin Kubasik
needs-work Details | Review
Update Sqlite Version Selection (2.32 KB, patch)
2006-09-22 00:45 UTC, Kevin Kubasik
committed Details | Review

Description Kevin Kubasik 2006-08-13 05:54:42 UTC
While this seems trivial at first, if someone (like me) already has a large f-spot db with sqlite2, then this can be a big deal.
Comment 1 Kevin Kubasik 2006-08-13 05:56:12 UTC
Created attachment 70804 [details] [review]
Allows --enable-sqlite2 configure time option

./configure --enable-sqlite2, and viola! the user has forced sqlite2 over sqlite3.
Comment 2 Joe Shaw 2006-08-14 18:24:48 UTC
Right idea, but it needs to fit in better with the existing sqlite checks.  

Consider this scenario: if you don't have sqlite2 installed but do have sqlite3 and pass in --enable-sqlite2, configure won't error out even though you don't have sqlite2.  Beagle will build fine but actually crash *at runtime* because don't have it.  (And we DllImport it, so there's not even a build-time error.)

I'd like to see this patch reworked so that if you pass in --enable-sqlite2, the checks for sqlite2 are strict and fatal and sqlite3 is not checked.  Moreover, I'd like to see an --enable-sqlite3 which does the exact same thing for sqlite3.
Comment 3 Kevin Kubasik 2006-09-01 01:08:13 UTC
Created attachment 72001 [details] [review]
Update

Hey, this should do the trick, I can't uninstall the sqlite libs to check, so in a perfect world, could someone check that? But it does allow us to force either 2 or 3
Comment 4 Kevin Kubasik 2006-09-02 23:14:01 UTC
Any thoughts?
Comment 5 Joe Shaw 2006-09-05 19:28:38 UTC
This doesn't work because it does nothing if the check fails; it needs to error out.  It'd also be good to do those checks before the automatic detection and only do the automatic detection if the version isn't set.
Comment 6 Kevin Kubasik 2006-09-22 00:45:23 UTC
Created attachment 73180 [details] [review]
Update Sqlite Version Selection

Ok, this should error out, and it checks for the commandline arguments first.
Comment 7 Joe Shaw 2006-09-26 15:54:09 UTC
Looks good
Comment 8 Kevin Kubasik 2006-09-26 16:11:43 UTC
Done and done.