James Ausmus wrote:
On Tue, Nov 17, 2009 at 1:53 PM, Dale <rdalek1...@gmail.com
<mailto:rdalek1...@gmail.com>> wrote:
Hi,
KDE 4 was having "issues" with sqlite not working correctly.
After reading about and people telling me that mySql works
better, I installed mySql. Its big and all but at least it works.
Anyway, I changed the USE flags and have -sqlite in my USE flag
line. I want to get rid of sqlite on here. I see no need for me
to have two of these installed at the same time. Here is what
depends on sqlite:
r...@smoker / # equery depends sqlite
[ Searching for packages depending on sqlite... ]
app-pda/libopensync-0.22 (>=dev-db/sqlite-3)
app-portage/eix-0.17.0 (sqlite? >=dev-db/sqlite-3)
dev-lang/python-2.6.2-r1 (!build & sqlite? >=dev-db/sqlite-3)
dev-lang/python-3.1.1-r1 (!build & sqlite? >=dev-db/sqlite-3)
dev-libs/apr-util-1.3.9 (sqlite? dev-db/sqlite:0)
(sqlite3? dev-db/sqlite:3)
dev-libs/cyrus-sasl-2.1.23-r1 (sqlite? dev-db/sqlite)
dev-libs/nspr-4.8 (>=dev-db/sqlite-3.5)
dev-libs/nss-3.12.3-r1 (>=dev-db/sqlite-3.5)
dev-libs/redland-1.0.9-r1 (sqlite? =dev-db/sqlite-3*)
dev-util/subversion-1.6.5 (>=dev-db/sqlite-3.4[threadsafe])
kde-base/kget-4.3.3 (sqlite? dev-db/sqlite:3)
kde-base/kopete-4.3.3 (statistics? dev-db/sqlite:3)
media-libs/libsndfile-1.0.20 (sqlite? >=dev-db/sqlite-3.2)
net-im/pidgin-2.6.3 (prediction? =dev-db/sqlite-3*)
net-libs/webkit-gtk-1.1.10 (>=dev-db/sqlite-3)
net-libs/xulrunner-1.9.1.4 (sqlite? >=dev-db/sqlite-3.6.16)
www-client/mozilla-firefox-3.5.4 (sqlite? >=dev-db/sqlite-3.6.10)
x11-libs/qt-sql-4.5.3 (sqlite? dev-db/sqlite:3)
r...@smoker / #
Those appear to be in the ebuild and MySql is not a option for
replacement. Is there a way? I have already emerged these with
the -sqlite and +mysql USE flag. I notice something about sqlite3
in one of the ebuilds. What is that?
Ideas?
Unfortunately, MySQL is not a drop-in replacement for sqlite - the
programming APIs and DB capabilities are sufficiently different to not
be able to "just replace one with the other" - the developer has to
add in extra code/abstraction in order to be able to support one or
the other or both.
As far as sqlite vs. sqlite3, the more recent major version of sqlite
(sqlite-3.*) broke backwards compatibility with <=sqlite-2.*, and has,
once again, a different programming API and different DB capabilities
- some packages might still only be able to use <sqlite-3, some might
be able to use either (hence the sqlite vs. sqlite3 USE flags), and
some might only be able to use >=sqlite-3.*. If you look at the
package list above, you'll see that pretty much all of them require
some version of sqlite-3, and the only one that can optionally do
either has the USE flag split out into sqlite (for the <sqlite-3
version) and sqlite-3 - I would guess w/o looking at the ebuild that
sqlite-3 takes precedence if both are set, as it's a better and more
robust DB system than the older sqlite.
HTH-
-James
So they do the same thing but in different ways. Hmmm. Oh well.
Dale
:-) :-)
