> It's not really necessary to have a big config file, you can remove the > comments: > sed -i 's/#.*//' /etc/freevo/local_conf.py > remove any trailing whitespace: > sed -i 's/ *$//' /etc/freevo/local_conf.py > remove any blank lines: > sed -i '/^$/d' /etc/freevo/local_conf.py > Tidy it up: > /path/to/freevo/contrib/developer/reindent.py /etc/freevo/local_conf.py > > This should cut the file down quite a lot.
I don't think that the physical size of the file is the issue (I'm sure the OP can correct me if I'm wrong) but just the amount of stuff that is configured in one file. This would be ever worse if all the white space and comments were removed! As it stands there are lots of cryptic variables with little help beyond the commends and checking the mailing list about how things should be configured. For a first time user who is present by this one massive config file, with the dire warning that if you get your white space wrong you can stuff it all up (and I have in the past) this is quite intimidating. If this can be split out as you suggested into smaller sub config files, this will make life less scary for a new user. However I do really think that the reliance of a python file for config should be removed altogether. I've had problems in the past with variables changing names etc. and forgetting to run the migration script. If these are sanitised out into a config file then the internal variables can be renamed without having to update the users config file. This will provide a more stable design and remove the visibility of internal variable names to end users. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Freevo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freevo-users
