Hi!
I already answered that question very extensively, I think on this
list too (no only on disttributions@fd.o)
However, I dislike the cache approach very much and right now trying
other things which might solve the issue too, if upstream accepts my
suggestions.
Was really SQLite the problem? Which database are you using now?
Cheers,
Matthias
2012/6/5 Michael Schroeder
Hi, me again ;)
On Mon, Jun 04, 2012 at 01:36:51PM +0200, Matthias Klumpp wrote:
The database is in PK and therefore generic, it can be used by every other tool too.
Just a couple of words about storing package data into a big sqlite database: that's what opensuse-10.X did, and updating the database with new repository data was so slow that this led to the development of libsatsolver (now libsolv) used in newer opensuse versions. I really don't see why there's need for yet another database when the packagekit backends already maintain their own ones.
Cheers, Michael.
-- Michael Schroeder mls@suse.de SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
-- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org