This work is based on the "deltarpm" tool which is written by Michael Schroeder at suse, and is the tool used by suse. Not sure if Mandrake is using the same tool though!<br><br><div><span class="gmail_quote">On 3/11/07,
<b class="gmail_sendername">nodata</b> <<a href="mailto:lsof@nodata.co.uk">lsof@nodata.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Am Sonntag, den 11.03.2007, 14:07 -0400 schrieb Warren Togami:<br>> Toshio Kuratomi wrote:<br>> >> If you had efficiency threashold at >50% and size of ORIGINAL rpm<br>> >> larger than a certain size (say 1 meg? 10 megs? that would be up to
<br>> >> whoever is doing the work and not me, a lurker), it could work.<br>> >><br>> > Another metric could simply be absolute size of the difference. If a<br>> > major openoffice.org-core update was only a 25% savings, that would
<br>> > still be about 25MB of data.<br>> ><br>><br>> Err, yes, this is what I meant. =)<br>><br>> Warren Togami<br>> <a href="mailto:wtogami@redhat.com">wtogami@redhat.com</a><br>><br><br>Is this delta rpm work separate from what Mandrake or Suse (I forget
<br>which) have been using for quite some time now?<br><br>--<br>fedora-devel-list mailing list<br><a href="mailto:fedora-devel-list@redhat.com">fedora-devel-list@redhat.com</a><br><a href="https://www.redhat.com/mailman/listinfo/fedora-devel-list">
https://www.redhat.com/mailman/listinfo/fedora-devel-list</a><br></blockquote></div><br>