Date: Wed, 17 Nov 2004 16:56:22 -0800 From: Kris Kennaway <kris@obsecurity.org> To: jason andrade <jason@rtfmconsult.com> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: freebsd 5.3-release and some observations Message-ID: <20041118005622.GA95141@xor.obsecurity.org> In-Reply-To: <Pine.LNX.4.60.0411180925420.29442@luna.rtfmconsult.com> References: <Pine.LNX.4.60.0411171512011.29442@luna.rtfmconsult.com> <20041117160330.GA71815@xor.obsecurity.org> <Pine.LNX.4.60.0411180622020.29442@luna.rtfmconsult.com> <20041117232407.GA80979@xor.obsecurity.org> <Pine.LNX.4.60.0411180925420.29442@luna.rtfmconsult.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--1yeeQ81UyVL57Vl7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Nov 18, 2004 at 09:31:40AM +1000, jason andrade wrote: > On Wed, 17 Nov 2004, Kris Kennaway wrote: >=20 > >No, they're tied to the release. Often most packages will work, but > >not all, and not always. The point of keeping package sets for the > >releases are because they've undergone QA during the release, and > >users know they'll always work. Note that the release trees are > >static, so they're a once-only download. >=20 > yes, and that's a good current goal. i just wanted to raise the idea > on whether this continues into the future (e.g FreeBSD6).=20 > > > >In theory, you can always prioritise your updates so that e.g. i386 is > >always synced when it changes, but ia64 is not synced more than once a > >month. I don't know how easy this would be to do automatically on the > >mirror end, or if more infrastructure support would be needed, but > >that's out of my area. >=20 > ideally this is achieved by not rebuilding some of the architectures at > the same rate and then it's automatic, you don't update and i won't have > to fetch :-) >=20 > yes, this is a good idea and something that i imagine a number of us > have been doing informally - i will work to try to codify this into > the mirror documentation so people know. i suspect i386 weekly and > everything else monthly would work. That would impose policy upon the mirror operators who may want to sync immediately (because bandwidth is not a concern for them), and upon the users, since they may want to have access to new packages more than once a month (in particular, amd64 is rapidly gaining in ascendance, and sparc64 is also fairly popular). If you want to have a less frequent update policy, you can just choose one locally to suit your limitations and users can use a different mirror if they want something better (e.g. the main ftp site). Kris --1yeeQ81UyVL57Vl7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm/M2Wry0BWjoQKURAgaIAJ9AUhj3++EaXd5Opt+4W+nxhrJXdQCgy2XV Uq+CbH/WhtVeXpQPr/+MXWs= =VI9l -----END PGP SIGNATURE----- --1yeeQ81UyVL57Vl7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041118005622.GA95141>