I am looking into building kdepim-branch (which is Kontact enterprise4)
with a dbus that has Jaroslaws improvements.

(See  
http://techbase.kde.org/index.php?title=Projects/PIM/MS_Windows#.22Locked.22_dbus-daemon
and the corresponding kolab/issue2639 where the patches are published.)

I see that qt-4.4.0.20080222.py seems to use it own private dbus libs
from 
http://downloads.sourceforge.net/kde-windows/dbus-mingw-1.1.2.20080216-lib.tar.bz2

(By default it also gets qt-copy, so wouldn't the name "qt-copy-svn.py" be 
more appropriate?)

For getting the better dbus, I would need to get dbus-src.
Question 1: Obviously it would not be a problem to rebuild dbus later,
but wouldn't the right order to to first build dbus-src and then qt?
(This would only work if qt would not get their private copy of dbus.)

In dbus-src-1.1.2.20080216.py I've then noticed that the default is 
"svn" which - following a comment - is version 1.2.1. Also the
package version is fixed to 1.2.1.

Question 2: Would a renaming of dbus-src-1.1.2.20080216.py be adaquate?

I have no clue about if 1.2.1 has a significant improvement over the
version used for qt-4.4.0.20080222.py above, but the used version for the
qt build seems older. 

Question 3-5: Is the dbus-mingw-1.1.2.20080216-lib.tar.bz2 actually 1.1.2 or 
1.2.1? Would an update of qt-4.4.0.20080222.py' internal dbus lib be helpful?
Is the reason for using an internal version for the build still given?

Sorry for all the question marks, but it is getting to complicated for me to 
keep the overview and what might cause problems or not later.

Best,
Bernhard

-- 
Managing Director - Owner: www.intevation.net       (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

Attachment: pgpn7kaAWlseH.pgp
Description: PGP signature

_______________________________________________
Kde-windows mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kde-windows

Reply via email to