From owner-freebsd-hubs Sun Mar 9 23: 8:27 2003 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 5EDCB37B401; Sun, 9 Mar 2003 23:08:25 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-63-207-60-52.dsl.lsan03.pacbell.net [63.207.60.52]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EE5E43FDD; Sun, 9 Mar 2003 23:08:18 -0800 (PST) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id 1D00C66D16; Sun, 9 Mar 2003 23:08:18 -0800 (PST) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id F22BE786; Sun, 9 Mar 2003 23:08:17 -0800 (PST) Date: Sun, 9 Mar 2003 23:08:17 -0800 From: Kris Kennaway To: Chris Demers Cc: jason andrade , Kris Kennaway , David O'Brien , hubs@FreeBSD.ORG Subject: Re: Poor state of some top-level FTP mirrors Message-ID: <20030310070817.GA72834@rot13.obsecurity.org> References: <20030309215448.GB30033@dragon.nuxi.com> <20030310013355.GA70336@rot13.obsecurity.org> <20030310064332.M84136@govital.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YiEDa0DAkWCtVeE4" Content-Disposition: inline In-Reply-To: <20030310064332.M84136@govital.net> User-Agent: Mutt/1.4i Sender: owner-freebsd-hubs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --YiEDa0DAkWCtVeE4 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Mar 10, 2003 at 01:58:57AM -0500, Chris Demers wrote: > I took a quick look around to find out just how this was being done and i > couldn't find it. So i'm going to do some assuming and make some suggestions. > Assuming a full package build is normally just pushed out for distribution, > this would cause much unneeded bandwidth usage among all of the mirror sites. > Wouldn't it be just better to maybe keep a record of the fingerprint of a > port and if it matched from the last build not send it out to the mirrors so > that only things that have been updated get pushed out? The only problem with > this method is that it would slow down the build system a bit while it checks > the files. Or maybe instead of just blindly building the entire collection > all the time, keep a database of the versions that have been built and only > build the ones that change. There would have to be some extra checking in > there too to make sure that all dependacys affected by a version change of any > port also get rebuilt, but that method would probably work better as the build > system wouldn't have to work as hard all the time to churn out packages for > ports that rarely change. And then just do a full build from time to time to > double check everything. Not really practical..see my other mail. Kris --YiEDa0DAkWCtVeE4 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+bDnhWry0BWjoQKURAosLAKDYLOwcE974x2lp5Q4btFjzgYE+nACgxg0K mJ58X5rg5XHV6qgo7ex1nB0= =taRQ -----END PGP SIGNATURE----- --YiEDa0DAkWCtVeE4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hubs" in the body of the message