Date: Sun, 28 Aug 2011 13:57:18 -0700 From: Doug Barton <dougb@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: <4E5AABAE.6030200@FreeBSD.org> In-Reply-To: <20110828183300.GX17489@deviant.kiev.zoral.com.ua> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/28/2011 11:33 AM, Kostik Belousov wrote: > Apparently, this have to be written explicitely. Users, who upgrade > their ports, are not presented with the configuration dialog. The dialog is re-presented to the user if the quantity of options has changed. That's a feature. See my previous message on a way to make this feature work for us in this situation. > Using > automated tool like portupgrade, all you get is a list of the failed > ports. After that, user needs to start investigation, spending his > own time and possibly time of the people on list. > > 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. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E5AABAE.6030200>