On Sun, Jun 15, 2003 at 03:23:37PM -0400, Anthony DeRobertis wrote: > In a perfect world, somehow the correct gcc would be used (to make sure > C++ ABI problems don't happen). Not sure if we can have that perfect world > or not; see below.
No, we can't. Not today, and definitely not a year ago. > >According to 2.4.2, the package should build correctly. It did. > >However, it didn't run because you had an incompatible version of apt > >installed. > > "If build-time dependencies are specified, it must be possible to build > the package AND PRODUCE WORKING BINARIES.... In particular, this means > that version clauses should be used rigorously in build-time > relationships so that one CANNOT PRODUCE BAD OR INCONSISTENTLY > CONFIGURE PAKAGES when the relationships are properly satisfied." > (Policy 2.4.2, Emphasis added) > > 2.4.2 says the package has to work, too. Er, no. Those binaries would work perfectly fine if you had built apt with the same C++ ABI. But I can't specify in a build-dependency "oh, and your apt must be built with the same C++ ABI". I _certainly_ can't do so retroactively. I am bothered by the implication that I did something wrong in building the python-apt package for woody. -- - mdz
