On 11/25/2013 06:52 AM, Hauke Wintjen wrote:
Hans-Christoph Steiner h...@eds.org hat am 23. November 2013 um 18:43
geschrieben:
On 11/22/2013 05:55 AM, Jochen Sprickerhof wrote:
Hi,
* Hauke Wintjen hwint...@rimpl-consulting.de [2013-11-21 09:30]:
Hans-Christoph Steiner h...@eds.org
Hans-Christoph Steiner h...@eds.org hat am 23. November 2013 um 18:43
geschrieben:
On 11/22/2013 05:55 AM, Jochen Sprickerhof wrote:
Hi,
* Hauke Wintjen hwint...@rimpl-consulting.de [2013-11-21 09:30]:
Hans-Christoph Steiner h...@eds.org hat am 20. November 2013 um 20:13
On 11/22/2013 05:55 AM, Jochen Sprickerhof wrote:
Hi,
* Hauke Wintjen hwint...@rimpl-consulting.de [2013-11-21 09:30]:
Hans-Christoph Steiner h...@eds.org hat am 20. November 2013 um 20:13
geschrieben:
Also, what tool are you building it with? I couldn't get it to build with
either
Hi,
* Hauke Wintjen hwint...@rimpl-consulting.de [2013-11-21 09:30]:
Hans-Christoph Steiner h...@eds.org hat am 20. November 2013 um 20:13
geschrieben:
Also, what tool are you building it with? I couldn't get it to build with
either dpkg-buildpackage or git-buildpackage.
I have
Hi.
Hans-Christoph Steiner h...@eds.org hat am 20. November 2013 um 20:13
geschrieben:
The first thing that needs doing is the debian/copyright file. All of the
various licenses of the code that are included in the openni source release
need to be marked in there, or the Debian
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2013-11-21 09:30, Hauke Wintjen wrote:
Why do you change the SONAME from upstream? That's a pretty
unusual thing to do.
patches/0001-Add-SONAME-to-libraries.patch
Because upstream does not add a SONAME and jsprickerhoff had it in
its
* IOhannes m zmoelnig zmoel...@iem.at [2013-11-21 10:37]:
it's always best to follow upstream as closely as possible (as long as
they make sane assumptions :-)), esp. in picky areas like SONAMEing.
if your package has not been in debian yet (which i think is true),
you should get rid of any
On 11/21/2013 04:41 AM, Jochen Sprickerhof wrote:
* IOhannes m zmoelnig zmoel...@iem.at [2013-11-21 10:37]:
it's always best to follow upstream as closely as possible (as long as
they make sane assumptions :-)), esp. in picky areas like SONAMEing.
if your package has not been in debian yet
The first thing that needs doing is the debian/copyright file. All of the
various licenses of the code that are included in the openni source release
need to be marked in there, or the Debian ftp-masters will reject the package.
So things like in the ThirdParty/ folder. Check out the
