Re: [Jeff Squyres <jsquyres@lam-mpi.org>] Re: LAM: LAM/MPI v7.1 released
- To: Camm Maguire <camm@enhanced.com>
- Cc: Josselin Mouette <joss@debian.org>, clustalw-mpi@packages.debian.org, xmpi@packages.debian.org, tessa-mpi@packages.debian.org, scalapack-lam-test@packages.debian.org, r-cran-rmpi@packages.debian.org, netpipe-lam@packages.debian.org, libxmpi4@packages.debian.org, libhdf5-lam-1.6.2-0@packages.debian.org, lampython@packages.debian.org, lam4-dev@packages.debian.org, lam-runtime@packages.debian.org, blacs1-lam@packages.debian.org, blacs-lam-test@packages.debian.org, debian-beowulf@lists.debian.org
- Subject: Re: [Jeff Squyres <jsquyres@lam-mpi.org>] Re: LAM: LAM/MPI v7.1 released
- From: Dirk Eddelbuettel <edd@debian.org>
- Date: Thu, 23 Sep 2004 08:15:14 -0500
- Message-id: <[🔎] 20040923131513.GA17555@sonny.eddelbuettel.com>
- In-reply-to: <[🔎] 54pt4djfv4.fsf@intech19.enhanced.com>
- References: <[🔎] 54acvi2nsy.fsf@intech19.enhanced.com> <[🔎] 1095876358.4248.15.camel@arrakis.localnet> <[🔎] 54pt4djfv4.fsf@intech19.enhanced.com>
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
Reply to: