Date: Tue, 12 May 2009 18:53:09 +0200 From: Mel Flynn <mel.flynn+fbsd.current@mailing.thruhere.net> To: freebsd-current@freebsd.org Cc: Giorgos Keramidas <keramida@ceid.upatras.gr>, Jon Loeliger <jdl@jdl.com> Subject: Re: Feedback and Questions Updating to CURRENT Message-ID: <200905121853.09947.mel.flynn%2Bfbsd.current@mailing.thruhere.net> In-Reply-To: <E1M3JOk-0007fX-CH@jdl.com> References: <E1M3GfE-0007Ld-9B@jdl.com> <87vdo8powi.fsf@kobe.laptop> <E1M3JOk-0007fX-CH@jdl.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 11 May 2009 02:29:38 Jon Loeliger wrote: > > pkgdb -Fu && portupgrade -fa > > > > or: > > > > portmaster -fa > > And confusingly here, there's no indication as to why I might > pick one or the other, nor the pros and cons of either, nor > if having picked one, I could use the other later. portmaster is superior when crossing major release boundaries as it has no dependencies other then /bin/sh, while portupgrade uses ruby and bdb. > A "use the defaults" configuration for totally non-interactive > build would have been my expectation here. Will I need to > babysit this whole build now? Yep. Nope. Again, portmaster will present you with all options before you go to dinner and when confronted with an interactive port will tell you before it starts to build and allows you to eat. Adding -m '-DBATCH' to portmaster will also silence any confirmation questions. These are not considered interactive ports, because of this fact that BATCH compiling can turn them off. Ports marked interactive (IS_INTERACTIVE=yes) have no sane or legally valid default (accepting a license for example). -- Mel
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905121853.09947.mel.flynn%2Bfbsd.current>