about configuration file in ditrack

[Ivan Glushkov]

Hello.

Thoughts after reading i#176 and i#20.12.
I suggest to use single configuration file, for example issues/etc/config,  
that will combine all current configuration files (categories  filters   
listing-format  users  versions). There are several reasons for that:

1. To begin to use new 0.6 version of ditrack all current users should  
convert there database from v2 to v3. We've already changed database  
format, why not make all jobs this time?
2. Current rules for writing 'listing-format' and all other configuration  
files differ, it will confuse users.
3. In the next release(s) we will undoubtedly begin to use Python standard  
library for parsing all residual configuration files (or more, will begin  
to use the single configuration file). So all users once more will have to  
convert there databases.

Opinions?

Ivan.