Moving kompare build to dh sequencer and libpkgs_gen_strict_local_shlibs

[Aurélien COUDERC]

Dear team,


I’m working on updating kompare and would like to move the build to using the dh
sequencer.


However the current d/rules uses this:
  libpkgs_gen_strict_local_shlibs = $(libpkgs_all_packages)
  include /usr/share/pkg-kde-tools/qt-kde-team/3/library-packages.mk

Reading through library-package.mk, I understand that it here forces the
dependencies to internal libraries to a = versioned dep in ${shlibs:Depends}.
This way kompare 4:18.08.1-1+b1 has a dep to:
  kpart5-kompare (= 4:18.08.1-1+b1)
and kpart5-kompare 4:18.08.1-1+b1 has a dep to:
  libkompareinterface5 (= 4:18.08.1-1+b1)

Question is how can I reproduce this behaviour with pure dh ?
Any existing examples ?


Also diffoscoping the existing packages and my new builds I noticed the
following diffs in shlibs:
- for kpart5-kompare:
│ │ ├── ./shlibs
│ │ │ @@ -1 +1 @@
│ │ │ -libkomparedialogpages 5 kpart5-kompare
│ │ │ +libkomparedialogpages 5 kpart5-kompare (>= 4:20.04.2)
- for libkompareinterface5:
│ │ ├── ./shlibs
│ │ │ @@ -1 +1 @@
│ │ │ -libkompareinterface 5 libkompareinterface5
│ │ │ +libkompareinterface 5 libkompareinterface5 (>= 4:20.04.2)

I guess this is due to the change explained in DH_MAKESHLIBS(1):
  In compat 12 and later, dh_makeshlibs defaults to -VUpstream-Version.  In
  compat 11 and earlier the default behaved like -VNone.

Is it something I should worry about ?
Should I override it with dh_makeshlibs -VNone ?


Thanks & happy hacking !
--
Aurélien