RE: [JunkMail] Re: sasl version mismatch: 2.1.15 vs 2.1.17

["Howard Chu" <hyc@highlandsun.com>]

> -----Original Message-----
> From: owner-openldap-software@OpenLDAP.org
> [mailto:owner-openldap-software@OpenLDAP.org]On Behalf Of Andreas

> On Tue, Dec 09, 2003 at 01:16:13PM -0800, Howard Chu wrote:
> > As an example, BDB 4.1.17 changed its db_open API and added
> an additional
> > parameter in the middle of the parameter list. The API is completely
> > incompatible with what came before it, but the minor
> version is still the
> > same. The version number is > 4.0 so we should be happy
> with it, from a
>
> This is an example of a vendor (Sleepycat) who doesn't care
> about incompatible
> changes between minor release. Bad cat :)

These were early (pre-release) BDB versions, so I don't think it's any fault
on their part. We were lucky to get advance access so we could get our code
working with theirs quickly.

> With this type of vendor one cannot rely on the soname (if it
> contains only
> the major version) at all. That's why I asked if cyrus-sasl
> had such behaviour
> in the past.

Much as I like Linux, there's more to the world than just that. Not all
platforms that support shared libraries use sonames or versioning of any
kind. To think that there is a simpler, straightforward solution to this mess
is missing the larger picture.

  -- Howard Chu
  Chief Architect, Symas Corp.       Director, Highland Sun
  http://www.symas.com               http://highlandsun.com/hyc
  Symas: Premier OpenSource Development and Support