From kde-core-devel  Thu Jan 22 14:27:30 2009
From: Allen Winter <winter () kde ! org>
Date: Thu, 22 Jan 2009 14:27:30 +0000
To: kde-core-devel
Subject: Re: Application version numbers
Message-Id: <200901220927.30899.winter () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=123263450919885

On Thursday 22 January 2009 8:43:30 am John Tapsell wrote:
> 2009/1/22 Allen Winter <winter@kde.org>:
> > On Wednesday 21 January 2009 11:49:41 pm John Tapsell wrote:
> >> Is it possible to have an application version just simply be the
> >> version number of KDE?
> >>
> >> The version numbers tend to be confusing.  For example, kate is
> >> released with each KDE release.  It follows the KDE releases exactly,
> >> so shouldn't the kate version be simply the KDE release version?
> >>
> >> Instead kate is at version 3.1.3, while KDE is at version 4.1.3.
> >> It makes bug reporting kinda confusing.  If I say that I have a
> >> problem with kate 3, people generally think that I mean the version of
> >> kate that came with KDE3..  And Konsole is at version 2.1.
> >>
> > Coincidentally, just the other day I created a kdepim-version.h
> > for kdepim apps to use which contains a version string matched
> > to the kdelibs version that it is released against.
> >
> > currently it says
> > #define KDEPIM_VERSION "4.3.0 pre"
> 
> You know that you could do:
> 
> #include <kdeversion.h>
> #define KDEPIM_VERSION KDE_VERSION_STRING
> 
> right?
> 
No, can't do that.
Because kdepim theoretically can build against older kdelibs.
At least that's traditionally been a goal that we try to meet.