| 1 |
On Tue, Nov 17, 2009 at 1:53 PM, Dale <rdalek1967@×××××.com> wrote: |
| 2 |
|
| 3 |
> Hi, |
| 4 |
> |
| 5 |
> KDE 4 was having "issues" with sqlite not working correctly. After reading |
| 6 |
> about and people telling me that mySql works better, I installed mySql. Its |
| 7 |
> big and all but at least it works. Anyway, I changed the USE flags and have |
| 8 |
> -sqlite in my USE flag line. I want to get rid of sqlite on here. I see no |
| 9 |
> need for me to have two of these installed at the same time. Here is what |
| 10 |
> depends on sqlite: |
| 11 |
> |
| 12 |
> root@smoker / # equery depends sqlite |
| 13 |
> [ Searching for packages depending on sqlite... ] |
| 14 |
> app-pda/libopensync-0.22 (>=dev-db/sqlite-3) |
| 15 |
> app-portage/eix-0.17.0 (sqlite? >=dev-db/sqlite-3) |
| 16 |
> dev-lang/python-2.6.2-r1 (!build & sqlite? >=dev-db/sqlite-3) |
| 17 |
> dev-lang/python-3.1.1-r1 (!build & sqlite? >=dev-db/sqlite-3) |
| 18 |
> dev-libs/apr-util-1.3.9 (sqlite? dev-db/sqlite:0) |
| 19 |
> (sqlite3? dev-db/sqlite:3) |
| 20 |
> dev-libs/cyrus-sasl-2.1.23-r1 (sqlite? dev-db/sqlite) |
| 21 |
> dev-libs/nspr-4.8 (>=dev-db/sqlite-3.5) |
| 22 |
> dev-libs/nss-3.12.3-r1 (>=dev-db/sqlite-3.5) |
| 23 |
> dev-libs/redland-1.0.9-r1 (sqlite? =dev-db/sqlite-3*) |
| 24 |
> dev-util/subversion-1.6.5 (>=dev-db/sqlite-3.4[threadsafe]) |
| 25 |
> kde-base/kget-4.3.3 (sqlite? dev-db/sqlite:3) |
| 26 |
> kde-base/kopete-4.3.3 (statistics? dev-db/sqlite:3) |
| 27 |
> media-libs/libsndfile-1.0.20 (sqlite? >=dev-db/sqlite-3.2) |
| 28 |
> net-im/pidgin-2.6.3 (prediction? =dev-db/sqlite-3*) |
| 29 |
> net-libs/webkit-gtk-1.1.10 (>=dev-db/sqlite-3) |
| 30 |
> net-libs/xulrunner-1.9.1.4 (sqlite? >=dev-db/sqlite-3.6.16) |
| 31 |
> www-client/mozilla-firefox-3.5.4 (sqlite? >=dev-db/sqlite-3.6.10) |
| 32 |
> x11-libs/qt-sql-4.5.3 (sqlite? dev-db/sqlite:3) |
| 33 |
> root@smoker / # |
| 34 |
> |
| 35 |
> Those appear to be in the ebuild and MySql is not a option for replacement. |
| 36 |
> Is there a way? I have already emerged these with the -sqlite and +mysql |
| 37 |
> USE flag. I notice something about sqlite3 in one of the ebuilds. What is |
| 38 |
> that? |
| 39 |
> |
| 40 |
> Ideas? |
| 41 |
> |
| 42 |
> |
| 43 |
Unfortunately, MySQL is not a drop-in replacement for sqlite - the |
| 44 |
programming APIs and DB capabilities are sufficiently different to not be |
| 45 |
able to "just replace one with the other" - the developer has to add in |
| 46 |
extra code/abstraction in order to be able to support one or the other or |
| 47 |
both. |
| 48 |
|
| 49 |
As far as sqlite vs. sqlite3, the more recent major version of sqlite |
| 50 |
(sqlite-3.*) broke backwards compatibility with <=sqlite-2.*, and has, once |
| 51 |
again, a different programming API and different DB capabilities - some |
| 52 |
packages might still only be able to use <sqlite-3, some might be able to |
| 53 |
use either (hence the sqlite vs. sqlite3 USE flags), and some might only be |
| 54 |
able to use >=sqlite-3.*. If you look at the package list above, you'll see |
| 55 |
that pretty much all of them require some version of sqlite-3, and the only |
| 56 |
one that can optionally do either has the USE flag split out into sqlite |
| 57 |
(for the <sqlite-3 version) and sqlite-3 - I would guess w/o looking at the |
| 58 |
ebuild that sqlite-3 takes precedence if both are set, as it's a better and |
| 59 |
more robust DB system than the older sqlite. |
| 60 |
|
| 61 |
HTH- |
| 62 |
|
| 63 |
-James |
| 64 |
|
| 65 |
|
| 66 |
|
| 67 |
> Dale |
| 68 |
> |
| 69 |
> :-) :-) |
| 70 |
> |
Archives