
hmm.. what about splitting config file into template and then what the user actually wants... that makes cvs updates easier i think. i mean there would be a config.pm with all the stuff in it and then an config.user.pm which is loaded after config.pm where you just copy&paste the values you want to change from the default. so you can always easy see what you changed from default values. bastian

Hi Bastian, On Fri, Oct 25, 2002 at 05:53:31PM +0200, Bastian Hoyer wrote:
hmm.. what about splitting config file into template and then what the user actually wants... that makes cvs updates easier i think.
i mean there would be a config.pm with all the stuff in it and then an config.user.pm which is loaded after config.pm where you just copy&paste the values you want to change from the default. so you can always easy see what you changed from default values.
That's sound good. :-) But I would change it. Kernel/ConfigDefault.pm (default values, loaded at first) Kernel/Config.pm (just your own config changes, loaded after Kernel/ConfigDefault.pm) And the update would be much easier (CVS/RPM/tar). You never have to update to a new config system/format... A good idea! By default there would be no Kernel/Config.pm in the tar.gz. Just one like Kernel/Config.pm.dist. And this would be a good update solution for tar.gz user! To all: What do you think? PS: Thanks Bastian!
bastian
Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ -- Old programmers never die. They just branch to a new address.
participants (2)
-
Bastian Hoyer
-
Martin Edenhofer