The attached patch (can't inline, as Gmail will break formatting)
abstracts the config file lookup, allowing for a CDRDAO_HOME
environment variable to be added. This makes it possible to specify
some other location than $HOME for the configuration file.
The reason for this feature is to allow users, such as me, to put
their configuration file some other place than .cdrdao. Also, seeing
as how cdrdao reads $HOME/.cdrdao-drivers, making it possible to place
these two files in a subdirectory such as CDRDAO_HOME=$HOME/cdrdao
If CDRDAO_HOME is set, cdrdao will now look there instead for a file
with the same name as the old configuration files, but skipping the
I've added documentation to the manual page.
I noticed also that $HOME/.cdrdao-drivers is not mentioned in the
manual page. Is that intentional?
Thank you for an excellent piece of software!
Get latest updates about Open Source Projects, Conferences and News.