From owner-freebsd-questions@FreeBSD.ORG Fri Jan 15 16:44:09 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 98D3C1065672 for ; Fri, 15 Jan 2010 16:44:09 +0000 (UTC) (envelope-from kirk@strauser.com) Received: from kanga.honeypot.net (kanga.honeypot.net [IPv6:2001:470:a80a:1:21f:d0ff:fe22:b8a8]) by mx1.freebsd.org (Postfix) with ESMTP id 5745E8FC15 for ; Fri, 15 Jan 2010 16:44:09 +0000 (UTC) Received: from kanga.honeypot.net (localhost [127.0.0.1]) by kanga.honeypot.net (Postfix) with ESMTP id 43D253D186 for ; Fri, 15 Jan 2010 10:44:08 -0600 (CST) X-Virus-Scanned: amavisd-new at honeypot.net Received: from kanga.honeypot.net ([127.0.0.1]) by kanga.honeypot.net (kanga.honeypot.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DrJpo8AmmwDC for ; Fri, 15 Jan 2010 10:44:05 -0600 (CST) Received: from athena.daycos.com (athena.daycos.com [IPv6:2001:470:c054:1:221:9bff:fe00:de3f]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by kanga.honeypot.net (Postfix) with ESMTPSA id 301C93D182 for ; Fri, 15 Jan 2010 10:44:04 -0600 (CST) Message-ID: <4B509B51.3060809@strauser.com> Date: Fri, 15 Jan 2010 10:44:01 -0600 From: Kirk Strauser User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.5) Gecko/20100105 Thunderbird/3.0 MIME-Version: 1.0 To: FreeBSD Questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Dislike the way port conflicts are handled now X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jan 2010 16:44:09 -0000 Until recently, it seems like port dependencies were handled at installation time. Lately, they're handled any time I try to do anything with a port. I absolutely detest the new behavior. Example cases: OLD WAY: $ cd /usr/ports/something/foo22 $ make $ pkg_delete foo21-2.1 $ make install NEW WAY $ cd /usr/ports/something/foo22 $ make ===> foo22 conflicts with installed package(s): foo21-2.1 $ make fetch ===> foo22 conflicts with installed package(s): foo21-2.1 $ curse --type=copious $ pkg_delete foo21-2.1 $ make install This isn't just a hypothetical pain in the butt. An example was being unable to build databases/mysql51-client because mysql-client-5.0.something was installed. I understand not being able to *install* it, but to be prevented from *building* it? In most circumstances, I want to be able to delete the old package and install the new one with minimal downtime. As another example, can you imagine not being able to even run "make fetch" on something huge like OpenOffice until you uninstalled the old version? In the mean time, I've been editing the port's Makefile to remove the CONFLICTS line long enough to finish building. That's not very helpful for those ports that don't actually build until you run "make install", but at least I can get the distfile download out of the way. -- Kirk Strauser