From owner-freebsd-ports@FreeBSD.ORG Thu May 15 16:35:48 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 99CFF37B401 for ; Thu, 15 May 2003 16:35:48 -0700 (PDT) Received: from mx2.fillmore-labs.com (lima.fillmore-labs.com [62.138.193.83]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E23B43F93 for ; Thu, 15 May 2003 16:35:47 -0700 (PDT) (envelope-from eikemeier@fillmore-labs.com) Received: from pd951af13.dip.t-dialin.net ([217.81.175.19] helo=fillmore-labs.com ident=2bnh17uu8jl39hc6) by mx2.fillmore-labs.com with asmtp (TLSv1:AES256-SHA:256) (Exim 4.20) id 19GSGG-000C5z-1u; Fri, 16 May 2003 01:35:44 +0200 Message-ID: <3EC4244D.4050901@fillmore-labs.com> Date: Fri, 16 May 2003 01:35:41 +0200 From: Oliver Eikemeier MIME-Version: 1.0 To: Christian Kratzer References: <3E91776B.40602@fillmore-labs.com> <20030409084948.Q16956@majakka.cksoft.de> <3E93EE35.3090107@fillmore-labs.com> <20030515175316.A84357@chaos.obstruction.com> <20030516000043.C21401@majakka.cksoft.de> In-Reply-To: <20030516000043.C21401@majakka.cksoft.de> X-Enigmail-Version: 0.74.3.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: eikemeier@fillmore-labs.com User-Agent: KMail/1.5.9 Organization: Fillmore Labs GmbH X-Complaints-To: abuse@fillmore-labs.com cc: ports@FreeBSD.org cc: Guy Middleton Subject: Re: break up cyclic dependency openldap21 <-> cyrus-sasl2 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 May 2003 23:35:48 -0000 Hi Guys, >>>>> [OE:] >>>>>I'm trying to enable OpenLDAP 2.1 SASL support. [...] >>>>>I've got a cyclic dependency cyrus-sasl-2.1.12 -> >>>>>openldap21-2.1.16 -> cyrus-sasl-2.1.12. Obvioulsy portupgrade doesn't >>>>>like cyclic dependencies. FreeBSD Porter's Handbook >>>>> >>>>>does not mention this, so I am stuck. >>>> >>>[...] I think we have to address the >>>dependency problem too. Splitting up cyrus-sasl and saslauthd looks >>>like a good plan to me, [...] >> >> [GM:] >>I just ran into the same problem myself -- I would like to compile OpenLDAP >>with SASL support, and I don't really need saslauthd, so the direction of >>dependency in the ports collection is backwards for me. > > [CK:] > I was going to whip up a saslauthd-ldap port but can't currently find > time to do it. > > On the other hand there is a new openldap version just released and > I would like to get the other parts of the patch committed. So I will > reverse the dependency to make sasl optional again and send a new pr updated > to openldap-2.1.19 over the weekend. In my opinion a cyrus-saslauthd port would be a good solution (Actually no saslauthd-ldap port, because ldap is optional for saslauthd) with dependencies: - cyrus-saslauthd -> cyrus-sasl2 - optional: cyrus-saslauthd -> openldap20/21 - optional: openldap21 -> cyrus-sasl2 (A -> B: A depends on B) This should work, the only references to ldap in cyrus-sasl2 are in the saslauthd part. Having said that this dependency scheme is a little crude, but the best I can come up with. Any other ideas, or should we discuss this with the cyrus and openldap people? Regards Oliver