On 05/11/2010 07:33 PM, Jesse Keating wrote: > On Tue, 2010-05-11 at 19:20 +0200, Ralf Corsepius wrote: >> On 05/11/2010 07:12 PM, Jesse Keating wrote: >>> On Tue, 2010-05-11 at 19:10 +0200, Ralf Corsepius wrote: >>> >>>> On 05/11/2010 07:03 PM, Jesse Keating wrote: >>>> >>>>> On Tue, 2010-05-11 at 18:44 +0200, Ralf Corsepius wrote: >>>>> >>>>>> On 05/11/2010 06:27 PM, James Antill wrote: >>>>>> >>>>>>> As I said in another reply, there are currently no deltarpms for >>>>>>> wesnoth-data due to it's size. >>>>>>> >>>>>> Then fix this deficiency of your process and provide them. >>>>>> >>>>>> >>>>>> >>>>>> >>>>> Patches welcome. >>>>> >>>> Part of it is lingering in bugzilla: >>>> https://bugzilla.redhat.com/show_bug.cgi?id=563866 >>>> >>>> I am using a locally rebuilt (due to upstream refusing to provide one in >>>> Fedora) patched createrepo as part of a 3rd party repo's infrastructure. >>>> >>>> >>> That doesn't actually help. It doesn't address the base problem of how >>> delta rpm does its work, by reading everything into ram >> Correct, but it makes "running out of RAM" scalable. It allows you to >> extend the hard-coded limitations to the HW you are using and to the >> actual demands of your packages. >> >> > > And right now the values used are scaled to the hardware we have at > hand. So adjusting it wouldn't help Fedora one bit. Makes me wonder about your HW. Fact is, extending the limits to 200MB (the hard-coded limit is 100MB) I having no problems with building drpms from packages which are in the order of 150MB-200MB (unpacked size) on standard x86_64-PC hardware with 4GB RAM. Ralf -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
