Opened 15 years ago
Last modified 15 years ago
#261 new task
allow multiple config files
Reported by: | Peter Johansson | Owned by: | Peter Johansson |
---|---|---|---|
Priority: | major | Milestone: | svndigest 1.0 |
Component: | configuration | Version: | trunk |
Keywords: | Cc: |
Description
We should allow multiple config
files. This implies that user can have one config
file specific for the project that is analyzed (digested), but also a global config
that contain settings that the user always want to use. These should not be two different kinds of files and absolutely not two kinds of Configuration classes. Rather what it means is that load(istream&)
function in Configuration should be called twice.
I suggest the following schema
- Create Configuration object
- If $HOME/.svndigest/config exists load Configuration object from that file
- If <root>/.svndigest/config exists load Configuration object from that file
- If option
--config-file
is given and file exists load Configuration (if file does not exist exit)
In case several files are loaded and an option is set in multiple files, the latter file overrides the former one.
Note: See
TracTickets for help on using
tickets.
I am not sure about this ticket. Perhaps usability will not improve but only get more confusing. I move this to the future.