[asterisk-dev] builtin values and CLI changes in res_features

Eric "ManxPower" Wieling eric at fnords.org
Tue Sep 4 17:16:10 CDT 2007


Michiel van Baak wrote:
> On 16:05, Tue 04 Sep 07, Caio Begotti wrote:
>> Hi, I'm looking to know what do you guys think about the changes
>> posted at: http://bugs.digium.com/10524
>>
>> I've talked to Junk-Y and he told me the CLI changes are nice but
>> he's not so sure about removing default builtins. My argument is in
>> the link above, but it's that having default builtins for features
>> like transfer and parking is wrong when you must set a blank value to
>> set it off.
>>
>> I just don't know wheter it's "wrong and silly" or "wrong but
>> acceptable for most people". That's why I'm asking for input :-)
>>
>> There are samples attached in 10524 showing what changes as well. Do
>> you think this can be commited in trunk or removing default builtins
>> such like that is risky?
> 
> Removing defaults is something you cant do that easily.
> people depend on them.
> 
> What's wrong with the defaults if you state in the
> upgrade.txt that you can now alter all this stuff and also
> alter the sample config to reflect the new possibilities ?

Why not take the hardcoded defaults out of the source code and put them 
in feature.conf where they should have been in the first place?



More information about the asterisk-dev mailing list