Actually from what I see, you're buildging a whole infrastructure around deltarpm.. nice... very nice... So you're question seems to be not how-to use deltarpm, but how-to build distro infrastructure around it. But openSUSE doesn't have a real infrastructure around deltarpms (AFAIK). I.e. We only make delta ISOs to update, like openSUSE BETA1->BETA2. We do not have delta ISO build factory, online updates, and stuff like that. Building such an infrastructure is not an easy task. Deltrarpm usage is really simply: (it has 4 main commands) -makedeltarpm -makedeltaiso -applydeltarpm -applydeltaiso In openSUSE it is used mainly for distributing BETA DVDs. I think, that "deltarpm" for online updates must have 2 versions - for "latest" updates and for "RTM" (release to manufacture) updates (i.e. for users, that just installed Fedora from DVD, but want to do online update). So perhaps there needs to be 2 mirrors (for "latest" and "RTM") users, and they must be pre-registered in /etc/yum.repo... Garbage collection must function only on the "latest" mirror. This way, if user has not online-updated his system for several days (say he forgot to update last night), the RPMs that are updated to latest on mirror were "Garbage collected", so he will not be able to use "deltarpms". He will need to do update from normal RPM mirror, but only the RPMs that were updated last night will be updated this way. At least I see it this way... I see, that you also have hi-level dependency resolver (yum) integration with deltrarpm, while we have nothing like this for our (zypper). Since we only patch DVDs offline, we don't need dependency resolver integration with deltarpm. But very interesting idea indeed... -- -Alexey Eremenko "Technologov" --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org