Patch issues with RH ES3 - understanding the rpm versions
 

Hi,
I was looking at the Redhat Errata page for security advisories when I came across 2 source rpm packages which are concurrently in used (?).. My understanding was that they are cumulative.
For instance:
gdk-pixbuf-0.22.0-13 RHSA-2005-810
gdk-pixbuf-0.22.0-11 RHSA-2004-447

and
gtk2-2.2.4-19 RHSA-2005-811
gtk2-2.2.4-8 RHSA-2004-466

My question would thus be, does the gdk-pixbuf-0.22.0-13 incorporate the changes in gdk-pixbuf-0.22.0-11 too? If not, which would be a more correct version to be using?

ps. Does the -13 and -11, make any significance to identitying the packages? Or the 0.22.0 versioning would suffice for identifying the packages?

I came across 2 source rpm packages which are concurrently in used (?)..
Maybe due to an install instead of upgrade?


My understanding was that they are cumulative.
That would be my understanding as well.


If not, which would be a more correct version to be using?
With software it's best to go for the latest release, unless you have legacy apps or other considerations *and* understand the consequences of not upgrading.


ps. Does the -13 and -11, make any significance to identitying the packages? Or the 0.22.0 versioning would suffice for identifying the packages?
If you build rpm's you would define a version tag something like this:
# define major 0.22
# define minor 0
# define release 13
# define version %{major}.%{minor}-%{release}
You see the only thing incremented is the release tag, which is RHL's way of saying they incorporated changes to that version of gdk-pixbuf, so AFAIK in case releases > 1 the major+minor tag isn't sufficient.