delta rpm's for RPM Fusion! (was Re: delta rpm's for RPM Fusion?)

[Thorsten Leemhuis]

On 17.05.2009 20:44, Michael Schwendt wrote:
> On Sun, 17 May 2009 19:00:32 +0200, Thorsten wrote:
> 
>> On 16.05.2009 08:46, Jonathan Dieter wrote:
>>> On Fri, 2009-05-15 at 22:50 +0200, Michael Schwendt wrote:
>>>> On Thu, 14 May 2009 22:10:03 +0300, Jonathan wrote:
>>>>
>>>>> FWIW, createrepo now creates the deltarpms in the Fedora infrastructure,
>>>>> rather than the presto-utils.
>>>>> As for hardware resources, in Fedora we're not generating deltarpms for
>>>>> rpms larger than 100MB as [...]
>>>> What kind of repository inheritance is implemented by Fedora
>>>> Infrastructure for deltarpms?
>>>> For example, are F-11 deltarpms generated against F-10 Updates *and*
>>>> F-10? Or even a level deeper down to F-9 Updates plus F-9?
>>> The only repository inheritance is F-10 Updates inheriting from F-10 GA,
>>> and the same for F-9 Updates from F-9 GA.  F-11 Updates currently
>>> inherits from Rawhide F-11, and Rawhide F-11 only generates deltarpms
>>> against itself.
>> Mschwendt committed changes to the master push scripts that should make
>> something like the above easy to do in RPM Fusion as well.
>>
>> But I didn't update the push scripts on our master server yet. F11 is just
>> a few days away and I'd prefer not to do major changes so close before a
>> release. 
> 
> JFYI, it's not "major changes", and both the recently committed features
> need to be enabled explicitly. In other words, you don't get deltarpms
> or signed repomd just by updating the scripts. Also notice that it's
> still possible to test without pushing anything, e.g. by enabling
> features for just "development" and then running RepoBuild.py manually.

Sure, but development for RPM Fusion still is F11. And I (for example)
don't want to suddenly have a stale and unneeded drpms/ directory or
something like that somewhere I'm not aware of when I do the "mkdir
releases/11/; cp -l development/ releases/11/Everything" at then end of
next week ;-)

CU
knurd