From owner-freebsd-ports@FreeBSD.ORG  Mon Jun 18 22:59:02 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: ports@freebsd.org
Delivered-To: freebsd-ports@FreeBSD.ORG
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 52A9B16A46B
	for <ports@freebsd.org>; Mon, 18 Jun 2007 22:59:02 +0000 (UTC)
	(envelope-from clint@0lsen.net)
Received: from rwcrmhc14.comcast.net (rwcrmhc14.comcast.net [216.148.227.154])
	by mx1.freebsd.org (Postfix) with ESMTP id 4342E13C45E
	for <ports@freebsd.org>; Mon, 18 Jun 2007 22:59:02 +0000 (UTC)
	(envelope-from clint@0lsen.net)
Received: from 0lsen.net ([24.20.127.157])
	by comcast.net (rwcrmhc14) with ESMTP
	id <20070618225901m14006h28be>; Mon, 18 Jun 2007 22:59:01 +0000
Received: by 0lsen.net (Postfix, from userid 1001)
	id 9C2BC172A7; Mon, 18 Jun 2007 15:59:01 -0700 (PDT)
Date: Mon, 18 Jun 2007 15:59:01 -0700
From: Clint Olsen <clint.olsen@gmail.com>
To: ports@freebsd.org
Message-ID: <20070618225901.GA35682@0lsen.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.3i
Organization: NULlsen Network
X-Disclaimer: Mutt Bites!
Cc: 
Subject: Installing Openoffice.org-2-RC and bison conflicts
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Jun 2007 22:59:02 -0000

I'm trying to install openoffice, and some sub-portion of the port is
installing bison2, and later it tries to install bison and then it
complains about conflicting ports.  How is one supposed to deal with
sub-port conflicts like these?  Why do we /ever/ allow ports to have
conflicts with other ports?  That seems broken from the start.

Thanks,

-Clint