[Raphael Hertzog 2007-08-03] > Adding reverse build-dependencies should be easy as everything is > generated based on the "Sources" files.
It would be a great start, to have an idea about the impact when thinking about changing or adopting a package by just looking at packages.qa.debian.org. :) > However, reverse dependencies on binaries is going to be a lot more > complicated... as it depends on the architecture, and you'll have to > download and parse the "Packages" files (which is currently not > done). > > And selecting a single arch and hoping that the rest is in sync will at > least create problems on some arch-specific packages. What about listing binary dependencies individually and showing in which architecture they are used, for example like this * hostname [amd64 i386] * binutils [i386] Can the CDD be used to extract this information? -- Happy hacking Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
