Re: discussion of createrepo and repodata format future

  On 08/04/2010 04:59 PM, seth vidal wrote:
> Hi folks,
>     instead of trundling down the existing thread I thought we could
> [re]start a discussion of things that could be improved in future
> versions of the repodata and laying out the data.

I was thinking about the sqlite part, and I think the change has to go 
in a way that
* assumes sqlite3 is _yum_ cache
* allows distros to use different cache strategies

The sqlite types could go as extra data. Something like:

<data type="filelists">
<checksum 
type="sha256">1ef045e8c2a00901b1c3591990b2ec2498d2ed1807b315622a89aa73e6811778</checksum>
<timestamp>1277771835</timestamp>
<size>1098607</size>
<open-size>15276280</open-size>
<open-checksum 
type="sha256">7a620afa9594e0f9be4048d1968881079174b6a4600617f55da8bd0f0ae4a4a6</open-checksum>
<location href="repodata/filelists.xml.gz"/>
<cache-location format="sqlite3" href="repodata/filelists.xml.sqldb"/>
</data>

Another problem that shows up is that caches may be different. For 
example, yum has one file per metadata. We have just one solv file per 
repository. But I guess that is just another tag under repomd tag. 
Specifying the location, and the format, so that the downloader can 
choose whether to use it or not.

Also, what is the status of these tags?

<revision>1277771829</revision>
<tags>
<repo>obsrepository://build.opensuse.org/openSUSE:11.2:Contrib/standard</repo>
</tags>

In repomd.xml, we are already using them.

Duncan