On Thu, 2007-01-18 at 09:39 -0800, Toshio Kuratomi wrote: > On Thu, 2007-01-18 at 09:53 +0200, Ahmed Kamal wrote: > > Appreciating everyone's help, it seems others have attempted this > > before. Anyway, let's put this through the test of time :) Also, I > > totally agree with keeping drpms only if they meet certain criteria, > > i.e. provide >50% savings or similar. > > > > Right now, I am trying to figure out how/where the server side will > > store the drpm metadata. Other.xml.gz seems like a good place, or > > maybe a new drpm.xml.gz, but I am not sure how such file should be > > written. > > I seem to recall that primary.xml.gz can list arbitrary xml files which > the depsolvers will ignore if they don't need them but Seth would know > better. repomd.xml can list additional files, not primary - but the result is the same. You'd want to tie knowledge of drpms into createrepo. > Are you writing this from scratch? If it's using the yum plugin that > already exists it might be expecting the metadata in a specific format > already. plugins can do whatever, pretty much, when it comes to what kind of metadata they want to deal with. -sv
