From owner-freebsd-questions@FreeBSD.ORG Sun Jan 17 12:03:17 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 196B61065670; Sun, 17 Jan 2010 12:03:17 +0000 (UTC) (envelope-from miwi@FreeBSD.org) Received: from bsdcrew.de (duro.unixfreunde.de [85.214.90.4]) by mx1.freebsd.org (Postfix) with ESMTP id CB4B78FC08; Sun, 17 Jan 2010 12:03:16 +0000 (UTC) Received: from miwi.homeunix.com (dslc-082-083-134-099.pools.arcor-ip.net [82.83.134.99]) by bsdcrew.de (Postfix) with ESMTPA id CAF274AF8A; Sun, 17 Jan 2010 12:45:00 +0100 (CET) Date: Sun, 17 Jan 2010 12:45:06 +0100 From: Martin Wilke To: pav@FreeBSD.org Message-ID: <20100117124506.1563d9ad@miwi.homeunix.com> In-Reply-To: <1263725045.1541.66.camel@hood.oook.cz> References: <4B520C71.9080301@FreeBSD.org> <1263673588.1541.60.camel@hood.oook.cz> <4B524584.9050909@FreeBSD.org> <1263725045.1541.66.camel@hood.oook.cz> X-Mailer: Claws Mail 3.7.4 (GTK+ 2.18.5; amd64-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Cc: glarkin@FreeBSD.org, freebsd-questions@FreeBSD.org, "b. f." , portmgr@FreeBSD.org Subject: Re: 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: Sun, 17 Jan 2010 12:03:17 -0000 On Sun, 17 Jan 2010 11:44:05 +0100 Pav Lucistnik wrote: > Greg Larkin p=ED=B9e v so 16. 01. 2010 v 18:02 -0500: >=20 > > Here is the original post: > > http://www.mail-archive.com/freebsd-questions@freebsd.org/msg227363.html >=20 > I will agree that `portupgrade -o` is way too useful feature. > I'd vote for reverting to the old behaviour. >=20 > > I thought portmgr might have some insight into additional reasons > > for making the change, such as fixing a problem with pointyhat > > builds, etc. At the moment, I'm neutral on the change, since it > > hasn't caused me any grief, but I did some research for the folks > > who posted the original questions. >=20 > It was done because someone thought it is a good idea and submitted a > PR about it. >=20 Howdy, For some ports is the conflict check too late see example here. http://lists.freebsd.org/pipermail/freebsd-gecko/2009-December/000577.html= =20 I agree that we need a new pre-fetch hook in bsd.port.mk if a conflict present is. But that need a bit work and it is on my todo list... - Martin