Talk:Script - commercialremover

Just some clarification about the configuration file. MythTV has been writing a config.xml since 0.21, so there is no reason to bother looking for a mysql.txt, aside from the fact that it can be trivially "sourced" into bash scripts (grepping line by line is unnecessary). From 0.26 onward, the config.xml file changed formats, and you seem to support both, but incorrectly based off location. The file was never stored in /etc/mythtv/config.xml. The only two locations it is ever stored to and retrieved from is first ${MYTHCONFDIR}/config.xml, falling back to ${HOME}/.mythtv/config.xml if ${MYTHCONFDIR} is not defined. If this script is run as a user job, those environmental variables will be carried over from the backend that runs it, and will be available to the script, so there is no need to hard-code them to some place such as /etc/mythtv/. wagnerrp 14:09, 23 November 2013 (UTC)