From owner-freebsd-ports@FreeBSD.ORG Fri Mar 31 21:04:07 2006 Return-Path: X-Original-To: freebsd-ports@freebsd.org Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4353616A400 for ; Fri, 31 Mar 2006 21:04:07 +0000 (UTC) (envelope-from cperciva@freebsd.org) Received: from pd2mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id E4CDD43D45 for ; Fri, 31 Mar 2006 21:04:06 +0000 (GMT) (envelope-from cperciva@freebsd.org) Received: from pd4mr7so.prod.shaw.ca (pd4mr7so-qfe3.prod.shaw.ca [10.0.141.84]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IX000MWDFUUS440@l-daemon> for freebsd-ports@freebsd.org; Fri, 31 Mar 2006 14:04:06 -0700 (MST) Received: from pn2ml10so.prod.shaw.ca ([10.0.121.80]) by pd4mr7so.prod.shaw.ca (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IX0001TCFUU90J0@pd4mr7so.prod.shaw.ca> for freebsd-ports@freebsd.org; Fri, 31 Mar 2006 14:04:06 -0700 (MST) Received: from [192.168.0.60] ([24.82.18.31]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0IX000DZ8FUTATW0@l-daemon> for freebsd-ports@freebsd.org; Fri, 31 Mar 2006 14:04:06 -0700 (MST) Date: Fri, 31 Mar 2006 13:04:05 -0800 From: Colin Percival To: freebsd-ports@freebsd.org Message-id: <442D9945.7050001@freebsd.org> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-Enigmail-Version: 0.94.0.0 User-Agent: Thunderbird 1.5 (X11/20060112) Subject: FreeBSD Update and !i386 platforms X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 31 Mar 2006 21:04:07 -0000 I'm not subscribed to this list, but I hear that there have been some questions about FreeBSD Update and !i386 playforms here. The current situation is as follows: 1. The client code works on several platforms (the ones listed as working in the port). 2. The server code might work on some non-i386 platforms, but probably not. 3. In any case, I'm not building updates for non-i386 systems yet. The client port is marked as working because, well, it does work. As long as there are updates for it to fetch. :-) For what it's worth, getting the FreeBSD Update build code running on other platforms, and getting updates built for at least AMD64 (other platforms will depend upon the demand and availability of build hardware) is one of my goals for the summer if I can raise enough money: http://people.freebsd.org/~cperciva/funding.html Colin Percival