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
signature.asc
Description: This is a digitally signed message part.
-- https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-kde-talk
