[M3devel] CM3 RELENG: suggestion for distribution packages

[Tony Hosking]

I would argue strongly that a use would *not* want to change the  
config file.  It's definitions are intrinsic to the installation.

On 28 May 2009, at 13:00, hendrik at topoi.pooq.com wrote:

> On Thu, May 28, 2009 at 12:32:20AM +0000, Jay wrote:
>>
>> I'm still of the opinion that these might not be configuration files.
>> Just because they are text, doesn't make it so.
>> Just because /some/ people edit them, doesn't make it so.
>> If lots of people edit them, then it is more convincing.
>>
>> It is a gray, but I suspect the mere naming of the files, and the  
>> fact that install used to always change them (but it doesn't now)  
>> has everyone convinced.
>>
>> One of the questions is, what happens upon "upgrade"?
>> Is that supposed to leave /etc alone, and keep working with  
>> whatever is out there? I'd maybe rather not be limited like that.  
>> (But I actually build-in a lot of backward compat so that I can  
>> bootstrap using current config files, which I can control, instead  
>> of whatever the old releases came with; this is however a  
>> difference between the Tinderbox and my own workflow..)
>> Or keep churn low so that upgrade can do some merge? Ditto.
>
> If theyre not configuration files, then, of course they should *not*  
> be
> in /etc.  Is there any chance that the cm3 user might want to change
> them?  I'm not talking about making an entirely new set while
> cross-building for another system here.
>
> -- hendrik