From owner-freebsd-current@FreeBSD.ORG Wed Aug 23 10:12:29 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 742DC16A4DD for ; Wed, 23 Aug 2006 10:12:29 +0000 (UTC) (envelope-from Alexander@Leidinger.net) Received: from www.ebusiness-leidinger.de (jojo.ms-net.de [84.16.236.246]) by mx1.FreeBSD.org (Postfix) with ESMTP id DC4F943D45 for ; Wed, 23 Aug 2006 10:12:28 +0000 (GMT) (envelope-from Alexander@Leidinger.net) Received: from Andro-Beta.Leidinger.net (p54A5E135.dip.t-dialin.net [84.165.225.53]) (authenticated bits=0) by www.ebusiness-leidinger.de (8.13.6/8.13.6) with ESMTP id k7N9s4lw025443; Wed, 23 Aug 2006 11:54:07 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from localhost (localhost [127.0.0.1]) by Andro-Beta.Leidinger.net (8.13.4/8.13.3) with ESMTP id k7NABwqe091419; Wed, 23 Aug 2006 12:11:58 +0200 (CEST) (envelope-from Alexander@Leidinger.net) Received: from psbru.cec.eu.int (psbru.cec.eu.int [158.169.131.14]) by webmail.leidinger.net (Horde MIME library) with HTTP; Wed, 23 Aug 2006 12:11:57 +0200 Message-ID: <20060823121157.yawh6f8e844w4osc@netchild.homeip.net> X-Priority: 3 (Normal) Date: Wed, 23 Aug 2006 12:11:57 +0200 From: Alexander Leidinger To: Michael Bushkov References: <44E9582C.2010400@rsu.ru> <44EAA213.6010507@delphij.net> <002901c6c5ba$628b67d0$9800a8c0@carrera> <86hd0423zk.fsf@xps.des.no> <44EB302A.7010106@rsu.ru> In-Reply-To: <44EB302A.7010106@rsu.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable User-Agent: Internet Messaging Program (IMP) H3 (4.1.2) / FreeBSD-4.11 X-Virus-Scanned: by amavisd-new Cc: Dag-Erling =?utf-8?b?U23DuHJncmF2?= , freebsd-current@freebsd.org, LI Xin Subject: Re: [HEADS UP]: OpenLDAP+nss_ldap+nss_modules separated patch and more (SoC) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Aug 2006 10:12:29 -0000 Quoting Michael Bushkov (from Tue, 22 Aug 2006 =20 20:26:18 +0400): > Dag-Erling Sm=C3=B8rgrav wrote: > >> "Michael Bushkov" writes: >> >>> Li Xin wrote: >>> >>>> Would you please consider having the imported OpenLDAP to install >>>> shared objects under alternative names? It might be painful for >>>> users who wants OpenLDAP installation from the ports collection >>>> (as OpenLDAP team moves fast and fixes bug from time to time) if >>>> they get a same library in /usr/lib... >>>> >>> I've been thinking about that. Would names like "libldap_i.so" and >>> "liblber_i.so" be ok ("_i" means "imported", or "internal")? >>> >> >> Please don't. If somebody isn't happy with the base system's libldap, >> they can add WITHOUT_LDAP to their make.conf. >> >> DES >> > This issue turned to be more complex than I originally expected. I > believe that "not having 2 different entities in the system, that do > the same thing" is the good rule. So maybe, leaving libldap.so(a) in > /usr/lib is not an absolutely good decision. But renaming libldap to > some other name and leaving it there (and enforcing everything beside > the base system to use almost the same ports' libldap) is probably much > more worse. > So, after all, I'd prefer to leave libldap (and nss_ldap, which can > also conflict with PADL's nss_ldap) as is and let users use > WITHOUT_LDAP and WITHOUT_NSS_LDAP when appropriate. If someone doesn't like the base system libldap, but wants the =20 nss_ldap stuff, this way will not work out. While building the base =20 system, no 3rd party libs are known to the build infrastructure. Conflicting libs aren't good and some people may want to have more =20 recent versions of a lib installed. To solve this issue phk didn't =20 importet "libxml", but renamed it to "libbsdxml" (we only need to =20 update the lib if we need a new feature, or if there's a security =20 problem). This way base system tools are able to use a XML lib while =20 ports can use a more recent version of it (ports aren't using our =20 version of the lib). So this is not like the openssl or kerberos cases from the =20 lib-handling point of view (I'm talking about the ports<->basesystem =20 interaction, not about updating the lib in the basesystem). An idea which wasn't suggested yet is to install a renamed version (I =20 would suggest libbaseldap instead of libbsdldap or libldap_i, but I =20 don't really care about the name) and a link from the original name =20 (only the .so and .a, but not the .so.X) to the new name. This link =20 can be protected with a WITHOUT_LIBLDAP_LINK switch (or the other way =20 around... depending on what we want to achieve). This way it is =20 possible to link with the renamed lib in the base system, to use the =20 base system version of the lib in ports, and to use the lib from ports =20 if desired (a recompile of ports may be needed in the last case, yes). Bye, Alexander. --=20 The gent who wakes up and finds himself a success hasn't been asleep. http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID =3D B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID =3D 72077137