From owner-freebsd-apache@FreeBSD.ORG Mon Dec 21 12:13:48 2009 Return-Path: Delivered-To: apache@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2020E1065676 for ; Mon, 21 Dec 2009 12:13:48 +0000 (UTC) (envelope-from robin@reportlab.com) Received: from mail-ew0-f213.google.com (mail-ew0-f213.google.com [209.85.219.213]) by mx1.freebsd.org (Postfix) with ESMTP id B70A48FC17 for ; Mon, 21 Dec 2009 12:13:47 +0000 (UTC) Received: by ewy5 with SMTP id 5so5899751ewy.34 for ; Mon, 21 Dec 2009 04:13:46 -0800 (PST) MIME-Version: 1.0 Received: by 10.213.109.201 with SMTP id k9mr1304149ebp.87.1261395887303; Mon, 21 Dec 2009 03:44:47 -0800 (PST) In-Reply-To: <44y6kxvf59.fsf@lowell-desk.lan> References: <4B2A2023.5050607@chamonix.reportlab.co.uk> <44y6kxvf59.fsf@lowell-desk.lan> Date: Mon, 21 Dec 2009 11:44:47 +0000 Message-ID: From: Robin Becker To: FreeBSD Mailing List , apache@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: binary package dependencies X-BeenThere: freebsd-apache@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Support of apache-related ports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Dec 2009 12:13:48 -0000 2009/12/20 Lowell Gilbert : .......... >> Somehow I had naively assumed that apache20 and apache22 were >> incompatible and could not simultaneously be installed. Did the binary >> package load ignore all conflicts? What's the proper way to approach >> these issues. Looking in the apache20 Makefile I see it conflicts with >> earlier apache, but how can it conflict with a later one? > > I think that it should. =C2=A0As I read it, apache22 registers a conflict > with apache20, but the reverse is not true. =C2=A0If you had installed th= em > in the other order, it would've refused to install. =C2=A0apache20 is the > default, so the official package was built depending on that. > > I think this should be entered as a bug, but I'm not quite positive... > clearly A conflict B is supposed to be a symmetric relation, but I guess in this case when I install apache22 it's the entire ports system that needs to record the conflicts. I don't think it's reasonable for an individual port to know that a future conflict may arise. -- Robin Becker