Mailinglist Archive: opensuse-packaging (89 mails)

[Christoph Thiel <cthiel@xxxxxxx>]

On Thu, 1 Dec 2005, Richard Bos wrote:

> Op woensdag 30 november 2005 23:26, schreef Christoph Thiel:
> > On Wed, 30 Nov 2005, Scott Lowrey wrote:
> > > Thanks, Andreas.  How, then, do I develop a patch RPM?  Are there spec
> > > file macros that tell rpmbuild that this is a patch?
> >
> > Basically you just need two different version of a package to create a
> > patch from a to b. The creation of a patch rpm is done by a special
> > program, which isn't publicly available to my knowledge - but AFAIK there
> > are attempts to change this. Michael will know for sure ;)
> 
> linux:~ # rpm -qi deltarpm
> Name        : deltarpm                     Relocations: (not relocatable)
> Version     : 3.3                               Vendor: SUSE LINUX Products 
> GmbH, Nuernberg, Germany
> Release     : 0.1                           Build Date: Tue Oct 11 15:30:17 
> 2005
> Install date: Sun Oct 30 10:42:22 2005      Build Host: vivaldi.suse.de
> Group       : System/Packages               Source RPM: 
> deltarpm-3.3-0.1.src.rpm
> Size        : 534916                           License: BSD
> Signature   : DSA/SHA1, Tue Oct 11 15:40:41 2005, Key ID a84edae89c800aca
> Packager    : http://www.suse.de/feedback
> URL         : ftp://ftp.suse.com/pub/projects/deltarpm
> Summary     : Tools to Create and Apply deltarpms
> Description :
> This package contains tools to create and apply deltarpms. A deltarpm
> contains the difference between an old and a new version of an RPM,
> which makes it possible to recreate the new RPM from the deltarpm and
> the old one. You do not need to have a copy of the old RPM, because
> deltarpms can also work with installed RPMs.


deltarpm != patchrpm


Regards
	Christoph