On 2/1/07, Jos Vos <jos@xxxxxx> wrote:
On Thu, Feb 01, 2007 at 05:50:04PM +0100, Martin Koller wrote: > Is there any way to solve this or is RPM simply not made for this scenario ? The latter. You should provide new RPM's of the full product and give them a newer version and/or release number, so that you can upgrade with "rpm -U ...".
This is true to the point that RPM does not provide patching support ATM. That said, better packaging produces many packages rather than one monolithic 250Meg pile o stuff. So if you split your rpm into several smaller rpms that provide some logical set of functionality you won't have the mess you have atm. In doing this you can even stream line the building of your application because its likely you really don't have rebuild all the libs and binarys of your app every time. Cheers...james _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
