Date: Sun, 28 Aug 2011 17:15:08 -0400 From: Sahil Tandon <sahil@FreeBSD.org> To: freebsd-ports@freebsd.org Subject: Re: How to handle upgrade of libnotify when cups-client-1.4.8 is marked as broken Message-ID: <20110828211508.GC668@magic.hamla.org> In-Reply-To: <4E5AABAE.6030200@FreeBSD.org> References: <4E5A48AC.6050201@eskk.nu> <20058.20743.791783.342355@jerusalem.litteratus.org> <BLU0-SMTP182102B9C96837517ECB6BB93150@phx.gbl> <20110828172651.GB277@magic.hamla.org> <20110828173059.GT17489@deviant.kiev.zoral.com.ua> <20110828181356.GD277@magic.hamla.org> <20110828183300.GX17489@deviant.kiev.zoral.com.ua> <4E5AABAE.6030200@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2011-08-28 at 13:57:18 -0700, Doug Barton wrote: > On 8/28/2011 11:33 AM, Kostik Belousov wrote: > > Ignoring or removing the option makes the ports upgrade without user > > intervention. > > Neither of those is a valid option (pardon the pun). The primary goal > is to avoid breaking the user's system, not to make the upgrade > process go through without human intervention. Imagine a scenario > where the user has a critical dependency on cups being compiled with > gnutls. Not upgrading the currently installed (and working) version is > a totally valid outcome. Silently upgrading cups to a version without > gnutls makes the upgrade process "successful," but with a very poor > outcome for the user. Bingo. -- Sahil Tandon <sahil@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110828211508.GC668>