Re: [opensuse-buildservice] openSUSE:Factory & 11.1 repos - meta data primary.xml
On Montag 08 Dezember 2008 12:37:29 Martin Mohring wrote:
Michael Schroeder wrote:
On Mon, Dec 08, 2008 at 11:17:30AM +0100, Martin Mohring wrote:
We use primary.xml for Download on Demand. Do we sit on a dead horse? What else could we use instead for getting the meta data?
You should also support the susetags format, it's pretty easy to parse.
Which files in a SUSE repo file hierachy must we parse *instead* of rpmmd primary.xml?
It is suse/setup/descr/packages.gz . However, this format might get superceeded by an extended rpm-md with next release (or not, the plan exists for a longer time already, but it did not happen so far) ... -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
Adrian Schröter wrote:
On Montag 08 Dezember 2008 12:37:29 Martin Mohring wrote:
Michael Schroeder wrote:
On Mon, Dec 08, 2008 at 11:17:30AM +0100, Martin Mohring wrote:
We use primary.xml for Download on Demand. Do we sit on a dead horse? What else could we use instead for getting the meta data?
You should also support the susetags format, it's pretty easy to parse.
Which files in a SUSE repo file hierachy must we parse *instead* of rpmmd primary.xml?
It is suse/setup/descr/packages.gz .
However, this format might get superceeded by an extended rpm-md with next release (or not, the plan exists for a longer time already, but it did not happen so far) ...
We had tested the flavors of rpmmd with the Download on Demand parser, and tested in practise with Fedora/Red Hat and openSUSE/SUSE Linux variants, to be sure it works. Now I wanted to add openSUSE 11.1 and current Factory, but did not find a primary.xml . Couldn't you call createrepo for us ? Otherwise we have to write a third parser. Martin -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Dec 08, 2008 at 01:04:28PM +0100, Martin Mohring wrote:
We had tested the flavors of rpmmd with the Download on Demand parser, and tested in practise with Fedora/Red Hat and openSUSE/SUSE Linux variants, to be sure it works. Now I wanted to add openSUSE 11.1 and current Factory, but did not find a primary.xml . Couldn't you call createrepo for us ? Otherwise we have to write a third parser.
No, createrepo kills us. It's much too slow and uses too much memory. M. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Mon, Dec 8, 2008 at 7:58 AM, Michael Schroeder
On Mon, Dec 08, 2008 at 01:04:28PM +0100, Martin Mohring wrote:
We had tested the flavors of rpmmd with the Download on Demand parser, and tested in practise with Fedora/Red Hat and openSUSE/SUSE Linux variants, to be sure it works. Now I wanted to add openSUSE 11.1 and current Factory, but did not find a primary.xml . Couldn't you call createrepo for us ? Otherwise we have to write a third parser.
No, createrepo kills us. It's much too slow and uses too much memory.
Dumb question: what in the nature of generating a package index requires the memory usage to scale in proportion to the number of packages, instead of being O(1) (constant)? Or is creatrepo's algorithm just, uh, sub-optimal? -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
On Montag 08 Dezember 2008 16:33:56 Archie Cobbs wrote:
On Mon, Dec 8, 2008 at 7:58 AM, Michael Schroeder
wrote: On Mon, Dec 08, 2008 at 01:04:28PM +0100, Martin Mohring wrote:
We had tested the flavors of rpmmd with the Download on Demand parser, and tested in practise with Fedora/Red Hat and openSUSE/SUSE Linux variants, to be sure it works. Now I wanted to add openSUSE 11.1 and current Factory, but did not find a primary.xml . Couldn't you call createrepo for us ? Otherwise we have to write a third parser.
No, createrepo kills us. It's much too slow and uses too much memory.
Dumb question: what in the nature of generating a package index requires the memory usage to scale in proportion to the number of packages, instead of being O(1) (constant)?
Or is creatrepo's algorithm just, uh, sub-optimal?
I think it is just sub-optimal. At least older implementation worked fine. However, it seems that no one has currently a real interesst to fix it, so it stays disabled for now. It is no problem to enable it again, once it works better, but this will happen after 11.1. bye adrian -- Adrian Schroeter SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) email: adrian@suse.de -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org
participants (4)
-
Adrian Schröter
-
Archie Cobbs
-
Martin Mohring
-
Michael Schroeder