Ahoy,
The binutils-dev package description does say
"This package includes header files and static libraries necessary to build 
programs which use the GNU BFD library, which is part of binutils. Note that 
building Debian packages which depend on the shared libbfd is Not Allowed."

I'm very curious about that remark at the end. Why are Debian packages 
prohibited from using this shared library in particular? Is it prescribed by 
Debian Policy? I really can't think of any problem.
I am interested for the sake of cross-Binutils packages like my 
binutils-sh-elf. If any of libbfd, libctf, and/or libsframe are 
target-independent in their functionality (and I believe they all are), then 
using those instead of rebuilding them all over sounds nice and would save disk 
space. Even ABI compatibility shouldn't be a concern; if necessary my package 
could enforce a dependency on libbinutils for a release version equal to that 
of binutils-source, so there would never be any drift.

Attachment: signature.asc
Description: This is a digitally signed message part

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to