From kde-windows  Mon Apr 26 08:52:18 2010
From: Kevin Ottens <ervin () kde ! org>
Date: Mon, 26 Apr 2010 08:52:18 +0000
To: kde-windows
Subject: KDE Platform Profiles: BIC changes
Message-Id: <201004261052.25068.ervin () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-windows&m=127227200221911
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1334324253=="

--===============1334324253==
Content-Type: multipart/signed;
  boundary="nextPart2868910.vh6arzgnTN";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart2868910.vh6arzgnTN
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hello,

As some of you might be aware of, we're working on making different profile=
s=20
for the KDE Platform, in particular to tackle the mobile case. For the long=
=20
version with the details, the thread starts there:
http://lists.kde.org/?l=3Dkde-core-devel&m=3D127107095103573&w=3D2

Now I'm addressing you guys directly because we have one particular issue=20
which is in a grey area. We try to retain binary compatibility as much as=20
possible with our changes, but there's one type of change which would not=20
break binary compatibility on our main target but would break it on Mac, an=
d=20
maybe on Windows (I'm getting mixed signals for this one).

Said change is: Moving a class lower in the depencency chain.

=46or now we found only one such case, namely KCrash could move from kdeui =
to=20
kdecore. It's a particularly interesting one as kbuildsycoca would then dep=
end=20
on kdecore only, and for the mobile case some apps might not want to link o=
n=20
kdeui.

Also I wouldn't be surprised if we find more of such cases as we go.

Hence this mail, I'd need to know if we'd be fine breaking binary=20
compatibility on those platforms in this case? It really depends on how big=
=20
the installed base is for KDE/Mac and KDE/Windows and how strong our=20
commitment on those targets is so far. Do we have any official "stable"=20
release on it? etc.

=46eedback is badly needed here so that we know if we can pursue this kind =
of=20
changes or not. I really don't want to break the binary compatibility on yo=
u=20
guys if that's not welcomed. This case would be a nice trade-off if that's=
=20
only minor annoyance as that would benefit greatly to the platform in gener=
al=20
(simplifying the internal dependencies).

Regards.
=2D-=20
K=E9vin Ottens, http://ervin.ipsquad.net

KDAB - proud patron of KDE, http://www.kdab.com

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

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

iEYEABECAAYFAkvVVEgACgkQB0u7y43syeIRIQCdGin9/KQW4qVO4k5UHxm9VuMd
sH4An0gWrAx5SN//MHKyQ+GeuN4gGE9P
=/YRZ
-----END PGP SIGNATURE-----

--nextPart2868910.vh6arzgnTN--

--===============1334324253==
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

--===============1334324253==--