Thorsten Glaser <t...@mirbsd.de> writes: > (Were legal reasons the driving force behind adding Built-Using in the > first place?)
Yes, although not this particular issue. There are a set of packages that we build that use other packages as source during the build process. The most common are cross-compilation tool chains, but there are also some externally-maintained GCC frontends that incorporate GCC code at build time, etc. We needed a way to represent that the specific version of, say, GCC incorporated into that build was part of the source and therefore had to be retained in the archive until the binaries built from that source were replaced. At the time, though, the assumption was that Built-Using would be a fairly rare thing that would only be used for those few score packages that were Build-Depending on *-source packages. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87bo81mn7y....@windlord.stanford.edu
