Re: Packaging of static libraries
- To: debian-devel@lists.debian.org
- Subject: Re: Packaging of static libraries
- From: Jakub Wilk <jwilk@debian.org>
- Date: Wed, 4 May 2016 13:14:36 +0200
- Message-id: <[🔎] 20160504111429.GA6769@jwilk.net>
- Mail-followup-to: debian-devel@lists.debian.org
- In-reply-to: <20160414160625.GA5077@jwilk.net>
- References: <20160410070536.GC31278@an3as.eu> <20160410141205.GI1850@belkar.wrar.name> <20160410155716.GE31278@an3as.eu> <CAKTje6HrvHeyHB7QSDJs774uhxa9y_j2GeMOm4r2jdpRYbWvfQ@mail.gmail.com> <20160410161536.GA12125@scru.org> <570ABCE3.9000207@debian.org> <20160410220505.GA9627@jwilk.net> <570AF123.6030708@debian.org> <20160414160625.GA5077@jwilk.net>
* Jakub Wilk <jwilk@debian.org>, 2016-04-14, 18:06:
It would be helpful if we could check if a dynamic binary is linked to
a static library from another package; but I'm not aware of any
reliable method to implement such check.
Maybe we could exploit the fact that static libraries are normally
stripped, unlike the freshly built code. So if there's large amount of
code that doesn't have corresponding debugging information in the
-dbgsym package, it might be because the binary is linked to a static
library.
--
Jakub Wilk
Reply to: