From: Jason Wever <weeve@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] OpenLDAP 2.2 series
Date: Thu, 19 May 2005 09:40:48 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0505190935190.12177@stargazer.weeve.org> (raw)
In-Reply-To: <20050430234458.GA1804@curie-int.orbis-terrarum.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sat, 30 Apr 2005, Robin H. Johnson wrote:
> It shouldn't cause any problems for anybody that has OpenLDAP installed
> as a client only, but it's a bit bumpy for those that are running
> OpenLDAP servers.
Before this package goes stable, I'd like to suggest that backwardly
compatible libraries be provided so that applications aren't horribly
broken by this upgrade (similar to how we've done for openssl in the past).
On two different test systems, this upgrade caused broken dynamic library
dependencies in over 35 packages on each system. I'm going to hazard a
guess that a majority of systems that have openldap installed have more
than one or two packages depending on openldap (and probably aren't
dedicated LDAP servers). For those folks who use LDAP for various thing,
I could see this as being a very big gotcha.
Cheers,
- --
Jason Wever
Gentoo/Sparc Co-Team Lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCjLOCdKvgdVioq28RAkbiAJ0RWLtV2T8TFuvXUriJVoPu4eAYIQCguPmW
k/vPBXhefN2Gf7fop50laoE=
=VtpG
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-05-19 15:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 23:44 [gentoo-dev] OpenLDAP 2.2 series Robin H. Johnson
2005-05-01 0:00 ` Grant Goodyear
2005-05-02 13:39 ` Chris Gianelloni
2005-05-02 15:08 ` Grant Goodyear
2005-05-17 9:48 ` Robin H. Johnson
2005-05-19 15:40 ` Jason Wever [this message]
2005-05-19 20:16 ` Robin H. Johnson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.63.0505190935190.12177@stargazer.weeve.org \
--to=weeve@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox