Hi Jose,

On 08/08/17 08:07, Jose Gutierrez de la Concha wrote:
> On Mon, Aug 7, 2017 at 4:47 PM, <jcowg...@debian.org
> <mailto:jcowg...@debian.org>> wrote:
>     To ensure that new executables will pull in the newer version of the
>     library built with GCC 7:
>     - Your library package should Build-Depend on g++ (>= 4:7).
> Do we really need the version here or is fine to just Build-Depend on
> g++? I will prefer to not
> have a version there as currently I share the same control file for
> several distributions were
> 4:7 is not available

Firstly, you shouldn't build depend on g++ without a version since it's
already build-essential.

For Debian, you can probably get away with not adding this dependency if
you wait some time (say a week?) for all the buildds to update to using
GCC 7 by default. Doing this is less robust though - for your other
distributions you will need to remember to do another shlibs bump if you
do switch to GCC 7.

>     - If your package does not provide a symbols file, add a dh_makeshlibs
>       override so that tight enough dependencies are generated.
>       Using libebml as an example (debian/rules):
>       + override_dh_makeshlibs:
>       +     # For new symbols when compiled with GCC 7
>       +     dh_makeshlibs -V'libebml4v5 (>= 1.3.4-2~)'
> Does this work with dbgsym generated packages?

dh_makeshlibs has nothing to do with dbgsym packages. I'm not sure I
quite understand your question.


Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to