From owner-freebsd-hubs@FreeBSD.ORG Wed Nov 17 16:00:21 2004 Return-Path: Delivered-To: freebsd-hubs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4C1A916A4D0 for ; Wed, 17 Nov 2004 16:00:21 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.194.102.143]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1543C43D4C for ; Wed, 17 Nov 2004 16:00:21 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id D533D5128A; Wed, 17 Nov 2004 08:03:30 -0800 (PST) Date: Wed, 17 Nov 2004 08:03:30 -0800 From: Kris Kennaway To: jason andrade Message-ID: <20041117160330.GA71815@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AqsLC8rIMeq19msA" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i cc: hubs@freebsd.org Subject: Re: freebsd 5.3-release and some observations X-BeenThere: freebsd-hubs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Distributions Hubs: mail sup ftp List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 16:00:21 -0000 --AqsLC8rIMeq19msA Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Nov 17, 2004 at 03:21:02PM +1000, jason andrade wrote: > given the length of time for package tree updates i'd be > asking if there is any thoughts that could be raised about > how better to supply package trees so they aren't `tied' > to an architecture and thus appear to be released in 3-5G > chunks. package trees are absolutely tied to an architecture, because they contain compiled files that will only run on that architecture (modulo things like amd64-i386 compatibility). > i'm a little confused about the -current package trees in ports/$ARCH. alpha packages are not built regularly any more (I announced this some time ago). For other architectures we build packages for supported release branches (4.x, 5.x and 6.x). Since FreeBSD 4.x only supports i386 and alpha (but see above), that's why the others don't have 4.x packages. The missing 6.x packages are because the first such builds are not yet finished. They'll appear in the next week or so. > how often are the -current package=20 > sets being updated ? once upon a time it was a weekly (?) rebuild. All supported package branches for i386 are rebuilt roughly every week, depending on how the builds go. Other architectures are updated a bit less frequently because the builds take longer. Note that 4.x and 5.x builds are usually incremental builds thesedays, meaning that if the package doesn't change it isn't changed on the server, thus reducing mirror download bulk. > should mirrors carry this ? If at all possible, yes. Mirrors are most useful when they're complete mirrors. Kris --AqsLC8rIMeq19msA Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQFBm3ZSWry0BWjoQKURAmyiAKDDTB2UICR/Z3XdQ2u2ouLbfJSALgCgsj8F LNcocEbD3FXkIsdwBw1fokk= =urEN -----END PGP SIGNATURE----- --AqsLC8rIMeq19msA--