Thorsten Glaser <t...@mirbsd.de> writes: > In this specific case, there are one to two statically linked programs > there. In some cases, they link statically against a GPL licenced > library. So my current interpretation of the text from Policy above says > that Built-Using is indeed required there.
Per previous discussion on debian-devel, the Policy text is too aggressive and, read literally, encourages people to do things we definitely do not want them to do, such as add Build-Using for libgcc. We need to get the Policy text fixed. In the meantime, please don't add Built-Using for libgcc. The libgcc license does not require it, due to the runtime exception, and essentially every package in the archive would acquire a Built-Using if it were used for libgcc. I haven't looked at the situation for static linking with eglibc or the other libc implementations you reference. The general consensus on debian-devel (at least as I understood it) was to only use Built-Using when there's some licensing reason why we need to keep the referenced package. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
