Re: Procedure reminders on updating a lib package for a C++ ABI change
Steve Langasek <firstname.lastname@example.org> writes:
> On Sun, Jul 17, 2005 at 06:22:21AM +0200, Goswin von Brederlow wrote:
>> Steve Langasek <email@example.com> writes:
>> > On Sat, Jul 16, 2005 at 02:44:03PM +0200, Ralf Treinen wrote:
>> >> I have a (probably very stupid) question:
>> >> On Sat, Jul 16, 2005 at 03:09:18AM -0700, Steve Langasek wrote:
>> >> > If one of your packages needs to be transitioned, DO NOT upload it before
>> >> > the C++ libraries it depends on have successfully made the transition.
>> >> Is there an easy way to find out which of the libraries a package
>> >> depends are C++ libraries, and which are not?
>> > grepping for libstdc++ in the deps is usually a good indicator, although
>> > apparently that will cause false-positives *and* false-negatives. :/ You
>> > could also try grepping for '::' in the -dev package's headers, which may be
>> > more reliable. :)
>> The grep would catch cases where c++ is used but not exported. See the
>> libGLU stroy in this thread for an example. I think the libstd++ false
>> positives would be caused by the same.
> $ grep :: /usr/X11R6/include/GL/glu.h
Oh, right. The -dev package shouldn't contain internal headers with
c++ stuff. Sorry.