From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 8 02:27:32 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B23EA16A4CE; Thu, 8 Jan 2004 02:27:32 -0800 (PST) Received: from obsecurity.dyndns.org (adsl-67-119-53-122.dsl.lsan03.pacbell.net [67.119.53.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id B0D6E43D4C; Thu, 8 Jan 2004 02:27:30 -0800 (PST) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 37B9766E67; Thu, 8 Jan 2004 02:27:30 -0800 (PST) Date: Thu, 8 Jan 2004 02:27:30 -0800 From: Kris Kennaway To: Dag-Erling Sm?rgrav Message-ID: <20040108102730.GA55397@xor.obsecurity.org> References: <3FFC03E5.7010305@iconoplex.co.uk> <200401071429.i07ETZMI068819@grimreaper.grondar.org> <20040107200838.GD86935@freepuppy.bellavista.cz> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Mailman-Approved-At: Thu, 08 Jan 2004 06:43:19 -0800 cc: freebsd-hackers@freebsd.org cc: freebsd-chat@freebsd.org cc: Mark Murray Subject: Re: Where is FreeBSD going? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 10:27:32 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jan 08, 2004 at 11:09:49AM +0100, Dag-Erling Sm?rgrav wrote: > Roman Neuhauser writes: > > The ports freeze seems to last too long with recent releses. Or > > maybe it's just I've gotten more involved, but out of the last four > > months (2003/09/07-today), ports tree has been completely open > > for whopping 28 days. >=20 > I strongly suspect that this could be at least partially alleviated by > giving portmgr more package-building hardware to play with. It's certainly true that we're lacking in build hardware for some non-i386 platforms (particularly sparc64), and this made it pretty tricky to build packages for 5.2 on those architectures (a full sparc64 build takes at least a month). I've heard some rumours of donated equipment waiting to be installed, but I don't know what the status of that is. Likewise, a 5.2 i386 build takes about a week, which means that the freeze *cannot* be shorter than this, even if everything goes perfectly (which, in practise, never happens). This time around, the freeze started on 23 Nov and was lifted on 3 Dec. That's 10 days, which is about as good as you could hope for. If we could build packages in - say - a day, we'd be able to cut the freeze time down further, although I expect the duration would become limited by the speed at which problems can be corrected. Every now and then we get offers of access to a machine here or a machine there to help with building packages. The main problem with donating machine resources is that there's limited space in the freebsd.org equipment racks, and the package build system currently needs LAN-equivalent connectivity between the machines. To be useful we'd either need a full cluster of faster machines located somewhere, or to find time to rewrite the build scripts to work efficiently with remote build resources. Kris --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQE//TCRWry0BWjoQKURArzwAKCnIUZSbEPPntlK0rUPkcR/FjBTiACfTVlj rIJvecSvYBWt8R8TmViPgFw= =PkRG -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24--