Date: Thu, 26 Dec 2013 21:48:58 -0700 From: Warner Losh <imp@bsdimp.com> To: Glen Barber <gjb@FreeBSD.org> Cc: freebsd-arm ml <freebsd-arm@freebsd.org>, FreeBSD Release Engineering Team <re@freebsd.org> Subject: Re: FreeBSD 10.0-RC3 Now Available Message-ID: <30F75F2D-A42B-410F-8FB0-C930729AF1D5@bsdimp.com> In-Reply-To: <20131227042055.GS13109@glenbarber.us> References: <20131226162521.GK2009@glenbarber.us> <2B79BF2A-1798-40F5-AD6E-D560E9C6C1E7@freebsd.org> <20131226194830.4f6e5b13@bender.Home> <AB7A24B9-A7FF-4364-8257-B8DF0E75A462@bsdimp.com> <7684A21C-4451-44ED-A11A-C03EF7850F01@freebsd.org> <20131227025814.GQ13109@glenbarber.us> <22576EF1-B4AB-4174-81E7-CF2A77594FAC@freebsd.org> <20131227032555.GR13109@glenbarber.us> <8A587B4F-40C8-43A2-A5FF-64214CC1F268@freebsd.org> <20131227042055.GS13109@glenbarber.us>
index | next in thread | previous in thread | raw e-mail
On Dec 26, 2013, at 9:20 PM, Glen Barber wrote: > On Thu, Dec 26, 2013 at 08:08:32PM -0800, Tim Kientzle wrote: >> On Dec 26, 2013, at 7:25 PM, Glen Barber <gjb@FreeBSD.org> wrote: >> >>> Well, no. :( The time-consuming part is the dependency chain for the >>> build. Such as, RPI-B needs python, gsed, and world+dog. BeagleBone >>> needs cross-gcc, and I'm sure other stuff. >>> >>> It would be pretty cool if crochet could have a '-D' flag to 'show >>> missing dependencies for board specified’. >> >> I’ve not yet come up with a particularly clean way to >> do that within Crochet, but there are a few ideas >> I’ve not yet tried. >> >> It does occur to me that at some point crochet >> is trying to do package management and maybe >> that’s a bad thing. >> >> But here’s an idea that might get exactly that: >> I’ve considered literally building board images as >> ports/packages. >> >> E.g., >> >> $ cd /usr/ports/freebsd/raspberry-pi >> $ make >> ... builds/installs python, gsed, boot bits, etc as necessary via port dependencies >> ... builds world/kernel (using non-root path…) >> $ sudo make install >> ... creates disk image and installs world/kernel/boot bits >> > > Hmm. I think you're on to something here. I'd include '-build' in the name, so we can still have port that's to install on the rpi... >> I don’t think this actually requires much effort >> to get this working, and it would have some >> interesting side-effects (like having RPi images >> spit out regularly by the package cluster). >> > > Maybe we don't need to go that far. But building a port that includes > the dependencies needed to do the actual image build would be a *huge* > bonus from the releng side. Meaning, if there was a port that I could > install that would give me all the necessary bits to create an image for > a specific board, that's a big step forward. > > Plus, the package builders don't actually 'buildkernel', so offloading > releng tasks to portmgr is not really scalable (meaning, if head/ > arm/armv6 is broken, etc...). I'm not sure I understand what you are saying here... Warnerhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30F75F2D-A42B-410F-8FB0-C930729AF1D5>