14 Sep
2010
14 Sep
'10
9:34 p.m.
Okay, let's ensure I have my head on straight. :)
Yes you do; your summary below is correct.
I think I understand
what is happening here. I've already updated svn and am compiling
kdebindings now.
Here is what I am adding to the kdebindings build script notes, adapted
from your svn README. Please review:
# Some build notes about kdebindings:
# In the past, the kdebinding sources from KDE upstream were stock and
untouched. With
# Trinity KDE, the SIP and Python binding support was split from the
original kdebindings
# sources. Both SIP and PyQt are maintained upstream and no longer are or
should be a part
# of (Trinity) kdebindings. Further, the python sources originally part of
the stock
# kdebindings package were outdated and do not compile with the latest
flex/bison/python
# sources.
# SIP and PyQt3 may be downloaded at slackbuilds.org.
# Python binding support remains available with Trinity KDE. A new package
called PyKDE is
# available in the Trinity source tree: <svnroot>/libraries/python-kde3.
That package can be
# compiled against the latest SIP and PyQt sources. That is, install SIP
and PyQT, then build PyKDE.
# SIP and PyQT are required to build PyKDE.
# Summary: Python support no longer is part of kdebindings but remains
available in different packages.
Are the patches I submitted regarding the three /usr/include files needed?
I'm building right now with those patches....
I don't think so. In fact, I was hesitant to apply them (and did not
apply them) because I did not like what they were doing to the Trinity C++
namespace. If they are absolutely necessary, then I will have no choice
but to commit them and do a full rebuild test for Debian.
Let me know either way!
Tim