From owner-freebsd-ports@freebsd.org Fri Nov 18 17:28:10 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 27ECDC48F57 for ; Fri, 18 Nov 2016 17:28:10 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (mx.catwhisker.org [198.144.209.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DDC4FF9 for ; Fri, 18 Nov 2016 17:28:09 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.15.2/8.15.2) with ESMTP id uAIHDlwR069935; Fri, 18 Nov 2016 17:13:47 GMT (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.15.2/8.15.2/Submit) id uAIHDl5K069934; Fri, 18 Nov 2016 09:13:47 -0800 (PST) (envelope-from david) Date: Fri, 18 Nov 2016 09:13:47 -0800 From: David Wolfskill To: Gary Aitken Cc: FreeBSD Mailing List Subject: Re: best time to sync Message-ID: <20161118171347.GE1080@albert.catwhisker.org> References: <2c878c5b-34e0-a58c-352d-b6c533b4da34@dreamchaser.org> <20161118152947.GR2648@home.opsec.eu> <552cf255-3a7f-2ea5-8401-d0218c445ece@dreamchaser.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="nVrqoArjIp3ewQcx" Content-Disposition: inline In-Reply-To: <552cf255-3a7f-2ea5-8401-d0218c445ece@dreamchaser.org> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Nov 2016 17:28:10 -0000 --nVrqoArjIp3ewQcx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 18, 2016 at 09:36:36AM -0700, Gary Aitken wrote: > ... > ... > >> Can someone tell me what the best time to synchronize ports is, > >> in terms of having a consistent ports tree? > ... > I'm interested in a consistent ports tree for build purposes. I want > updates, but I want the tree to be consistent enough to build. In > the past I have sync'd at less than ideal times and things did not > build as a result. I understand this is always a possibility, but > was wondering if there was a time when it was most likely consistent. > For example, is a weekly build done on the ports tree starting at a=20 > particular day and time? Daily? > .... Of the possibly-relevant things I do, the one that comes to mind is that I maintain a local private mirror of the FreeBSD SVN ports repository. (I also maintain one each for src and doc, but that's veering off-topic.) I synchronize my mirror overnight (in 2 passes -- though that's a legacy =66rom when I used CVSup, and was because of the huge amount of time spent when a new tag was laid down; with svn, that's really not an issue). In my case, the sync runs at about 03:30 hrs. US/Pacific. That done, I can make my ports working copy follow head or a quarterly branch as I see fit -- though in practice, I choose follow head. (I also update the base system frequently (daily), and follow that by updating all installed ports on the laptop I use for day-to-day use. That's probably something folks ought to think long and hard about before actually doing it: it works for me, but it's not for everyone.) And the repository is thus stable while I'm awake, which I find useful. On the other hand, if someone commits a change I need just after I synchronized for the day, well... that's awkward. Peace, david --=20 David H. Wolfskill david@catwhisker.org Ref. 08 Nov 2016, let's see if the "winners" actually deliver on their slog= ans. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --nVrqoArjIp3ewQcx Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQF8BAEBCgBmBQJYLzbLXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRDQ0I3Q0VGOTE3QTgwMUY0MzA2NEQ3N0Ix NTM5Q0M0MEEwNDlFRTE3AAoJEBU5zECgSe4X7joH/RT6mGJOZW/7k3YWlArh1vgc vgJ14gMFOa6vBwhidzrnQ7e5LVVEw/Lw+IIB3Q+ZKxxLnXSGnPkYmA8igb29aQ8o 3Qjv1R+G17ZDlZcXaUvVvqtymAqtDZvw7QfxZmPa3sSa9T3l478XRCNmVF3tnhAG MLLQiNy4oYJszpOn80aitgLswoeqdPz+yyL1lPpda3FOSqZ2m+70KGzIMyNTrmtg hlxyDx8GvsUfbNi3pCucZ4uv011IjpfGZJZhyBLea1U+SeXjpe7esBkAxP/ZnMCj EWnCKfz+29QAl1y0uv3dFv9JRulE70kXQXbkRUSlnjGoC8as1Rc7DFWtobA1aaU= =hTfG -----END PGP SIGNATURE----- --nVrqoArjIp3ewQcx--