--nextPart1262890.vjXB0pJNly
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Alexander Neundorf wrote:
>If it is possible to work on KDE with the software as it comes with your
>distro the entry barrier to development is much lower.

This "entry barrier" only exists as such because the distros *are*=20
shipping cmake. If they weren't, nobody would be complaining that you=20
need a newer version.

I still see it as artificial. Why can't we require people to install the=20
newest CMake if they are building software that is hundreds of times more=20
complex? If you can get Qt and kdelibs to build, you can get CMake too.

This is the second time in as many months that you have had to intervene=20
because someone unknowingly used a CMake >=3D 2.4.4 feature. If we are=20
going to stay with 2.4.3, we should start then requiring that people use=20
*exactly* 2.4.3, so as to avoid this kind of mistakes.

>And, maybe most important, if we require a newer version of CMake, this
> needs to be brought up on k-c-d or k-b-s ;-) and then announced with at
> least one week warning period.
>And the required version in FindKDE4Internal.cmake HAS to be adjusted
>accordingly.

So what's stopping us from making that announcement now?

If you want an announcement for Qt 4.3: the qt-x11-4 snapshot switched=20
yesterday to Qt 4.3.0, which means the beta release will happen within=20
the next few weeks. Does this count as the announcement that we will=20
require Qt 4.3.0 beta 1 when it is out?

=2D-=20
=A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org
=A0 =A0 PGP/GPG: 0x6EF45358; fingerprint:
=A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358

--nextPart1262890.vjXB0pJNly
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBF8ImeM/XwBW70U1gRAt+VAJ96w+ZJLGez/Gje4WXjmDysHM9mWQCeNyfA
HH9hH4alfevINzE25kCwcwE=
=eE7E
-----END PGP SIGNATURE-----

--nextPart1262890.vjXB0pJNly--