From owner-freebsd-arm@freebsd.org Tue Sep 29 03:03:10 2015 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24E7EA0B5BF for ; Tue, 29 Sep 2015 03:03:10 +0000 (UTC) (envelope-from george@ceetonetechnology.com) Received: from feynman.konjz.org (feynman.konjz.org [64.147.119.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 6528A185D for ; Tue, 29 Sep 2015 03:03:09 +0000 (UTC) (envelope-from george@ceetonetechnology.com) Received: from 127.0.0.1 (server17.ofertaslimitadas.com.br [178.17.174.99]) (authenticated bits=0) by feynman.konjz.org (8.14.7/8.14.4) with ESMTP id t8T33rno076581 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Mon, 28 Sep 2015 23:03:56 -0400 (EDT) (envelope-from george@ceetonetechnology.com) Subject: Re: Building Less? To: Warner Losh References: <1443104974.1224.269.camel@freebsd.org> <20150928162916.GU99677@funkthat.com> <56099A79.8020403@ceetonetechnology.com> Cc: "freebsd-arm@freebsd.org" From: George Rosamond Message-ID: <5609FF5F.2070705@ceetonetechnology.com> Date: Mon, 28 Sep 2015 23:02:55 -0400 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Sep 2015 03:03:10 -0000 Warner Losh: > Crochet isn't part of the base system. If you'd like something included > with crochet, you'll need to generate a patch, or talk offline with Tim. > Yes, so that's what I noted, Warner. I brought it up with Tim and thought it would be most appropriate in crochet, but others thought it should go into the base. I tend to think it's most relevant in crochet. > But it's unlikely that there will ever be a fully populated src.conf file in > the base system. It would be too much of a hassle. We've tried that in > the past, and is a big reason why we have /etc/defaults/rc.conf instead > of having a fully populated /etc/rc.conf file. Right. That makes sense to me... the defaults/ approach makes sense in both cases, but I still think it for crochet it's a sure move. > > Why? Well, we could generate it on each build. mergemaster could install > it. But it would be a guaranteed merge conflict as generated files tend > to be ugly to merge. If we were to keep it up to date by hand, which > might help a little on the merging problem, it would go stale quickly. > We learned that with the src.conf.5 man page. Got it. > > If we generated something and installed it in src.conf.sample, that might > be OK. However, it wouldn't be right for all platforms. The defaults are > different depending on what target you are building for. That might be > manageable though, since there are only a few of them. > Good insight. Thanks. So maybe I'll do the push request to freebsd/crochet and at least put it in the wind, for now. Just to repeat, I raised this for two specific reasons: 1. crochet makes explicit references to a src.conf file, so there should be a starting point/template, IMHO. 2. src.conf is useful for building a stripped down system where disk space, disk writes and memory are at a premium. g > Warner > > On Mon, Sep 28, 2015 at 1:52 PM, George Rosamond < > george@ceetonetechnology.com> wrote: > >> John-Mark Gurney: >>> Russell Haley wrote this message on Sun, Sep 27, 2015 at 21:21 -0700: >>>> The option should be included in the man pages for build: >>>> >>>> >> https://www.freebsd.org/cgi/man.cgi?query=build&sektion=7&apropos=0&manpath=FreeBSD+10.2-RELEASE >>> >>> [great additions] >>> >>> I agree that this needs better documentation... If you send me a patch, >>> I'll make sure it's marked up properly and committed... >>> >>> Thanks! >>> >>>> On Sun, Sep 27, 2015 at 9:06 PM, Warner Losh wrote: >>>> >>>>> src.conf is only used to build /usr/src. src.con(5) documents that. >>>>> build(5) has a pointer. >> >> On a related note, I submitted this last year after some offline >> discussions with Tim and others: >> >> >> https://www.freebsd.org/cgi/man.cgi?query=build&sektion=7&apropos=0&manpath=FreeBSD+10.2-RELEASE >> >> Of course src.conf(5) is useful enough as it is, but a populated file >> makes sense to me, at least for crochet, since it can easily be >> explicitly referenced in the script. I don't think the *average* x86 >> server builder is concerned with removing bluetooth, floppy support, ipf >> from base, but I think for those with SoC and embedded hardware, it does >> matter. >> >> The point is, it might be worth having a fully commented, comprehensive >> /etc/src.conf file in place, at least for crochet. >> >> g >> >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >> >