On Wednesday 18 November 2009 00:22:08 Dale wrote: > > Some stuff uses sqlite for storage. If it works, leave it alone. Just > > because some parts of KDE <koff><koff> amarok <koff><koff> have issues > > with it doesn;t mean all of KDE has issues with it > > > > > > > > So basically I have to have it anyway? It's just one more thing to > update is why I want to gt rid of it. You have better things to worry about, trust me :-)
Like, why do you have to have redland and lucene around when a) redland sucks b) lucene sucks much less despite being java? Or XML parsers... why do you invariably have libxml and expat at the same time? For that matter, I'll bet you have 3 SLOTTED versions of db in addition to gdbm (all in addition to sqlite of course) Lets not even start with the scripting languages ... I often hear newbies complain about having bash, python, perl and ruby all at the same time. Can't the devs just stick to one language? See where I'm going with this? At <10M for two versions of sqlite, it's not worth worrying about and you don't have to pay any attention to updating it - portage and --depclean will sort you out just fine -- alan dot mckinnon at gmail dot com
