From owner-freebsd-current@FreeBSD.ORG Sat Nov 10 11:55:11 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1DB621CB for ; Sat, 10 Nov 2012 11:55:11 +0000 (UTC) (envelope-from mueller23@insightbb.com) Received: from mail.insightbb.com (smtp1.insight.synacor.com [208.47.185.23]) by mx1.freebsd.org (Postfix) with ESMTP id BFDCC8FC14 for ; Sat, 10 Nov 2012 11:55:09 +0000 (UTC) X_CMAE_Category: 0,0 Undefined,Undefined X-CNFS-Analysis: v=2.0 cv=f43K9ZOM c=1 sm=0 a=Dm9TOXL4taQ+Gy1KovpL+A==:17 a=2yuFT1btKP0A:10 a=jLN7EqiLvroA:10 a=9YQ-1ebCAAAA:8 a=70HuqxjXubIA:10 a=7YfXLusrAAAA:8 a=6I5d2MoRAAAA:8 a=8ggJXkvBAAAA:8 a=FP58Ms26AAAA:8 a=vHG5aY3EgAWcfBMW-qMA:9 a=XvKbGIMP6GoA:10 a=Dm9TOXL4taQ+Gy1KovpL+A==:117 X-CM-Score: 0 X-Scanned-by: Cloudmark Authority Engine Authentication-Results: smtp01.insight.synacor.com smtp.mail=mueller23@insightbb.com; spf=softfail; sender-id=softfail Authentication-Results: smtp01.insight.synacor.com header.from=mueller23@insightbb.com; sender-id=softfail Received-SPF: softfail (smtp01.insight.synacor.com: transitional domain insightbb.com does not designate 74.130.198.7 as permitted sender) Received: from [74.130.198.7] ([74.130.198.7:54745] helo=localhost) by mail.insightbb.com (envelope-from ) (ecelerity 2.2.3.49 r(42060/42061)) with ESMTP id 38/2F-17144-7904E905; Sat, 10 Nov 2012 06:55:03 -0500 Date: Sat, 10 Nov 2012 06:55:03 -0500 Message-ID: <38.2F.17144.7904E905@smtp01.insight.synacor.com> From: "Thomas Mueller" To: freebsd-current@freebsd.org Subject: Re: [head tinderbox] failure on arm/arm Cc: Brett X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 Nov 2012 11:55:11 -0000 from Brett : > Just an observation: a few years ago when I got sick of Linux's "headlong rush" development model, I subscribed to various BSD mailing lists to see what > +else was out there. I considered FreeBSD at the time - there was a neverending avalanche of "[head tinderbox] failure" messages. This told me that I would > +be more likely to be running code written by people who knew what they were doing if I went with Open, Net, or DragonflyBSD. > I safely run OpenBSD-current on my main computer and it always works (I think I have had 2-3 build problems in about 3 years, and they were all my fault). > At the moment, I only feel confident enough with FreeBSD-current to run it on my unimportant torrent computer. This is 80% due to constant build failures, > and 20% due to invasive changes being introduced with documentation/instructions scattered over many different pages and mailing lists, e.g: > http://wiki.freebsd.org/FrontPage?action=fullsearch&context=180&value=xorg&titlesearch=Titles > http://wiki.freebsd.org/FrontPage?action=fullsearch&context=180&value=pkgng&titlesearch=Titles > Hypothetical user: "Is it WITHOUT_PKGNG= or WITHOUT_PKGNG=yes or WITH_PKGNG=no today?" > I wonder how many other people that you never hear from feel the same, and if some sort of "x weeks commit freezeout" should apply to the build breakers. > Cute pointy hats or whatever obviously have no effect. > Rant over! I too had monstrous problems rebuilding all ports that depend on png. But I am not really satisfied with the other BSDs. NetBSD is hit-or-miss to build successfully, more miss than hit. NetBSD supports GPT awkwardly but has no support for USB 3.0. NetBSD is rather unstable. I think I'd trust FreeBSD-current over a stable or release version of NetBSD. How does OpenBSD compare in that regard? I think DragonFlyBSD just introduced USB 3.0 support in 3.2.1, but that is off by default. There are live USB images available for DragonflyBSD from www.dragonflybsd.org, and live USB images available for OpenBSD at liveusb-openbsd.sourceforge.net . I'd like to try, just to see what they look like and how or if they support my hardware. Tom