Re: [PATCH] Fix lintian errors, make .deb build multiarch-aware

On Wed, Jul 9, 2014 at 1:29 AM, Max Suraev wrote:

>  debian/...

If you would like any osmocom packages uploaded to Debian, I would be
happy to sponsor them.

Of course the usual Debian requirements apply; free licenses, source,
proper ABI tracking etc.

--

-- 
bye,
pabs

https://wiki.debian.org/PaulWise

Re: [PATCH] Fix lintian errors, make .deb build multiarch-aware

On Wed, Jul 9, 2014 at 12:09 PM, Paul Wise wrote:
> On Wed, Jul 9, 2014 at 1:29 AM, Max Suraev wrote:
>
>>  debian/...
>
> If you would like any osmocom packages uploaded to Debian, I would be
> happy to sponsor them.

I should mention that there are two source packages from OsmoSDR in
Debian, these were uploaded by the Debian Gnuradio package
maintainers:

https://packages.debian.org/source/sid/gr-osmosdr
https://packages.debian.org/source/sid/libosmosdr

--

-- 
bye,
pabs

http://wiki.debian.org/PaulWise

Re: [PATCH] Fix lintian errors, make .deb build multiarch-aware

On Wed, Jul 09, 2014 at 12:09:56PM +0800, Paul Wise wrote:

Hi,

> Of course the usual Debian requirements apply; free licenses, source,
> proper ABI tracking etc.

the debian maintainer guide is painful to read. Can you point me to
how ABI tracking should be implemented?

Re: [PATCH] Fix lintian errors, make .deb build multiarch-aware

On Wed, 2014-07-09 at 13:21 +0200, Holger Hans Peter Freyther wrote:

> the debian maintainer guide is painful to read. Can you point me to
> how ABI tracking should be implemented?

It is pretty simple; when library ABI is broken (when new code is
binary-incompatible with old code) the library SONAME (libc.so.6 for
example) should be bumped. The ABI Compliance Checker (ACC) can help
analyse the ABI and report incompatible changes but doesn't cover every
situation AFAIK. The libtool manual has a bunch of useful information
about maintaining shared libraries. 

http://ispras.linuxbase.org/index.php/ABI_compliance_checker
https://www.gnu.org/software/libtool/manual/libtool.html

For the Debian side of library packaging, maint-guide covers the very
basics, debian-policy covers requirements and the (quite outdated,
possibly still useful) libpkg-guide covers library packaging generally.

https://www.debian.org/doc/manuals/maint-guide/advanced.en.html#library
https://www.debian.org/doc/debian-policy/ch-sharedlibs.html
http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html

Two things I would like to highlight in particular:

Debian likes library upstreams who set their default symbol visibility
to hidden and then whitelist their public symbols.

Debian likes library upstreams who implement symbol versioning.