From owner-freebsd-ports@FreeBSD.ORG Thu Mar 17 17:54:56 2005 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1C21416A4CF; Thu, 17 Mar 2005 17:54:56 +0000 (GMT) Date: Thu, 17 Mar 2005 17:54:56 +0000 From: Kris Kennaway To: freebsd-ports@freebsd.org Message-ID: <20050317175456.GR91771@hub.freebsd.org> References: <20050317153840.GA39137@it.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050317153840.GA39137@it.ca> User-Agent: Mutt/1.4.2.1i cc: ports@freebsd.org Subject: Re: port name conflicts 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, 17 Mar 2005 17:54:56 -0000 On Thu, Mar 17, 2005 at 10:38:40AM -0500, Paul Chvostek wrote: > > The ports www/clearsilver and www/clearsilver-python both exist. The > latter calls the former with WITH_PYTHON enabled. So www/clearsilver > detects WITH_PYTHON, and changes its options accordingly ... but also > changes its package name with: > > .if defined(WITH_PYTHON) > ... > PKGNAMESUFFIX= -python > ... > > The result is that if WITH_PYTHON=yes is in /etc/make.conf, then these > ports have identical names, causing a conflict when `make index` runs. > > What's the solution here? Don't put WITH_PYTHON in /etc/make.conf? You can just ignore the warning, it shouldn't cause any problems. Kris