On Tue, Dec 6, 2011 at 10:56 PM, Olly Betts <o...@survex.com> wrote: > On Tue, Dec 06, 2011 at 10:31:33PM +0000, Luke Kenneth Casson Leighton wrote: >> On Tue, Dec 6, 2011 at 3:37 AM, Olly Betts <o...@survex.com> wrote: >> >> > It would probably be least error-prone if you patched the package locally >> > and once it was working, sent us a patch showing exactly what needs >> > changing. Failing that, an complete list of the "cp" commands needed to >> > take you from installing the current package to having a working setup >> > for what you're trying to do should do. >> >> sorry, olly - this is far too long ago for me to remember. the time >> for answering the bugreport was within at most 2 months of the time it >> was raised: > > It's a shame how long this bug report was left unanswered, but for the > record I've been involved in maintaining the wx packages for just under > 2 months. I'm really just a user of them who was disappointed with > the state they had got into.
*sigh* well that's fantastic that you're getting it sorted. >> i now cannot even remember what project it was that i was >> working on.. no... wait... yes i can: it was something to do with >> python-wx-webkit. > > So what does one need to do with python-wx-webkit to make use of these > files? ok, python-wx-webkit is slowly having full DOM access added to it, but it's being added manually via c++ bindings (which the wx-webkit developer is writing - it's taking him months: he could be a good couple of years at it). the python bindings _should_ be easy (viz: automatic), but the problem comes with the auto-generation of the python bindings. that's where the missing files are required, because the python-wx-webkit code is so low-level (it sub-classes wxwindow if i recall correctly) that you *have* to have those files in order to build. in other words, if someone in the future wanted to package python-wx-webkit for debian, the build would utterly fail... because "apt-get build-dep python-wx-webkit" would fail to install the required files as build dependencies [those src/_*.py files]. normally if you do "./autogen.sh; make; make install" etc on the standard wx source code then those src/_*.py files automatically get installed in /usr/include. so there's a pattern-match missing somewhere in the debian/* package files - i forget which one says which files are to be installed on a per-package basis - that's all that's needed. l. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
