[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: aspell upgrade woes

On Tue, Jul 19, 2005 at 09:39:23PM -0700, Brian Nelson wrote:
> It's a C++ library and the ABI changed due to being compiled with GCC
> 4.0.

> [Actually, although it's written in C++, AFAIK it only exports a C
> interface so the transition may not have been necessary.  I only
> realized this yesterday though and I'm not entirely sure a
> non-transition would be safe.]

Heh.  I've just confirmed this...

As with libGLU, libaspell is used in enough places that there's a definite
benefit to not breaking package compatibility unnecessarily.  Since
libaspell15c2's shlibs refer to "libaspell15c2 (>= 0.60)", the only way to
provide full compatibility is with two real packages.  I would suggest
restoring libaspell15, and creating a dummy libaspell15c2 package that
depends on libaspell15 and can be dropped once everything has been rebuilt
to use libaspell15 again; that would minimize the disruption caused by the
flip-flopping of the lib name.

Brian, if you agree, I'm happy to prepare a patch.

Steve Langasek
postmodern programmer

Attachment: signature.asc
Description: Digital signature

Reply to: