From owner-freebsd-ruby@FreeBSD.ORG Tue Jul 26 05:17:19 2011 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F6BA1065670; Tue, 26 Jul 2011 05:17:19 +0000 (UTC) (envelope-from netch@segfault.kiev.ua) Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by mx1.freebsd.org (Postfix) with ESMTP id B3DCF8FC0A; Tue, 26 Jul 2011 05:17:18 +0000 (UTC) Received: from segfault.kiev.ua (localhost.segfault.kiev.ua [127.0.0.1]) by segfault.kiev.ua (8.14.4/8.14.4/8.Who.Cares) with ESMTP id p6Q55uld069106; Tue, 26 Jul 2011 08:05:56 +0300 (EEST) (envelope-from netch@segfault.kiev.ua) Received: (from netch@localhost) by segfault.kiev.ua (8.14.4/8.14.4/Submit) id p6Q55pvM069103; Tue, 26 Jul 2011 08:05:51 +0300 (EEST) (envelope-from netch) Date: Tue, 26 Jul 2011 08:05:51 +0300 From: Valentin Nechayev To: arved@FreeBSD.org Message-ID: <20110726050551.GC1941@netch.kiev.ua> References: <201107251154.p6PBsPba098661@freefall.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201107251154.p6PBsPba098661@freefall.freebsd.org> X-42: On Cc: ruby@FreeBSD.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jul 2011 05:17:19 -0000 Mon, Jul 25, 2011 at 11:54:25, arved wrote about "Re: ports/134182: ports-mgmt/portupgrade incorrectly handles manual reject to upgrade": > Your proposal contains a lot of footshooting potential for the unaware user. This can be solved by allowing such behavior on option or config clause, turned off by default. > 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. So this is my problem, among with any other unsupported setting, as patched system, manual port creation, etc. Do you remember FreeBSD motto - "Tools, not policy"? You have depriven us of good tool to track dependencies, which still can be useful for complex circumstances as locally crafted packages, basing on suspect which can be easily fixed with one small option. -netch-