From owner-freebsd-ports@FreeBSD.ORG Fri Jun 18 20:44:54 2004 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 F03DF16A4CE for ; Fri, 18 Jun 2004 20:44:54 +0000 (GMT) Received: from fillmore.dyndns.org (port-212-202-50-15.dynamic.qsc.de [212.202.50.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0E8D43D54 for ; Fri, 18 Jun 2004 20:44:54 +0000 (GMT) (envelope-from eikemeier@fillmore-labs.com) Received: from [172.16.0.11] (helo=localhost) by fillmore.dyndns.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34 (FreeBSD)) id 1BbQDy-000Le1-Ll; Fri, 18 Jun 2004 22:44:37 +0200 Date: Fri, 18 Jun 2004 22:44:34 +0200 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v482) To: Thomas-Martin Seck From: Oliver Eikemeier In-Reply-To: <20040618203027.GA12950@laurel.tmseck.homedns.org> Message-Id: <4E5BA166-C168-11D8-9250-00039312D914@fillmore-labs.com> Content-Transfer-Encoding: 7bit User-Agent: KMail/1.5.9 cc: freebsd-ports@freebsd.org Subject: Re: CONFLICTS usage question 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: Fri, 18 Jun 2004 20:44:55 -0000 Am Freitag den, 18. Juni 2004, um 22:30, schrieb Thomas-Martin Seck: > * Oliver Eikemeier (eikemeier@fillmore-labs.com): > >> Thomas-Martin Seck wrote: > > [port (deliberately) CONFLICTS with itself] ??? Of course bugs like that won't hinder a port to install. >>>> No. You will break installation with FORCE_PKG_REGISTER=yes. >>> >>> What about "-DFORCE_PKG_REGISTER -DDISABLE_CONFLICTS"? >> >> This disables the checks for already installed packages *and* >> for conflicting packages, which are disjoint sets. You can >> use this to repair files overwritten by a conflicting port >> (of course damaging the other port in the process). > > Maybe, but one /can/ forcibly reinstall a self-conflicting port with > FORCE_PKG_REGISTER and DISABLE_CONFLICTS if one is determined to do so. Yep. You won't notice when you damage other ports, (which you will when you do not use DISABLE_CONFLICTS), but you can do it that way. Anyway, read bsd.port.mk if you want to see other uses of FORCE_PKG_REGISTER and why conflicting with itself is a relly bad idea. CONFLICTS and FORCE_PKG_REGISTER deal with different topics. > As an interesting side note: it is amazing how many ports install a > ${PREFIX}/etc/leapsecs.dat. Where are CONFLICTS when you need them :( Which ports are you referring to? -Oliver