--===============0314723827==
Content-Type: multipart/signed;
  boundary="nextPart4229924.Q2pjJ8kv76";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

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

On Tuesday 12 October 2010, Thomas Friedrichsmeier wrote:
> 1b) [...]
> Rationale: If package X is available in, say,
> 4.4.4, but fails to compile in 4.4.5, then the only options are to either
> stick with 4.4.4, or not to have package X. But most of the time package
> X-4.4.4 would work just fine with kdelibs-4.4.5, so why shouldn't it be
> included in the release?

Half an hour after I've written this, I've run into this type of problem,=20
again, while trying to talk a co-developer into getting RKWard to build on=
=20
Windows: Package "automoc" is not in available in 4.4.4, but the latest=20
available version of the package (4.3.2) works just fine (for me).

I suppose this can be fixed manually by whoever has the means to (please do=
!),=20
but wouldn't it be possible to avoid this type of problem most of the time,=
=20
simply by _not_ splitting up by release, by default?

Regards
Thomas

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

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

iEYEABECAAYFAky0kOMACgkQEKRv+5DVNhgMfwCfWsVv+tMWUeruZiiCQOxGlG9D
aLAAoMmFWEUuQdzprj3PYX+HKU4TQQVt
=pK2F
-----END PGP SIGNATURE-----

--nextPart4229924.Q2pjJ8kv76--

--===============0314723827==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-windows mailing list
Kde-windows@kde.org
https://mail.kde.org/mailman/listinfo/kde-windows

--===============0314723827==--