Re: primary refinement

Seth,

This is actually something I have been thinking about for a different
reason. We have to provide those fileds in different languages. rpm
headers have the english 'defaults' but we have some headers translated
in a DB outside of rpm which we use to generate the metadata for the
different languages supported
Trying to have a 1 to 1 presentation of what we have right now I came up 
with something similar to what you are suggesting.

- primary.xml has no text fields
- primary.{lang}.xml has translatable fields

So I think its a good idea to have the split.

I wonder if there was something else proposed with regard to
localisation and custom fields.


Anas


seth vidal wrote:
> So i'm looking at primary.xml.gz and I'm thinking of useful ways of
> refining the data included a bit so it's a bit lighter to read in.
> 
> I was thinking what do y'all think of moving the following fields to a
> different xml file in the repository?
> 
> summary
> description
> packager
> license
> vendor
> group
> url (url for the package, not url location of the rpm)
> buildhost
> 
> 
> my thinking is that it would decrease the data in primary.xml.gz and
> make actions that are most common, 'update, install, etc' a fair bit
> faster simply by not having to go through all these nodes.
> 
> every package has most of these entries, they're fairly text heavy and
> not useful for solving deps or finding out which packages are available.
> 
> thoughts?
> 
> -sv
> 
> 
> _______________________________________________
> Rpm-metadata mailing list
> [email protected]
> https://lists.dulug.duke.edu/mailman/listinfo/rpm-metadata