I help maintain the capnproto Debian packages. Debian bug #720063 (the
original ITP) may be relevant to this discussion:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720063

C++ mangled symbols are arch dependent & c++filt wasn't playing nice.
Then I stumbled across this part of the Debian Policy Manual:

https://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s
-sharedlibs-depends

Specifically:

"However, maintaining exhaustive symbols information for a C++ library
can be quite onerous, so shlibs files may be more appropriate for most
C++ libraries. Libraries with a corresponding udeb must also provide a
shlibs file, since the udeb infrastructure does not use symbols files."

And this:

http://www.eyrie.org/~eagle/journal/2012-02/001.html

"In the end, I reverted the changes and have gone back to not providing
a symbols file, and instead just using shlibs."

At this point we opted out of the symbols file as far as the Debian
packages were concerned. Open to patches if symbols can be easily
maintained, but it sounds like others have been down that road &
struggled.


** Bug watch added: Debian Bug tracker #720063
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720063

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to capnproto in Ubuntu.
https://bugs.launchpad.net/bugs/1367551

Title:
  [MIR] capnproto

Status in “capnproto” package in Ubuntu:
  Incomplete

Bug description:
  Can we please include this in main? unity-scopes-api has a dependency
  on capnproto.

  Source and bug tracking for this are here:
  https://github.com/kentonv/capnproto

  There are no dependencies other than C++ 11 (gcc 4.7 or later work).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/capnproto/+bug/1367551/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to