From owner-freebsd-arm@FreeBSD.ORG Thu Dec 26 20:20:24 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6A56BC40; Thu, 26 Dec 2013 20:20:24 +0000 (UTC) Received: from nibbler.fubar.geek.nz (nibbler.fubar.geek.nz [199.48.134.198]) by mx1.freebsd.org (Postfix) with ESMTP id 498D21F35; Thu, 26 Dec 2013 20:20:24 +0000 (UTC) Received: from bender.Home (97e07ae8.skybroadband.com [151.224.122.232]) by nibbler.fubar.geek.nz (Postfix) with ESMTPSA id B1BA65E002; Thu, 26 Dec 2013 20:20:22 +0000 (UTC) Date: Thu, 26 Dec 2013 20:20:16 +0000 From: Andrew Turner To: Glen Barber Subject: Re: FreeBSD 10.0-RC3 Now Available Message-ID: <20131226202016.3071b815@bender.Home> In-Reply-To: <20131226195512.GA13109@glenbarber.us> References: <20131226162521.GK2009@glenbarber.us> <2B79BF2A-1798-40F5-AD6E-D560E9C6C1E7@freebsd.org> <20131226194830.4f6e5b13@bender.Home> <20131226195512.GA13109@glenbarber.us> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-arm ml , FreeBSD Release Engineering Team X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 20:20:24 -0000 On Thu, 26 Dec 2013 14:55:12 -0500 Glen Barber wrote: > On Thu, Dec 26, 2013 at 07:48:30PM +0000, Andrew Turner wrote: > > On Thu, 26 Dec 2013 10:25:09 -0800 > > Tim Kientzle wrote: > > > > > > > > On Dec 26, 2013, at 8:25 AM, Glen Barber wrote: > > > > > > > The third RC build of the 10.0-RELEASE release cycle is now > > > > available on the FTP servers for the amd64, i386, ia64, powerpc, > > > > powerpc64 and sparc64 architectures. > > > > > > What do we need to include some ARM images? > > > > > > At a minimum, I would love to get an official RC3 build for RPi. > > > > I would suggest we could build a tarball of armv6 userland and an > > RPi image to dd to an SD card. > > > > Building the former should be straight forward. > > > > For the latter, assuming the release target is unable to build the > > required U-Boot binary, we could use crochet. I'm not sure if we can > > use a tarball as the input for this to guarantee both are the same. > > > > The problem with using crochet is that it requires git on the build > machine, which just adds to the minimum dependencies needed, both for > crochet itself, and (last I was aware) an external uboot tree. Github allows you to use svn to checkout a git repo with svn. There is an option under the clone url to set it to subversion. U-Boot should just be a tarball, if it is a git repo we would need to make it a tarball for the release to supply the source as it is GPL. > Maybe it is just more sensible to take what crochet is doing, and make > that into a release target. Yes, but I assume this is not feasible for 10.0. Andrew