On Tue, 28 May 2013 20:42:13 +0300
Alek Paunov <alex(a)declera.com> wrote:
So, it seems that yum already have the "filelists on demand"
optimization implemented. Why you are asking for removing a feature,
which do not make the things worse ... ?
I'm not.
But when you download the filelists - it is A LOT of data.
I'd rather not have filedeps so it doesn't get pulled in for other
things in depsolving.
I have a few questions:
* What is the reasoning behind the splitting of the database across
many .sqlite files?
many? it's 3 afaik. primary, filelists, other.
how do you mean 'many?
* Why the sql schema is so denormalized (IMO, leads to both
bandwidth and disk overspending without speed benefits)?. For
example: Why provides and requires tables do not use the common
domain table?
B/c it was designed 8yrs ago and we were going for compressable space
and making it as quick as possible to search?
* Why the incremental update mechanism (eg. applying xml diffs to
the sqlite database) was not been considered from the very beginning?
It wasn't necessary? There was a massively smaller number of pkgs to
consider.
-sv