On Thu, Jun 09, 2005 at 12:35:17AM +0200, Matthias Klose wrote: > one more thing: C++ dependencies are currently "hidden" within > build-essential. Currently you cannot see this dependency from the > outside, if the code is not dynamically linked to libstdc++ (or > doesn't use libstdc++ at all). I'm proposing to require a build > dependency on a virtual package `c++abi2-dev', which will be provided > by g++-3.4/g++-4.0, which let's you specify this dependency > explicitely, at least for C++ sources, where binaries built from these > sources do not depend on libstdc++.
If this dependency is not required for actually building the package, I'm afraid it will be too often forgotten to be useful. Such a dependency really should be required for some technical reason IMHO. --Jeroen -- Jeroen van Wolffelaar [EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357) http://Jeroen.A-Eskwadraat.nl -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
