[dev] default backends

[Michael M Slusarz]

Quoting Ronan SALMON <rsalmon at mbpgroup.com>:

> Jan Schneider <jan at horde.org> a écrit :
>> Zitat von Vilius ?umskas <vilius at lnk.lt>:
>>
>>> Sveiki,
>>>
>>> Monday, February 14, 2011, 9:58:33 PM, you wrote:
>>>
>>>> Quoting Michael M Slusarz <slusarz at horde.org>:
>>>
>>>> - Why are we forcing changes to be in the *.local.php files anyway?
>>>> This only makes sense if installing from git.  Most users will be
>>>> directly editing the default files and this isn't a bad thing.  If we
>>>> are concerned about changing/adding default values when upgrading, I
>>>> don't believe this has really been a problem in the past.
>>>
>>>> Forcing changes to *.local.php instead of *.php just makes things that
>>>> much more complicated.  I can't really think of another project that
>>>> requires people to do this.  And it sort of defeats the whole purpose
>>>> of storing the default "config" files in config/ in the first place.
>>>> These new default files are instead hardcoded values and if users
>>>> really aren't supposed to be touching them, they should be nowhere
>>>> near the config/ directory.
>>>
>>> As an ex-admin I agree here with Michael completely. Usually what I do
>>> when upgrading, is:
>>>
>>> 1. Backup whole Horde tree.
>>> 2. cvs/git update it.
>>> 3.  diff the new config files with backup config files for changes and
>>> adjust new files accordingly.
>>
>> Thanks for this example that clearly shows why the old way was not  
>> perfect and the new way is much better. After these changes, what  
>> you to is:
>> 1. Update the Horde tree.
>
> I agree with Jan here. I find the *.local.php files really handy.  
> Especially when you will upgrade Horde and Horde apps, you'll  
> automatically get the new settings.

I have no issue with keeping *.local.php files as a way to  
automatically override config defaults.  In fact, anybody  
installing/updating from git requires these files rather than changing  
the default files.

michael

-- 
___________________________________
Michael Slusarz [slusarz at horde.org]