From owner-freebsd-stable@freebsd.org Sat Jul 25 02:04:42 2015 Return-Path: Delivered-To: freebsd-stable@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 A741D9A95D8 for ; Sat, 25 Jul 2015 02:04:42 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 8B7BA18DF; Sat, 25 Jul 2015 02:04:42 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from FreeBSD.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by freefall.freebsd.org (Postfix) with ESMTP id 0A3A817FA; Sat, 25 Jul 2015 02:04:41 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Date: Sat, 25 Jul 2015 02:04:40 +0000 From: Glen Barber To: Nikolai Lifanov Cc: freebsd-stable@freebsd.org Subject: Re: help me understand latest->quarterly pkg.conf switch Message-ID: <20150725020440.GJ84931@FreeBSD.org> References: <20150724212757.GE84931@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="U5yJ31ax00IavOwq" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 11.0-CURRENT amd64 X-SCUD-Definition: Sudden Completely Unexpected Dataloss X-SULE-Definition: Sudden Unexpected Learning Event X-PEKBAC-Definition: Problem Exists, Keyboard Between Admin/Computer User-Agent: Mutt/1.5.23 (2014-03-12) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Jul 2015 02:04:42 -0000 --U5yJ31ax00IavOwq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jul 24, 2015 at 09:23:12PM -0400, Nikolai Lifanov wrote: > On 2015-07-24 17:27, Glen Barber wrote: > >On Fri, Jul 24, 2015 at 05:15:52PM -0400, Nikolai Lifanov wrote: > >>I noticed that in stable/10, /etc/pkg/FreeBSD.conf was switched from > >>using > >>latest package set to whichever one that is "quarterly" word is pointing > >>to > >>at the moment. What is the motivation for this change? > >> > > > >This was not done in the stable/10 branch, it was done in releng/10.2. > > > >>Quarterly package sets are useful if the end-user is able to pick which > >>one > >>to pull from and there is some amount of time of support overlap so that > >>the > >>user has time to validate the new package set and switch his systems to > >>it > >>(like what is done with pkgsrc). As-is, "quarterly" works just like > >>"latest" > >>from end-user perspective, but for most of the lifecycle packages are > >>outdated and there is a massive update bomb four times per year. > >> > >>Port branches are still valuable to those building their own packages, > >>since > >>they can support the previous (unsupported by the project) branch, > >>backporting fixes manually, while validating and upgrading to the new > >>one. > >>But, what is the value of the quarterly package set as-is and what is > >>the > >>value of switching to this set by default? > >> > > > >In general, the quarterly package set is less prone to having build > >failures, since the changes in the branch are (by intent) less > >intrusive, while still receiving security updates. It is analogous to > >the stable or releng branches in src, and how they compare to head. > > > >(This will be noted in the final 10.2-RELEASE announcement, as well as > >the release notes, and will also include instructions on how to switch > >to the 'latest' branch if that is what is desired.) > > > >Glen >=20 > Cool, thanks for the explanation! >=20 You're welcome. (The 'quarterly' branch is admittedly under-documented, which is a problem.) > What would be really amazing to see are quarterly branches that the end u= ser > can switch between, like pkg.freebsd.org/${ABI}/2015Q3 -> > pkg.freebsd.org/${ABI}/2015Q4 when he is ready, with at least a little bit > of overlap. >=20 I agree this would be a "nice to see" feature, but as I have insight into how the pkg(8) mirrors operate, this is an unfortunately non-trivial thing to implement. Glen --U5yJ31ax00IavOwq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJVsu64AAoJEAMUWKVHj+KTR7gQAJZOF/afm7a4HsmKD+L/Pk1/ HXtL6nNHxWuDCSPOd92LPSe6/mvo1phrLD9WEBA3HiwkNciidpwNxRg2Ru/sTxYl dbnzA7aG6AK+5AeWt2BuSBwCrIEEzR8pEBI8+zoNGJXoWLTRXh3CoDa9r6d3Xg5/ W+P8079ZeKiKA2RU/QdLIV20mxxWKK0Ie6zuEghvnrpbHReqkbkZsLoYkanH5NH9 ZhyaOt1A7yJ74lNvcVqByUN3BmvFVIkJTuNNVYAXKM1jLIqWyqgsHOqbj+yPi/OR LjbXZNQZyyRAxctDsB8OHX4Y3V4AbJCE11yo1hsTYZBkDWMNIapb+VKpNM7gbLYG QEb4R8Lj+Q+vdUNAUHq3E0vb6xgclwSQmFOd3hRwp9OfX+LwYwMTU28w68FKI4Sm rXkaVljmh5UrKiRJOccAgqm7DFJ2QHVhxXg62IWsNa0kWwYXl+bqa4YTmX/WwlU6 3w2xJhqSQBg+WyvsNJft3pEI9Il+MyoRwyVKs2HEJ9Hswow9f++OhKE3n8nfTHtX FFKH3i5aumyFiW3jyM4zpg2FsxC36JGEJcOcxeoqCGXHTaWENY/dFVkr3twpv1CF qwvNt58K4YExgSbgy4ffW+rKCRtoKPm9YJKanjyNSaEFpFhxYjDpgv/291BhI4Gv 4nC4M6scUzWrtFS8Pejc =Hc2Y -----END PGP SIGNATURE----- --U5yJ31ax00IavOwq--