Re: primesense-nite-nonfree should install resulting package?
On 20/06/11 23:40, Hans-Christoph Steiner wrote: With the primesense-nite-nonfree, it downloads the binary and generates the openni-module-primesense-nite-nonfree_1.3.1.5-1_i386.deb package but it doesn't install it afterwards. It seems to me that it should install it automatically, since that's the only purpose of installing primesense-nite-nonfree. How does that sound? I didn't do it in the beginning to avoid problems with the licence, just in case (out of ignorance and lack of time to check :). Feel free to add it. What the package actually needs is a sort of sha256 checksum like flashplugin does, but yeah installing the new package is only a line :) C. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni package for Debian
On 31/05/11 03:49, Hans-Christoph Steiner wrote: Ah, cool, so we have an uploader :) I'm just a DM. I'm not sure about Cosimo. I'm a DD. BTW, update to the pkgs status: I tried yesterday the three repos, they worked. I just pushed a couple of patches to fix small (but necessary) things. I just realized that we need to fix the .ini file for Kinect, I had to change InputFormat=1 which was commented, to make it work. Also, udev rules, does anybody know if we need OWNER=root or it can be xxx as set by upstream? Next steps: - Enable Mono in openni so that it can be re-enabled in NITE. - the Makefile for NITE OpenNI relies on the presence of the mono exec to compile mono, which means that in a chroot env it compiles without problems, but when build outside in an env which has mono installed it will fail. The reason of the failure is that the upstream install.sh script do not detach the build from the (post) installation process. As per my mono understanding (noob) we need to compile GAC in postinst, while create the DLL at build time. Until we split this behaviour (should be easy) we cannot build mono package and both openni and NITE are inherently broken. - Re-enable quilt, so that we can patch the Samples to be able to find their XML in a different location than ../../../../Data, and package it as openni-samples, the same for nite and kinect IIRC. - Fix all the lintian complaints and the .ini :) - Fix the SONAME and .so versioning issue, it depends on the email I still have to send to upstream about their build system :) So far this is not a real problem, until we'll have more than one version we need to be able to link at the same time. After that we might be able to consider an upload to unstable, IMHO. cheers, C. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni package for Debian
On 01/06/11 11:57, Cosimo Alfarano wrote: - Fix the SONAME and .so versioning issue, it depends on the email I still have to send to upstream about their build system :) So far this is not a real problem, until we'll have more than one version we need to be able to link at the same time. Adding a point: - upstream uses tinyXML, having its src embedded in the repo. We should try to use, as per policy, the libTinyXML provided by Debian instead, which makes easier the (security) updates related to this lib. Otherwise we should strictly monitor tinyxml reports and fix them ourselves if upstream is not responsive on that. This is not a blocker for unstable, though. cheers, Cosimo. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: openni and primesense/kinect status
On 30/05/11 18:53, Hans-Christoph Steiner wrote: Yeah, the upstream source is a mess for all this, there are mostly no [...] So, on that note, the optimization flags are in the upstream build system. It's on my TODO list to contact upstream and ask the rationale behind the current build system. I'll write the email in the next days, but if someone is planning to do the same please put me in CC. C. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
