From owner-freebsd-ruby@FreeBSD.ORG  Mon Jul 25 11:54:26 2011
Return-Path: <owner-freebsd-ruby@FreeBSD.ORG>
Delivered-To: ruby@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 495251065674;
	Mon, 25 Jul 2011 11:54:26 +0000 (UTC)
	(envelope-from arved@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 218C98FC13;
	Mon, 25 Jul 2011 11:54:26 +0000 (UTC)
Received: from freefall.freebsd.org (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p6PBsQDx098665;
	Mon, 25 Jul 2011 11:54:26 GMT
	(envelope-from arved@freefall.freebsd.org)
Received: (from arved@localhost)
	by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p6PBsPba098661;
	Mon, 25 Jul 2011 11:54:25 GMT (envelope-from arved)
Date: Mon, 25 Jul 2011 11:54:25 GMT
Message-Id: <201107251154.p6PBsPba098661@freefall.freebsd.org>
To: netch@netch.kiev.ua, arved@FreeBSD.org, ruby@FreeBSD.org
From: arved@FreeBSD.org
Cc: 
Subject: Re: ports/134182: ports-mgmt/portupgrade incorrectly handles manual
	reject to upgrade
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Jul 2011 11:54:26 -0000

Synopsis: ports-mgmt/portupgrade incorrectly handles manual reject to upgrade

State-Changed-From-To: open->closed
State-Changed-By: arved
State-Changed-When: Mon Jul 25 11:51:59 UTC 2011
State-Changed-Why: 
Your proposal contains a lot of footshooting potential for the unaware user.

I think the current behaviour is the right one.

If you want to update a port without updating its dependencies first, you
are running an unsupported setting and a lot of problems can occur. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=134182