[Rpm-metadata] Re: take 3 (or is it 4) whatever :)
skvidal at phy.duke.edu
Thu Oct 9 05:15:55 UTC 2003
> So I'm taking part of what Darrin recommended but giving the parser a
> quick way to skip the package if they don't understand it/don't need it.
> you check the namespace for the <package> - if it is not one you can
> deal with then you move on.
> Then we can get into the nitty-gritty of defining the namespace for each
> of the formats.
> And the rules get simpler b/c then all the package mgmt tools have to do
> is know what things they can and cannot deal with.
> so, for example, if jbj gets his way and rpm becomes capable of dealing
> with debs, then I can make yum start grokking the :
> <package xmlns="http://thatsite/ns/deb">
> but until then I skip the ones that are not rpm.
so one thought about this.
I don't know how functional this is in terms of xml namespaces - but it
would be great if there were a way of subclassing namespaces.
so you had a base package namespace
and then you had rpm and deb subclasses that use the base package
namespace for common things.
that way people parsing the file could write their parsers to the base
namespace and then to the other items in the deb and rpm subclasses.
So we'd still need to hash out the common areas for the base name space
and maybe as revisions and versions go forward be able to move more
things into the common namespace.
More information about the Rpm-metadata