-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Jonas and the team,
On 10-06-21 06:38 AM, Jonas Smedegaard wrote: > > From a quick glance it seems that your latest attempts are wrong. I > had a go at compiling now (my earlier laptop disk space problems have > been solved now!) but unfortunately didn't make it far enough to look at > this issue. > Sad I was wrong. Happy your disk is back. :) What I know for sure, is that the Python modules are not shipped with any Debian package anymore. :( > I improved build-dependencies on Boost libs. This shouldn't affect the > buildability. > Ok. I'm taking notes. ;) I don't know yet how to create patches like that. I gues git-buildpackage should provide some tools to ease that? > Python scripts are invoked directly, causing default Python to always be > used, ignoring autotools $(PYTHON) variable. This is only an issue on > systems that wants to build for a non-default Python version (i.e. not > currently a problem with Debian). I believe the best fix is to use the > autotools-provided $(PYTHON) (and the related python prefix variable - I > forgot its variable name) to compose the hashbang from a .in file of the > scripts, instead of the current "/usr/bin/env python" construct. > Reading the automake manual (#1) I guess it could be $(PYTHON_VERSION). #1: http://www.gnu.org/software/hello/manual/automake/Python.html Since the scripts have some automake variables already expanded, I could put #!/usr/bin/python@@PYTHON_VERSION@@ there, or something similar? > Python scripts rely on local modules that are a) not declared and b) not > yet built. I fixed a) with a patch, but b) still fails. I believe the > help2man rules need to depend on module building, and the patch then > changed to use build dir instead of source dir (which is wrong to use in > any case). > I think this is the most critical issue right now. Help2man calls the Python scripts, which it turn makes Python byte-compile the modules with the wrong Python version. (?) To fix this, the man page rule in man/Makefile.am should depend on building the Python modules. What target would that be ? scenic_PYTHON and rtpmidi_PYTHON ? > Another issue is weak cleanup. During build, directories and files are > created, which are not cleaned up in the clean target. I have worked > around this in the packaging by forcefully removing the build directory, > so not urgent to fix, just would improve elegancy of upstream build > routines :-) > Yes, I am aware of that. Meanwhile, I am building with `git-buildpackage - --git-export-dir=../build-area`. > Another more annoying issue is that upstream autotools do not use > AM_MAINTAINER_MODE, causing normal builds to regenerate autotools if > "too old" which might happen accidentally, especially when using a VCS > as we do. The fix upstream is simple: Add AM_MAINTAINER_MODE to > configure.am and all should be fine. Until then we need to do a clumsy > workaround of preserving upstream autotools and restoring in our clean > rule. > I just filled a bug (#2) report upstream about it. It will be in the next release. #2: https://svn.sat.qc.ca/trac/scenic/ticket/589 > > Sorry for my silence - I have been busy with Real Life. I am really > excited about this package, as it seems to provide quite cool > functionality that I am really looking forward to play with :-) > Happy to read this. :) Our team really care about improving audio-video tools offer for GNU/Linux. We hope this package will be useful, and believe it really answers a need. (especially for live events and installations) Thanks for your help! Alex -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJMH34iAAoJEJQ0pOgl2qx1cmgP/2mM35SGOeV/ElfxmCNyIk4k 3z1wH8OZRgcDB5KlvBSPd5wK7dL0CW9IPSzZHVB7I9dzUkAsA0cx4aAIvTjFaxzK u4ex7Y2KvpivIiRRsow2c1iFommpPlH3aHh8o7t+aC6tOdMQdsDHBdPDAK15P63G v+BXLVhjOO74oK0uH4tlrptg3LG7B3UBJH4xRBijF5OtVayJf1SUferZMzUR7XcS klDIdK/Gyxz0CprZTPRlo6jcUjCU2vbpyxhwYIajhxrKqe295okL+WoVgFHNGJKn hmujBD6qQYAQauAUVR21eboNzmu5q7rNE06TLU66PUd78Xv/Uq08PUeUfGuatl6t 46TlCQjyDyyL8R/fDe1t8L4/HXWxIWlUChMvFDKZ6EPsBO1tXko1XmJ7Ivig5g04 9GR0bYPTkrwZydXJtBmCEjHzuHU1HdtDZdRC8IpHN0RIhDI3C+qjyw+TaIQwGw8R eJOceOhWUokuElNL/cF/gJR+RRlJD43ccMP/Q8vtGvTGWdMVXmevsTbG2XOuoRSy XnPst3BRrX4VGJ9gx2dv7eGVpn5z4ZXjmEcG1hLT6PN4JcCm5J0eYQLeVpt+0P2e 58hBOZdkqe35L4TfgtXA1cuzfwsP38lLMlbEebwiz3TRTpdLfRUcQ7qRHIyAvJ0s FdxY93Uip5EjKyl0TDDP =1iIi -----END PGP SIGNATURE----- _______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
