Status of KDevelop 1.2
hi Debian folks,
for those who do not know it already, I'm the guy who try to package the
KDevelop 1.2 application for Debian since the QT2 libraries are GPL.
The proble I've is the incompatibility of KDevelop 1.2 with the qt2.
IT IS NOT POSSIBLE TO GET IT COMPILE WITH THE QT2 LIBRARIES !!!
Future versions of KDevelop 2.0 will be based on QT2. Also the CVS
snapshots "works" already with QT2 but they are not for productive
use. The status of the sources is more then experimental :(
The one and only solution to get KDevelop 1.2 running with potato and
the current QT2 libraries is to package KDevelop 1.2 against QT1. And
here is the second problem exist with the current KDE2 packages.
The QT1 and QT2 libraries can not coexist on the same system :( The
reason is to see in the missing support for the QT1 libraries by
Debian, so QT1 never exist officially so we have not to worry about
this...
Packaging KDevelop 1.2 against QT1 make it impossible to make this
package available from the Debian FTP server because of the license!
You will now ask me what could be done now?
+ Repackage QT1 stuff so it will not conflict with current QT2 packages
+ Package KDevelop 1.2 against this packages and make them public
on a unficial way!
+ Support the KDevelop people to get the 2.0 working with QT2 with the
same or better quality as 1.2 did!
Received already a interesting eMail from Erik Winn you can read as
next, so I hope to get it working for all the Debian fans here who
would like to try/use KDevelop 1.2...
> Noticed your question on the lists at kdevelop - I am not subscribed to the
> list but I might be able to help. I am running kdevelop 1.2 with KDE2 as I
> write... I was just trying to find a good trick to avoid editing the
> makefiles manually to link to /usr/lib instead of /usr/local/lib ...:)
>
> Anyway, alot of the old kde apps will still run on the new libs. So, if you
> compile against kde1 and then shuffle some icons around it may actually work
> - other wise you might have to do what I did which is to compile just kdelibs
> for /usr/local (or what ever) and then build against that. Might be worth
> using rpath in this case as otherwise you have to set KDEDIR which screws up
> configure ... and we're back to what I was just doing.
>
> BTW, the kde 1 and kde 2 debs have several conflicting .so. files and
> headers - they don't really get along :(. I'm afraid running the two may
> never really work with stock (rkrusty) debs. Its one of those situtations
> where policy is sort of strangling us.
>
> Let me know if you have any questions or need any help - I'll do what I can
> (might not be much but what the hell ...)
>
> Cheers,
> Erik
>
> PS I actually got the whole kdk to work - could maybe whip up a couple of
> example debs for you .... if I could figure out where to put them ...
--
Raphael Bossek <raphael.bossek@solutions4linux.de> [ICQ #40047651]
Reply to: