This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Holger Freyther holger at freyther.de> On 26 May 2016, at 07:30, Ruben Undheim <ruben.undheim at gmail.com> wrote: > > Hi Holger! > > Just a short answer from me this morning. thank you. Let me merge your better/great description, manpages and symbols. In regard to symbols files when and how to update it? Can you point me to the docs for that? > I don't have a total overview of the backwards incompatible discrepancies. I probably should have, but hopefully there aren't too many. It's okay, we can have a flag day once if we keep compat after. > No, I don't have any experience. But technically, it shouldn't be too hard. The debian dir in the upstream tarball will always be overwritten when building the package, so whatever you do there, will be invisible in the official package unless we manually merge it in. Okay, but it would be somehow nice if our descriptions will not drift too much and we re-use the same parts? Can you agree to that? >> - At least for OpenBSC you do not seem to package the -dbg symbols. As a developer I am always annoyed (e.g. with sofia sip) when I can't install the debug symbols. > > -dbg packages are now handled automatically by Debian. Any package with binaries, will automatically get "-dbgsym" packages. Just google it. This is also the case for Ubuntu AFAIK. This will however not be of any help for older Ubuntu and Debian releases (if you desire to support them also with -dbg symbols) finally! I never understood (okay compats) why so many packages don't have a -dbg(sym). Should -dbgsym packages be listed on https://packages.debian.org/source/sid/openbsc? So even when going to a mirror I don't see a -dbgsym package next to the other packages? Does one need to raise the compat version for it? > The extra debian dir is no problem. As said above, it will be overwritten automatically by the build tools when building the package. To move forward: we just pull interesting stuff from each other's debian dir. However, it may make sense to pull some things out of the debian dir and into the main source tree - for instance the man pages. Where would you put them? Makefile.am and install them? Shall we use asciidoc to generate manpages? holger