From owner-freebsd-ruby@FreeBSD.ORG Tue Jul 26 07:43:46 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 D1976106566B for ; Tue, 26 Jul 2011 07:43:46 +0000 (UTC) (envelope-from arved@FreeBSD.org) Received: from mail01.rise-w.com (iris.rise-s.com [88.116.105.226]) by mx1.freebsd.org (Postfix) with ESMTP id 869AF8FC0A for ; Tue, 26 Jul 2011 07:43:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail01.rise-w.com (Postfix) with ESMTP id 7B9CC40E0ED; Tue, 26 Jul 2011 09:21:37 +0200 (CEST) Received: from [192.168.59.162] (chello080108063010.8.11.vie.surfer.at [80.108.63.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.rise-world.com (Postfix) with ESMTPSA id E9B1D40E056; Tue, 26 Jul 2011 09:21:36 +0200 (CEST) Message-ID: <4E2E6B8A.6060700@FreeBSD.org> Date: Tue, 26 Jul 2011 09:23:54 +0200 From: =?ISO-8859-1?Q?Tilman_Keskin=F6z?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.18) Gecko/20110617 Thunderbird/3.1.11 MIME-Version: 1.0 To: Valentin Nechayev References: <201107251154.p6PBsPba098661@freefall.freebsd.org> <20110726050551.GC1941@netch.kiev.ua> In-Reply-To: <20110726050551.GC1941@netch.kiev.ua> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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 07:43:46 -0000 On 07/26/2011 07:05 AM, Valentin Nechayev wrote: > 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. Well, it is just harder for you to shoot your foot without an automatic tool, but all the pkg_tools still allow what you want to do. Another option for you might be to provide a patch and apply for the job as the future portupgrade maintainer. Then you will get the mail from all the people that used this feature an ran into problems.