From kde-edu-devel Tue Jun 03 20:48:01 2008 From: Thomas Zander Date: Tue, 03 Jun 2008 20:48:01 +0000 To: kde-edu-devel Subject: Re: [kde-edu]: koffice dependency for kdeedu Message-Id: <200806032248.01842.zander () kde ! org> X-MARC-Message: https://marc.info/?l=kde-edu-devel&m=121252998609625 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============1910031362==" --===============1910031362== Content-Type: multipart/signed; boundary="nextPart6554624.rsyT24ItUU"; protocol="application/pgp-signature"; micalg=pgp-sha1 --nextPart6554624.rsyT24ItUU Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 3. June 2008 09:32:44 Anne-Marie Mahfouf wrote: > Hi, > > I was surprised to learn that there is a KOffice dependency in kdeedu. > There is a Marble Koffice flake in Marble code and I am not sure this is > the right place for it. I'd like to discuss this with Koffice people as > they are involved as well. I don't know much about it as nobody explained > this but in general, having modules depending from each other that way is > not smart. AFAIK its not allowed by KDE policies; major modules should not have=20 inter-dependencies. But I don't think it has to be a problem. The long term planning of KOffice is something that may come to the rescue= =20 here, KOffice has a separate libs dir and Simon is currently linking again= st=20 those libs. Several ODF related libs are planned to be moved out of KOffic= e=20 into a separate module (some even speculate about kdelibs). These libs can= =20 then be used by other modules very much like kdepimlibs. The marble shape= =20 will certainly be able to use those instead of depending on koffice. Unfortunately the 2.0 release of KOffice is going to happen first, and we=20 won't be able to give an exact timeline on when these libs are going to be= =20 available for marble. The solution I suggested earlier for this issue was to make the marble-flak= e=20 plugin use the svn-extern to link to the flake libs as long as they are not= =20 yet released. I think this still is the best solution to avoid a lot of problems for all= =20 parties and long long recompiles for Simon. (depending on 2 modules that=20 change can't be easy). Maybe with the new data point that Annma brought up (unwanted module=20 dependency) we should re-evaluate this option? Cheers! =2D-=20 Thomas Zander --nextPart6554624.rsyT24ItUU Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQBIRa4BCojCW6H2z/QRAohYAJ4yp8SK4jT09pKmGk7c0W/bZCJ6BACgkkfF 2pCSiwEjl7UO9yBi2zL5FKU= =3EoY -----END PGP SIGNATURE----- --nextPart6554624.rsyT24ItUU-- --===============1910031362== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-edu mailing list kde-edu@mail.kde.org https://mail.kde.org/mailman/listinfo/kde-edu --===============1910031362==--