[Rpm-metadata] two other areas needed
seth vidal
skvidal at phy.duke.edu
Thu Oct 9 05:04:51 UTC 2003
> I was thinking that file #2 would probabaly only be
> something like:
>
> name version release epoch arch size headersize [url]
>
> for each package in the channel/repo/dir/whatever
> (url in brackets since it wouldnt be needed if you stick
> all the rpms in the same dir, but adding it would be
> theoretically more flexible).
then maybe files like this:
1. channels/repos/whatever available - timestamps/md5sums of the mdfiles
2. xml file of common data (nevral)and a tag telling what kind of file
they are
3. xml file of their dep/provides/suggests/etc information
4. xml of complete file lists
5. xml 'misc' data (changelogs, 'other' data) :)
Questions that come up - in this representation where do the pkg mgmt
and vendors store their specific info? Where does rc store some
licensing information (for an example)?
Would that be worth having an additional file?
Am I maybe a little looney for suggesting this?
-sv
More information about the Rpm-metadata
mailing list