> If you officially patch those files I'll be sure to run another pass at > building. Changes are in SVN; you may want to rebuild everything just to make sure nothing obscure broke. > I built this pykde3 package from svn. According to configure.py, the svn > version is 3.16.6 (pykde_version_str = "3.16.6"). The latest version > provided upstream is 3.16.7 > (http://www.riverbankcomputing.co.uk/software/pykde/download3). Oddly, the > upstream providers forgot to update the embedded version variable, which > is still at 3.16.6 despite the tarball saying 3.16.7. > > Questions: > > 1. The folks who create python-kde3 refer to the package as pykde3. For > consistency, should Trinity use the same name? Yes. > > 2. Should Trinity continue providing a version when upstream > (http://www.riverbankcomputing.co.uk/software/pykde/intro) maintains > package sources? You're not providing SIP and PyQt3 for that same reason. No. However, I cannot make that large of a change this close to release. The appropriate action will be taken for 3.5.13. Thanks for all your hard work in getting this to compile! Tim