On Wed, 08 Jun 2011 03:07 +0200, "Jochen Sprickerhof"
> * Hans-Christoph Steiner <h...@eds.org> [2011-06-07 18:47]:
> > On Jun 7, 2011, at 6:44 PM, Jochen Sprickerhof wrote:
> > >* Hans-Christoph Steiner <h...@eds.org> [2011-06-06 13:05]:
> > >>
> > >>I have not been in contact with avin. Is Bayer images support
> > >>something that is in the original from PrimeSense, or something that
> > >>you want added? If the idea is to maintain new features in the
> > >>package, I think that should probably be done in a separate git repo
> > >>to keep the development and the packaging separately. If you want
> > >>to maintain a fork of the primesense/sensor repo, we could base the
> > >>package off of that for now.
> > >
> > >it's something we have added. Should we put it on github and merge it
> > >with the avin2 branch?
> > That works for me.
> Here it is: https://github.com/ros-pkg-git/Sensor/tree/master. It's not
> based on the avin2 branch (as they are not really based to the official
> OpenNI once), let me know if you that's ok for you. By the way, why is
> the Debian git not connected to the github one? I mean this one:
These packages are packaged using standard Debian git-buildpackage
style. That means that the upstream code is imported from release
tarballs, and the git master branch is all about the debian packaging.
That's why this repo is not a fork of the upstream repo.
So if we decide to make primesense-kinect-sensor based off of your git
fork, then a release tarball would need to be imported using
git-import-orig. I'm thinking perhaps its a better idea if you make a
separate package of your fork. I used the avin2 fork rather than the
offical repo for this package because it seems that the official sources
don't fully work. It should be really easy to create a ros package
since the code is so close. It could be something like
primesense-kinect-sensor-ros or whatever.
pkg-multimedia-maintainers mailing list