getting openni2 into Debian

IOhannes m zmoelnig zmoelnig at iem.at
Thu Nov 21 09:37:55 UTC 2013


-----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 openni package (from which i started) and suggested to me to
> add this patch also.
> 
> Then for the debian-develop branch (2.3.x) they changed one api
> incompatible so i incremented it from the debian-master branch
> (2.0.x - 2.2.x).

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 hacks like renaming SONAME, as long as this
is still easily possible.


fgamsdr
IOhannes
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iQIcBAEBCAAGBQJSjdRvAAoJELZQGcR/ejb4DboP/i2Ek8PiwPvSLdtYQdOP4bwY
+5q9hV6zA1+cne8pf4tMjNmh8hefHRVa068DZNXesQcIVFyb3wluZUykNAcC+Tfx
MpySJvuFrCl7JOlrY7TbqI9EhgD8rxqIsdqqpziAHHfq8War+J88Su1fcOny/sFn
nqVpZ/73z8QC7OlbwAC8IPWq/A74khcjwNjmxutKxHhYxTyRG2kvewVA6xJF0bfL
H0NEigjcyqk8kGqrDLPtqU4i4YAngIty/XvcdT1Jkg9wCcDu+wotkOukZMuIOSDq
B83jtlTeYyfOmttqknvkgGMiW3ml/XBmCrActXsIjPPo+SPBbFqI9ik9OBd9Sc/A
lWDAXLe2IZp+n/OL9cQ3Gaum9G6VzQHSu0TVZiSwjJ2IZUExDjWPft95kRraQEqx
dlRA2qsjaQu+rxrn2zxHYy8TcT3YLN1m+GWWhADlzh6db84IIFdA4b1g7qdp6anh
V58WLyxmUcuDOVWrlpZAqgcBHIZXegMjmkjYQCw9PsfFGn7K1+Ebp8jPIeVwn3Xc
+EAe4/6hjy/SEbIBWpPI3xKpa6+s89eMURv9gNt7pLRRPV38JBXXPDzBd8KNXL1Q
rbKJit2Xa85fbUzUWVgAoFTeOery5jXk9r3Z/ikDNOuiXoQ9RhbChm7gRWLGR98c
Zqo5v8jQxgUamUCr5Y6c
=LhRW
-----END PGP SIGNATURE-----



More information about the pkg-multimedia-maintainers mailing list