From owner-freebsd-ports@FreeBSD.ORG Fri Jun 18 20:30:30 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 6971416A4CE for ; Fri, 18 Jun 2004 20:30:30 +0000 (GMT) Received: from smtp2.netcologne.de (smtp2.netcologne.de [194.8.194.218]) by mx1.FreeBSD.org (Postfix) with ESMTP id EF5E543D53 for ; Fri, 18 Jun 2004 20:30:29 +0000 (GMT) (envelope-from tmseck-lists@netcologne.de) Received: from laurel.tmseck.homedns.org (xdsl-213-196-220-108.netcologne.de [213.196.220.108]) by smtp2.netcologne.de (Postfix) with SMTP id A6A3948BE for ; Fri, 18 Jun 2004 22:30:23 +0200 (MEST) Received: (qmail 31993 invoked by uid 1001); 18 Jun 2004 20:30:49 -0000 Date: Fri, 18 Jun 2004 22:30:27 +0200 From: Thomas-Martin Seck To: Oliver Eikemeier Message-ID: <20040618203027.GA12950@laurel.tmseck.homedns.org> References: <20040618160618.19385.qmail@laurel.tmseck.homedns.org> <6EC9DFB0-C15D-11D8-9250-00039312D914@fillmore-labs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <6EC9DFB0-C15D-11D8-9250-00039312D914@fillmore-labs.com> User-Agent: Mutt/1.4.2.1i Organization: a private site in Germany X-PGP-KeyID: DF46EE05 X-PGP-Fingerprint: A38F AE66 6B11 6EB9 5D1A B67D 2444 2FE1 DF46 EE05 X-Attribution: tms 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:30:30 -0000 * Oliver Eikemeier (eikemeier@fillmore-labs.com): > Thomas-Martin Seck wrote: [port (deliberately) CONFLICTS with itself] > >>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. As an interesting side note: it is amazing how many ports install a ${PREFIX}/etc/leapsecs.dat. Where are CONFLICTS when you need them :(