Date: Fri, 21 Oct 2011 11:21:04 +0200 From: Damien Fleuriot <ml@my.gd> To: freebsd-questions@freebsd.org Subject: Re: which ports require dialog during update Message-ID: <4EA13980.4090505@my.gd> In-Reply-To: <4EA13806.5000803@ifdnrg.com> References: <4EA12507.7090703@ifdnrg.com> <4EA125D1.1020204@my.gd> <4EA13806.5000803@ifdnrg.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/21/11 11:14 AM, Paul Macdonald wrote: >>Hi, Is there a way to tell which ports might require dialog input > during update, i have some auto update scripts >> Stop doing this. >> >> Your update scripts do not read /usr/ports/UPDATING. >> Your update scripts do not read package changelogs. >> >> What you're doing is irresponsible, and potentially dangerous/harmful if >> your server is in production. >> >> You should really be very careful about this. > i do of course read those files (which require daily checking to confirm > usually no relevant changes, but thats another issue!).. > > however i don't need to read UPDATING on every box, (this tool is an > assistent, not a replacement, for monitored updates.) > > i do need to check that an update that went fine on the initial test box > will behave the same on other boxes, which is my question, > > can i tell if the options dialog is going to be invoked? > > thanks > Paul. I'm afraid I can't see an option in portmanager that would handle this. I think you portupgrade's --batch mode might be the answer to your question though.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EA13980.4090505>