Re: Exposing split media

On Thu, 2005-11-10 at 03:11 -0500, seth vidal wrote:
> That also ties into David's idea of being able to make virtual
> repositories of arbitrary packages w/o having to have the packages
> themself. So we could possibly:
>  - generate the metadata w/o the media/base path on the actual packages
> or 
>    download existing metadata from a previously created repository.
> 
>   Then:
>  - generate a file mapping package->media/basepath
>  - combine media/basepath + previously created package metadata into new
> set of metadata, rewriting primary.xml and repomd.xml for new content
>   or
>  - create a new metadata file named location.xml containing the
> package->media map

I think for both anaconda's needs and virtual repos, you need a way to
manually specify the package -> basepath mapping (with appropriate tool
support), so that for both cases the same flow could be used; I would
structure it a little differently though to avoid rewriting primary.xml
and repomd.xml:

      * Generate/maintain a package->media/basepath mapping with a
        separate tool
      * In createrepo:
              * Read package->media/basepath mapping in a separate data
                structure (if it is given on the cmd line)
              * When generating primary.xml, add xml:base info if it
                exists for that package

Since we need a separate file to describe the package->media/basepath
mapping anyway, an alternative is to push all the work into the client,
and just include the mapping file in the repomd.xml. It would keep
createrepo simpler at the cost of duplicating work in every client that
uses the mapping info. I am not hot on this idea, but it's worth
thinking about.

> The reason I like the idea of having a package->basepath map that
> createrepo could take for input to generate the new primary.xml is to
> avoid arbitrary 'subdir mapping' code happening in createrepo.

Yes, specifying this explicitly seems much cleaner than relying on
subdir naming conventions.

David

_______________________________________________
Rpm-metadata mailing list
[email protected]
https://lists.dulug.duke.edu/mailman/listinfo/rpm-metadata

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQBDc6me4BLQetDjzDARAvx/AJ9HpMU/kA51RG2Ji5Wi2DRXl8zpbwCgk7O+
rYRTw8Xd/hRvr1pEpj7nW8c=
=yblw
-----END PGP SIGNATURE-----