about configuration file in ditrack

[Vlad Skvortsov]

Ivan Glushkov wrote:
> Hello.
>
> Thoughts after reading i#176 and i#20.12.
>   

There is also i#168 that is relevant.

> 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:
>   

Even these sources that you are listing here come from different classes:
* categories, users and versions define the schema (database-specific);
* filters are shared among different clients (currently 'dt' and 'webui');
* listing formats are specific to command-line client only ('dt').

So stacking all this data into a single file seems wrong to me.

> 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?
>   

I'd like to get 0.6 out of the door as soon as possible, so my take on 
this is "any *improvements* to be postponed".

> 2. Current rules for writing 'listing-format' and all other configuration  
> files differ, it will confuse users.
>   

True, but it's a tradeoff we have to make.

> 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.
>   

I don't think it's a big deal provided there is an automatic conversion 
utility. We never guaranteed for the data formats to remain stable (come 
on! it's pre-1.0 version!).

Summary: -1 on changing all configuration before 0.6.

-- 
Vlad Skvortsov, vss at 73rus.com, http://vss.73rus.com