Moving kompare build to dh sequencer and libpkgs_gen_strict_local_shlibs

[Pino Toscano]

In data domenica 28 giugno 2020 22:54:14 CEST, Aurélien COUDERC ha scritto:
> > Strictly speaking, you can do this without this makefile snippet;
> > however there are two downsides:
> > - you have to copy&paste the strict dependencies in all the binaries
> > - you hardcode the strict library dependencies, which means that if a
> >   binary either gains a dependency on another binary of the same source
> >   or it loses it, you have to update things manually; example:
> 
> Indeed, that second drawback was making me uncomfortable switching away from this, 
> as it would add maintenance overhead and risks of dependency relations bugs that would 
> be hard to catch.

I thing I forgot to mention: of course this is useful, and you indeed
will find it only in those few cases, only for sources with more than
one library/binary package.

> Bonus question : why do we need libkompareinterface5 and libkompareinterface-dev in 
> the first place ?

Possibly it was needed in the past, as many years ago libkomparediff2
was not split from kompare, and thus users (e.g. kdevelop) used to use
the development files from kompare, which were libkomparediff(2) and
libkompareinterface.

It looks like there are no users of it nowadays, so we might just fold
libkompareinterface5 into kpart5-kompare, and drop any development
stuff. If (and only if) there is any demand for that, re-evalutate it.

> Cannot we ship all the binaries in kpart5-kompare the same way konsole-kpart does and 
> skip shipping the headers entirely ?

Note that it is not exactly the same thing: konsole has no development
stuff.

-- 
Pino Toscano
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-kde-talk/attachments/20200629/764884f2/attachment.sig>