[for debian-gcc people: please Cc: to me because I am not subscribed] On Fri, 16 Aug 2002 14:51:34 +0100, Matthew Wilcox <[EMAIL PROTECTED]> wrote: > * If your package contains no C++, do nothing. One fine day, > gcc-defaults will be changed to gcc-3.2 and you'll start using GCC > 3.2 with no work by yourself. 1. Does a C (not C++) library compiled with gcc 2.95 work with a C++ program compiled with gcc 3.2? 2. Does this mean I must not use gcc 3.2 before it becomes gcc-defaults? There may be a case where gcc 3.2 offers better optimization.
> * If you maintain a library written in C++, add a `c' to the end of > the name of your .deb, eg libdb4.0++.deb -> libdb4.0++c.deb. This > is similar in spirit to the glibc transition adding `g' to the end > of libraries. What does this "c" mean? -- Oohara Yuuma <[EMAIL PROTECTED]> Debian developer PGP key (key ID F464A695) http://www.interq.or.jp/libra/oohara/pub-key.txt Key fingerprint = 6142 8D07 9C5B 159B C170 1F4A 40D6 F42E F464 A695 Better just encrypt it all in your head :-). --- Derrick 'dman' Hudson, about encryption without any physical medium
