Date: Thu, 28 Apr 2016 12:51:53 +0100 From: RW <rwmaillists@googlemail.com> To: ports@freebsd.org Subject: Re: Ports tree gone unstable? Message-ID: <20160428125153.49d29836@gumby.homeunix.com> In-Reply-To: <201604280648.u3S6mhDX006562@gw.catspoiler.org> References: <572140C0.1030903@sorbs.net> <201604280648.u3S6mhDX006562@gw.catspoiler.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 27 Apr 2016 23:48:43 -0700 (PDT) Don Lewis wrote: > I'd lose many hours of potential build time. Because of the > infrequent upgrades I would have to deal with all of the intervening > special cases in UPDATING that accumulated between upgrades, and the > portupgrade -fr and -a options didn't interoperate well, so I ended > up having to build some ports multiple times. If things crashed, > then I'd have to run portupgrade -rf again, rebuilding a lot of > things unnecessarily since there was no way of doing a restart. FWIW the portupgrade -fr entries in UPDATING only need be followed if you are doing a partial update. Any port affected by these gets its port revision bumped, so is rebuilt as part of a portupgrade -a.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160428125153.49d29836>