Bug#971243: sysprof: Split to separate binary packages

[Simon McVittie]

On Sun, 27 Sep 2020 at 19:46:38 -0400, Jeremy Bicha wrote:
> We should split sysprof into separate packages, a library package, a
> development headers package, etc.

I've already taken the first step by giving sysprof some versioned
Provides:

- libsysprof-4
- libsysprof-4-dev
- libsysprof-capture-4-dev
- libsysprof-ui-4
- libsysprof-ui-4-dev

and making the two shared libraries generate dependencies on the virtual
packages libsysprof-4 and libsysprof-ui-4, instead of on sysprof.

(Note that libsysprof-capture-4 is static-only, so there is no shared
library for that one.)

Perhaps splitting the development files is overkill and it would be better
to have libsysprof-4-dev contain all three sets of development files?
I think the two shared libraries ought to be packaged like proper shared
libraries in separate binary packages, though.

Note that they have odd SONAMEs (libsysprof{,-ui}-4.so) so they are not
necessarily compatible with legacy shlibs files, but symbols files can
represent this situation fine, so I don't think we need to ask upstream
for a SONAME change.

    smcv