[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: Q:How to handle backports?
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2003-11-04 0:16:17
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Monday 03 November 2003 03:37, Friedrich W. H.  Kossebau wrote:
> Pardon me, but I fear this won't work this way round... Using kdelibs from
> HEAD I have close to no comfortted way to find out what calls are new or
> where fixed and which aren't... Right?

all new methods in the libraries should be marked as "@since 3.2" (or whatever 
version they were new in) ... as for fixed, there shouldn't be any behaviour 
changing changes to the API... bugfixes, perhaps, but that should be all 
(exceptions exist, i'm sure)...

but yes, it isn't the easiest thing to check that app changes work perfectly 
against an older version w/out having the older version installed... 
something i've found handy: install the kdelibs, kdelibs-devel, kdebase and 
kdebase-devel  packages for your OS for the current stable and build against 
that for larger app backporting efforts...

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2-rc1-SuSE (GNU/Linux)

iD8DBQE/pu/S1rcusafx20MRAgmOAJ403gc5qJT3RHKib1dLRylLjGLxDQCdHZzu
Nk2Rz/sXGZ31OIXey4oMPU8=
=kpPk
-----END PGP SIGNATURE-----
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]