Building Less?

[George Rosamond]

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 at 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 <imp at bsdimp.com> 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 at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to "freebsd-arm-unsubscribe at freebsd.org"
>>
>