Re: openni package for Debian

2011-06-19 Thread Hans-Christoph Steiner


On Jun 1, 2011, at 6:57 AM, Cosimo Alfarano wrote:


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.


It would be nice to have the Mono stuff working, but I don't think it  
should be a blocker on getting the package uploaded.  So far, most of  
the useful stuff I've seen done with openni has not involved Mono/.NET/ 
C#.



- 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 :)


I fixed the man page complaints, tho the man pages I just made could  
definitely improved a lot.


.hc


- 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






If nature has made any one thing less susceptible than all others of  
exclusive property, it is the action of the thinking power called an  
idea, which an individual may exclusively possess as long as he keeps  
it to himself; but the moment it is divulged, it forces itself into  
the possession of everyone, and the receiver cannot dispossess himself  
of it.- Thomas Jefferson




___
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

2011-06-01 Thread Cosimo Alfarano
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

2011-06-01 Thread Cosimo Alfarano
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 package for Debian

2011-06-01 Thread Hans-Christoph Steiner


On Jun 1, 2011, at 6:57 AM, Cosimo Alfarano wrote:


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?


I don't know, but it shouldn't be too hard to test.


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.


 I guess currently, if we want to use the packages as-is without  
fixing the Mono stuff, we could add a Build-Conflicts.  But having the  
Mono stuff sorted out would be nicer. I just know next to nothing  
about Mono/C#/.NET.



- 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.


Sounds good, we might want to name the package that hints that they  
are kind of like utilities/debug tools too.  Things like a depth  
camera viewer, etc.



- 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.



Yup, glad to see progress.

.hc



“We must become the change we want to see. - Mahatma Gandhi


___
pkg-multimedia-maintainers mailing list
pkg-multimedia-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers