[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Google
  Web www.spinics.net

Re: Appropraite use of Release and Version



On Thu, 10 Mar 2011, Marc Deop wrote:

> On Thursday 10 March 2011 12:30:20 Fawad Ali wrote:
> > I am rpm packaging my software. I want to know the appropraite use of
> > Release and Version Numbers. Lets say my RPM package has release 1 and
> > version 1 currently. If I do a small change like a one line addition in
> > code, what should I change in my spec file for this, release or version?
> 
> If you changed the spec file you should increase the release version.
> 
> The Version in the spec file refers to the software version, therefore you
> should only modifiy it if there is an upgrade to the software you are
> packaging.

You would also change the release when adding new Patch files to an
existing upstream vendor version.  As an extreme example, look at the
release numbers on RedHat enterprise kernels.  They apply numerous patches
backporting various features and fixes to a stable linux kernel version.
That is why you can have a package like kmod-drbd83 that works with a
whole series of EL5.5 kernel releases.  (See the Userfriendly joke
about "very few unpatched kernels".)

-- 
	      Stuart D. Gathman <stuart@xxxxxxxx>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
_______________________________________________
Rpm-list mailing list
Rpm-list@xxxxxxxxxxxxx
http://lists.rpm.org/mailman/listinfo/rpm-list


[Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch List]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]