Mike Frysinger wrote: > On Friday 14 September 2007, Hanno Böck wrote: > >> I noticed that the sqlite/sqlite3-useflags have no consistent meaning in >> the tree. >> >> E.g. >> - apr-util uses sqlite for sqlite-2.x support and sqlite3 for sqlite-3.x >> support >> - eix uses sqlite for sqlite-3.x support >> Just the first examples I found, you can find countless for both of them in >> the tree. >> >> We should imho decide if >> a) sqlite means sqlite-2.x and sqlite3 means sqlite-3.x. >> b) sqlite means enable sqlite-support always and sqlite+sqlite3 means if >> both are available use sqlite-3.x instead of 2.x. >> >> I don't care which one (or a completely different one), but I think it >> should be made clear. At least I think the current behaviour in the tree >> doesn't really make sense. >> > > how about 'sqlite' means you want sqlite irregardless of version ... then > sqlite-2 either gets punted from apr-util or it gets a local USE > flag 'sqlite-old' for older cruft > -mike > I agree with this. I'd take this a step further, using old cruft isn't a choice anymore. If an app supports sqlite2 and sqlite3, we'll have a USE=sqlite that'll enable sqlite3... sqlite2 just isn't an option anymore. The conversion process is very simple...
Step 1) mv mydatabase.db mydatabase.db-old Step 2) sqlite mydatabase.db-old .dump | sqlite3 mydatabase.db Step 3) Profit! I'm willing to start making this change asap in the tree. Since sqlite2 and sqlite3 are SLOTED, people won't lose their sqlite2 binary and will be able to make the conversion. I'll even add an ewarn for people to make sure to update their databases to sqlite3. Also, qt already uses it's own internal sqlite2 library and doesn't use the system library so that won't be a problem. -- [EMAIL PROTECTED] mailing list
