Re: adding different compression types to createrepo

"Duncan Mac-Vicar P." <[email protected]> Fri, 06 Aug 2010 12:02:32 +0200
Newsgroups gmane.linux.rpm.metadata
Message-ID <[email protected]>
  On 08/04/2010 04:28 PM, seth vidal wrote:
> Then what does it matter to you if there are xml files or not; if you're
> just converting whatever data you have into .solv files?
Because that will force everyone else to reimplement their tools using a 
design that is based on a implementation and not the other way around.
> Do you realize how combative your tone is? Is that on purpose?

I am not combative, really. I actually feel sad.

We have invested so much time in following what you guys do in every 
possible aspect, the metadata, we moved our updates to updateinfo.xml, 
changed the whole wording of channels/sources to repositories.

We took all SUSE weird changes to rpmmd and put them as extensions. We 
started to deprecate the old susetags format for rpmmd repositories.

All this just to make the rpm world better and interoperable. The 
openSUSE build service can build for SUSE/Fedora/Mdv distros, and of 
course the generated repositories are rpmmd-based.

If yum will manage the repodata format tied to Fedora's specific 
implementation, that means that _IMO_ rpmmd is just not ready to be the 
rpm metadata format.

I am not saying that you should not do it. I am just saying that may be 
it was wrong for us to think of rpmmd as a "format" or possible 
"standard". We also have investments to protect here, and we need to 
define or have an idea what will be the metadata for our repositories in 
the long term (because it is not something you want to change every week).

Duncan