On Wed, 11 Apr 2007, seth vidal wrote:
On Wed, 2007-04-11 at 08:19 +0300, Panu Matilainen wrote:
On Tue, 10 Apr 2007, James Bowes wrote:
It's not just about breaking yum API but also about any other repodata
sqlite users. The only one at the moment is probably apt-rpm and even
there it's not included in any released version yet so from that POV now's
a good time to make changes (even bigger ones if needed), later it gets a
bit uglier. Although I will need to figure out a nice way to support more
than one db format sooner or later by looks of things.
I'm assuming, perhaps incorrectly, that smart might be able to make use
of this, too.
It certainly could, but doesn't at the moment. Most likely Gustavo & other
smartpm-folks aren't even aware of the sqlite extension :)
But nevertheless, you're right - needing to be able to cope with
distinguishing b/t db version X or db version X+1 is something that it
will be useful to do.
Indeed. At least with the sqlite db, there IS a version tag one can
cleanly check against and refuse to go on in case of an unsupported
version instead of blowing up trying to parse it. So while the format
obviously shouldn't change too often, changes CAN be handled safely now,
which is only a good thing.
- Panu -
_______________________________________________
Yum-devel mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/yum-devel
