From kde-core-devel  Fri Jan 13 18:48:01 2012
From: Ingo =?iso-8859-15?q?Kl=F6cker?= <kloecker () kde ! org>
Date: Fri, 13 Jan 2012 18:48:01 +0000
To: kde-core-devel
Subject: Re: hard-dep for Qt 4.8
Message-Id: <201201131948.02062 () thufir ! ingo-kloecker ! de>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=132648066204674
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart11439687.MbegcaDz2N"

--nextPart11439687.MbegcaDz2N
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Friday 13 January 2012, Thiago Macieira wrote:
> On Thursday, 12 de January de 2012 22.50.24, Ingo
> =3D?ISO-8859-1?Q?Kl=3DF6cker?=3D
> wrote:
> > If you want developers to switch to Qt 4.8 to get the KDE code
> > better tested with this version of Qt then simply ask developers
> > to do so. I see no good reason to force developers to do so.
>=20
> You know what happens when people are using a new version of Qt,
> right?
>=20
> They start using features from it.

Sure. And they are welcome to do so in their applications. But if they=20
want to do so in a library that many people depend on then they should=20
do so respectfully, i.e. without forcing everybody else to update to the=20
new version the same minute a new feature is used for the first time. As=20
Thomas wrote ifdef's can help.

In kdepimlibs we have lived quite well with this policy for years.


Regards,
Ingo

--nextPart11439687.MbegcaDz2N
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)

iEYEABECAAYFAk8QfGIACgkQGnR+RTDgudjvNwCcDbBQdVfxB6c0nGIiCHc+Barj
xTkAnj8nM69oDaUgLys4+DHpq6frT3Qj
=IhN6
-----END PGP SIGNATURE-----

--nextPart11439687.MbegcaDz2N--