Greetings! OK, I've gone through the following per the recommendation of upstream:
mpi.h lam_config.h include/mpi2cxx/* and there appears to be nothing in the diff between 7.0.6 and 7.1 which would break backward binary compatibility in this case. I think I should release 7.1 with the same soname=4. If anyone strenuously objects, I'll be happy to reconsider, but please let me know ASAP so we don't miss our chance to migrate the latest into Sarge. Take care, Dirk Eddelbuettel <[EMAIL PROTECTED]> writes: > On Thu, Sep 23, 2004 at 09:04:47AM -0400, Camm Maguire wrote: > > > When there are such binary incompatibilities between every single > > > version of a library, the best solution is probably to change the SONAME > > > and package name between each versions, just like for libhdf5 of > > > libdirectfb. It's a hassle to rebuild all depending packages, but this > > > way you're sure there's no problem. > > > > This is definitely a possible policy. What do you think of a slightly > > looser policy -- to bubmp the Debian-specific soname when any of the > > headers or related files have changed between releases? Upstream > > mentioned three specific files in the original note. > > IMHO this would be sufficient. Let's face it, lam/mpi isn't quite as widely > used as libstdc++ -- so we don't have to go multiple versions "just because > we can". > > Just my $0.02. > > Dirk > > > -- > Those are my principles, and if you don't like them... well, I have others. > -- Groucho Marx > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > > > > -- Camm Maguire [EMAIL PROTECTED] ========================================================================== "The earth is but one country, and mankind its citizens." -- Baha'u'llah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
