updates

Hi all,
 some trivial updates to the repository generation scripts:
 http://linux.duke.edu/metadata/generate/

I was also thinking some about the repository description file and it's
purposes/goals.

right now it looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<repository> 
  <name>some name for human consumption</name>
  <contact>[email protected]</contact>
  <description>some text description</description>
  <key type="gpg">http://path/to/my/gpg-pubkey</key>
  <key type="gpg">http://path/to/his/gpg-pubkey</key>
  <metadata>
    <data type="primary" timestamp="1068793003" href="relative/path/to/primary.xml"/>
    <data type="filelist" timestamp="somenumber" href="relative/path/to/filelists.xml"/>
    <data type="other" timestamp="somenumber" href="relative/path/to/other.xml"/>
    <data type="groups" timestamp="somenumber" href="relative/path/to/groups.xml"/>
  </metadata>
</repository>


which is fine  - but the stuff outside of <metadata> is really not
appropriate for what  is being described.

It seems to me that it would be useful to have a more static file that
describes the repository and points to a this file that contains the
entries about the actual metadata file.

The reason I'm thinking of this is for repository management, the
more-static file could include the:

name, description, contact, gpg keys, keywords, etc information

the metadata descriptions could just include timestamps/checksums of the
metadata xml files and nothing else.

Then the primary repository description file could be pulled in directly
by a pkg-mgmt tool for including a new repository for the user.

So, for example, a user using yum might be able to click on a
repository.xml file in mozilla and have it import that xml file into the
yum configuration so that repository is now included in the lookups.
That way you can get some basic information that changes less often and
is more customizable.

So then our concern for a the repomd file is just:

  <metadata>
    <data type="primary" timestamp="1068793003" href="relative/path/to/primary.xml"/>
    <data type="filelist" timestamp="somenumber" href="relative/path/to/filelists.xml"/>
    <data type="other" timestamp="somenumber" href="relative/path/to/other.xml"/>
    <data type="groups" timestamp="somenumber" href="relative/path/to/groups.xml"/>
  </metadata>

which is very small and very simple and it seems to separate out the
type of data b/t the files better.


Thoughts?

-sv