Date: Fri, 18 Nov 2016 13:10:25 -0500 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: Gary Aitken <freebsd@dreamchaser.org> Cc: FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: best time to sync Message-ID: <441sy8r75a.fsf@lowell-desk.lan> In-Reply-To: <552cf255-3a7f-2ea5-8401-d0218c445ece@dreamchaser.org> (Gary Aitken's message of "Fri, 18 Nov 2016 09:36:36 -0700") References: <2c878c5b-34e0-a58c-352d-b6c533b4da34@dreamchaser.org> <20161118152947.GR2648@home.opsec.eu> <552cf255-3a7f-2ea5-8401-d0218c445ece@dreamchaser.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Aitken <freebsd@dreamchaser.org> writes: > For example, is a weekly build done on the ports tree starting at a > particular day and time? Daily? The weekly builds are done from a snapshot, last I recall. With new hardware for the build clusters, full package runs may well get done more often than weekly these days. I'm pretty sure there's a way to know the precise date when the build run is based on. Unfortunately, I can't remember what that is. You could update your ports tree to the same time, but that doesn't quite get what you want, because that's not a guarantee that everything builds (although once the official build is done, you'll know which things *it* wasn't able to build). The advantage to this approach would mostly be that you can use the official builds for anything where the default options are okay, and know that the things you build yourself will be in synch with them. Your odds of hitting broken ports are probably lower when there have been fewer ports commits than usual in the previous few hours, but only slightly so. The experts are bapt@ and bdrewery@.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?441sy8r75a.fsf>