Refile of https://github.com/Debian/debhelper/issues/8 to the Debian
BTS, where I am more likely to remember it exists. CC'ing Guillem
because he did the `dpkg-shlibdeps -l` transition and might shed some
light on whether the absolute path behaviour (still?) makes sense.
--- 8< --- Original message --- 8< ---
It took me forever to sort out why I was getting "dpkg-shlibdeps:
warning: cannot find library" for an internal library in my package,
even as I was using the -l parameter to point to it.
I eventually realized that by calling dpkg-shlibdeps -l directly it
would work fine. dh_shlibdeps wasn't passing along the -l as specified.
The workaround was to use -- and then pass -l directly to dpkg-shlibdeps
unchanged.
Looking into the code, dh_shlibdeps will prepend a slash to make the
path absolute. I also found that this used to be documented, but it's
been dropped from the man page.
This came up when I was using pdebuild, so maybe it's something related
to the chroot? I really don't know the reason for the absolute forcing
in the first place; it seems to work fine without.
Anyway, I'd at least restore the mention of relative paths being made
absolute in the man page, or reevaluate the forcing altogether.
--- 8< --- End message --- 8< ---
Last time we touched the -l parameter (AFAICT) was in
54bfb4207966f78b6412e84b12480e8a5c901cf6 (#717505) where Guillem Jover
moved the code around and migrated to `dpkg-shlibdeps -l`. The "force
path to be absolute" was present back (prior to that commit).
There is no remark about whether the "force absolute path" still made
sense with the transition to `dpkg-shlibdeps -l`, so I assume it did.
But this as far as I am willing to dig right now.
Best regards,
Niels