You said Mandriva and Novell were using these two methods. What is preventing their widespread adoption because they seem to me to be exactly what is need in Fedora? Is there continued development in this direction to creating even better tools and what those better tools would be I don't know.
<br><br>Either way, sounds great. I should probably install Mandriva or SuSE one of these days and check it out.<br><br>Benjy,<br>AWWTF<br><br><br><div><span class="gmail_quote">On 11/30/05, <b class="gmail_sendername">Michael Schroeder
</b> <<a href="mailto:mls@suse.de">mls@suse.de</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;">On Wed, Nov 30, 2005 at 05:09:31PM +0100, Emmanuel Seyman wrote:
<br>> Looking at all the rpms bigger than the kernel, a whole lot of them are<br>> language packs (KDE, openoffice, aspell) and fonts (asian and tetex). Is this<br>> patch.rpm mechanism going to work on these files?
<br><br>Sure. Why shouldn't it work? But please don't confuse patch rpms<br>and delta rpms.<br><br>patch rpms are rpms which contain only changed files. They contain<br>complete files, no binary delta mechanism is used. patch rpms can
<br>be applied to multiple versions.<br>delta rpms use a binary delta algorithm and can thus be only applied<br>to a single version of a rpm.<br><br>Cheers,<br> Michael.<br><br>--<br>Michael Schroeder
<a href="mailto:mls@suse.de">mls@suse.de</a><br>main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}<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>