* Dmitry Katsubo <dm...@mail.ru>, 2011-01-28, 13:03:
1. A few types and constants defined in cuneiform.h have very generic
names ("enum Languages", "Bool", "LANG_ENGLISH" etc.). This is not
something acceptable in a public header file, and these names could
easily conflict with other names in user's code.
Yes, this might be a problem, and I am already facing this problem with
other libraries. If you can, please, raise this question in mainstream,
Forwarded:
https://bugs.launchpad.net/debian/+source/cuneiform/+bug/710783
in particular, adding a CPP namespace for all declared types.
I won't advocate this part. The header file currently works with plain C
and I see no reason to give it up.
2. SONAME is currently "libcuneiform.so.1.0.0". Does it mean that it's
going to be "libcuneiform.so.<upstream-version>", i.e. changing with
every upstream release? That would mean that with every upstream
release:
- Debian package would have to pass through the NEW queue.
- Packages linking to the shared library (if any) would have to be rebuilt.
This is not something I'd be happy about. SONAME should change if and
only if the new version actually breaks API.
You're absolutely right here: the SO version number should be increased
only when API changes. So do not change it with every upstream release
(perhaps only the minor number).
Forwarded upstream as well:
https://bugs.launchpad.net/debian/+source/cuneiform/+bug/710814
--
Jakub Wilk
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
