What I would do then is create a patch to the RPM instead.
Using the mythical bdiff & bpatch ():
foo-1.0.0.0-1.rpm [250MB]
foo-1.0.0.0-2.rpm [251MB]
"bdiff" foo-1.0.0.0-1.rpm foo-1.0.0.0-2.rpm foo-1.0.0.0-1-2.patchrpm
foo-1.0.0.0-1-2.patchrpm [12MB]
"bpatch" foo-1.0.0.0-1.rpm foo-1.0.0.0-1-2.patchrpm foo-1.0.0.0-2.rpm
Done.
- -
- Jason Pyeron PD Inc. http://www.pdinc.us -
- Sr. Consultant 10 West 24th Street #100 -
- +1 (443) 269-1555 x333 Baltimore, Maryland 21218 -
- -
This message is for the designated recipient only and may contain
privileged, proprietary, or otherwise private information. If you
have received it in error, purge the message from your system and
notify the sender immediately. Any other use of the email by you
is prohibited.
Message
From: rpm-list-bounces (AT) redhat (DOT) com [mailto:rpm-list-bounces (AT) redhat (DOT) com]
Behalf Martin Koller
Sent: Thursday, February 01, 2007 12:42
To: RPM Package Manager
Subject: Re: Can RPM handle "patch" RPM files ?
Thursday 01 February 2007, Jos Vos wrote:
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 ".
That's a pitty, as a new package would mean ~250 MBs which is not really
an option if I want to deliver a patch for 1 file
Thanks nevertheless for the quick reply.