> Dear debhelper maintainers,
>
> I just ran into the following cases, where one of my packages (haveged)
> started to FTBFS due to the following situation:
>
Hi Nicolas,
I am sorry to hear that our auto-detection broke for haveged.
> [...]
>
> The suggested fix -- calling `dh_makeshlibs --add-udeb=haveged-udeb` -- does
> not work, and I was forced to override to `dh_makeshlibs --no-add-udeb`
> instead.
>
Ok, I have added the following warning/hints to that case
> warning("Hint: Alternatively, if you have merged the
> shared lib package into $udeb_name and it has no");
> warning("Hint: other packages need to know of this
> library, then use \"--no-add-udeb\"");
And added the following note to the man page:
>
> This may be useful in case you do not want a shlibs file at all for the udeb
> because no package will depend on it. E.g. because adding a udeb package
> for the library was "overkill" and the library is embedded in a different
> udeb package.
Let me know if you have any suggestions for improvements to these texts. :)
>
> Since it seems reasonable for a udeb to ship the necessary libraries directly,
> rather than splitting them to a separate udeb, I would suggest the following:
> make `dh_makeshlibs` check not only whether FOO contains the same libraries as
> FOO-udeb, but also consider FOO's dependencies from the same source package.
>
>
> Best,
>
> nicoo
>
> [...]
>
While an interesting suggestion, I think this is beyond what I am
willing to invest in dh_makeshlibs auto-detection feature at the moment.
Among other because dh_makeshlibs cannot reliably detect what packages
depend on at that point and it quickly becomes a chicken-and-egg issue
(or might become in the future if #942134 is implemented).
Thanks,
~Niels
