From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Sep 30 19:10:22 2006 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9CAFA16A415 for ; Sat, 30 Sep 2006 19:10:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 40D2043D46 for ; Sat, 30 Sep 2006 19:10:22 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k8UJAM7A066085 for ; Sat, 30 Sep 2006 19:10:22 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k8UJALmh066083; Sat, 30 Sep 2006 19:10:22 GMT (envelope-from gnats) Date: Sat, 30 Sep 2006 19:10:22 GMT Message-Id: <200609301910.k8UJALmh066083@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Dan Lukes Cc: Subject: Re: ports/103855: security/amavisd-new & security/amavisd-milter circular dependence X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dan Lukes List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Sep 2006 19:10:22 -0000 The following reply was made to PR ports/103855; it has been noted by GNATS. From: Dan Lukes To: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= Cc: bug-followup@FreeBSD.org Subject: Re: ports/103855: security/amavisd-new & security/amavisd-milter circular dependence Date: Sat, 30 Sep 2006 21:00:55 +0200 I think the correct view is - amavisd-milter is for those who want to run amavisd with milter. It use the amavisd-new as supporting port, so it should RUN_DEPEND on it. Those, who need new amavis, but don't want the milter interface, need amavisd-new. I see no reason to create special options for users who require new amavis with milter interface, but hate amavisd-milter port. Of course, you can create slave-variant from both ports, then include them from two separate master ports with different set of options. The amavis-milter will depend on slave-amavisd-milter and slave-amavisd-new, the amavisd-new will depend on slave-amavisd-new and, if required milter, on slave-amavisd-milter. But it sound as way to hell for me. As I said above, no user should require new amavis with milter, but rejecting to use amavisd-milter which is exactly for this. Dan