[Steve, my apologies for the private copy if you are subscribed to -x.]
On Fri, Aug 27, 2004 at 11:48:28PM -0700, Steve Langasek wrote:
> severity 268461 minor
> thanks
>
> This is hardly a serious bug -- the xfree86 package build-depends:
> libstdc++5-dev | libstdc++-dev, which is always satisfied by
> build-essential, so there is zero impact on the buildability of the
> package, even accounting for sbuild's peculiarities in resolving
> dependencies.
Okay, I'm tired of getting griped at about this issue by various people, so
I looked up why I originally made this change in the first place. :)
It was done back in 4.2.1-5, which just barely predates the import of
XFree86 packaging into Subversion for revision control, but fortunately my
chatty changelog entries have come to the rescue:
xfree86 (4.2.1-5) unstable; urgency=low
[...]
* debian/control:
- add Build-Dependency on libstdc++5-dev (for libGLU in xlibmesa3-glu)
[...]
- C++ ABI 1.02 transition / Mesa 5.0 awareness:
+ xlibmesa3, xlibmesa3-dbg, xlibmesa-dev split into:
xlibmesa3-gl, xlibmesa3-gl-dbg, xlibmesa-gl-dev,
xlibmesa3-glu, xlibmesa3-glu-dbg, xlibmesa-glu-dev (Closes: #175157)
+ xlibmesa3-gl conflicts with and provides libgl1 (pure virtual package)
+ xlibmesa3-gl replaces mesag3 and xlibmesa3
+ dropped old replacement of xserver-xfree86 (<< 4.0.2) by xlibmesa3;
those versions of xserver-xfree86 are long dead and were never part of
a stable Debian release
+ xlibmesa3-gl-dbg depends on exact same version of xlibmesa3-gl
+ xlibmesa3-gl-dbg conflicts with and replaces xlibmesa3-dbg
+ xlibmesa-gl-dev conflicts with and provides libgl-dev (pure virtual
package)
+ xlibmesa3-glu conflicts with and provides libglu1 (mixed virtual
package)
+ xlibmesa3-glu replaces mesag3 (<< 5.0.0-1) and xlibmesa3
+ xlibmesa3-glu-dbg depends on exact same version of xlibmesa3-glu
+ xlibmesa3-glu-dbg conflicts with and replaces xlibmesa3-dbg
+ xlibmesa-glu-dev depends on libstdc++5-dev and libc6-dev | libc-dev
+ xlibmesa-glu-dev conflicts with xlibmesa-dev and libglu-dev (pure
virtual package)
+ xlibmesa-glu-dev provides libglu-dev (pure virtual package)
+ xlibmesa-glu-dev replaces mesag-dev (<< 5.0.0-1) and xlibmesa-dev
+ dropped dependency on xlibmesa3 from xlibosmesa3 (was redundant
anyway, shlibs files work fine within the build)
+ added dependency on xlibs-dev to xlibosmesa-dev, since libOSMesa links
against Xlib and Xext
+ x-window-system-core metapackage depends on xlibmesa3-gl and
xlibmesa3-glu instead of xlibmesa3
+ xlib*mesa* package descriptions tweaked
[...]
-- Branden Robinson <branden@debian.org> Tue, 21 Jan 2003 12:02:40 -0500
It looks like I added the build-dep on libstdc++5-dev (which I later
broadened to include an alternative on libstdc++-dev) because I needed to
add a regular dependency to xlibmesa-glu-dev.
Generally, if you're shipping a -dev package that depends on a C library
-dev package, your source package depends on that C library as well, to
build.
The fact that libstdc++ (some real package providing it, rather) is
build-essential is persuasive to me, and I'd be happy to drop it.
*However*, we have a magical mystical C++ ABI shuffle going on. GCC 3.2
provides libstdc++5-dev. GCC 3.3 provides libstdc++5-3.3-dev. GCC 3.4
provides libstdc++6-0-dev.
For xlibmesa-glu-dev's Depends: line to be accurate, don't I need to
preferentially build-depend on the same C++ library?
It has been my understanding that sarge is supposed to use the GCC 3.3 C++
ABI, and not GCC 3.4's. But I may be wrong, as I cannot find any such
delcaration at <URL: http://release.debian.org/sarge.html >.
Advice wanted, please!
--
G. Branden Robinson | It's not a matter of alienating
Debian GNU/Linux | authors. They have every right to
branden@debian.org | license their software however we
http://people.debian.org/~branden/ | like. -- Craig Sanders
Attachment:
signature.asc
Description: Digital signature