[Yum-devel] Package update metadata

[seth vidal]

On Thu, 2006-01-12 at 17:14 -0500, Luke Macken wrote:
> I hacked out a quick implementation of Seth's metadata format[0] for the
> Fedora Update System (example[1]).  Mind you, the format isn't set in stone yet,
> so any suggestions are welcome.
> 
> My question is, how do we want to store this metadata? Do we want to
> push it alongside the repodata, or should it be integrated?
> 
> Questions/comments ?
> 
> luke
> 

I think just shoving them in 'repodata' would be messy. Maybe something
off of there, though, so we can always find them.

However I think we should sort out the order of operations for getting
this data in the right place.

What we had discussed before for this was:

1. update info is out there in some db accessible via a cgi or generated
into these files accessible somewhere.
2. user wants to make a repo out of some packages and wants to include
this update information in his/her repodata.
3. user runs:
 createrepo
--update-info-location=http://url/to/cgi/or/something /path/to/pkgs

4. createrepo grabs the update info .xml files from that cgi or path.


Does that still make sense or is it just dumb, now?

I'm thinking about the people here who are respinning or being picky
about the updates they get from their distro provider. People rebuilding
the updates or splitting out some of them, for example, who cannot
simply mirror.

-sv