[ANNOUNCE] vdrcm-0.0.2 - interactive console dialogs script for managing VDR configuration files
Lucian Muresan <lucianm <at> users.sourceforge.net>
2016-01-09 18:43:45 GMT
vdrcm-0.0.2 - the VDR Config Manager for managing VDR configuration
files is now available at .
What is this all about? You may remember the ARGSDIR feature introduced
in VDR last year, which allows to store all the CLI parameters supplied
to VDR and its plugins spread over several files with the extension
*.conf in INI style, located for example in the /etc/vdr/conf.d
directory. They only need to contain INI sections named like [vdr] or
[plugin-name], followed by one option per line, then vdr launched with
no CLI-parameters at all will read these files in their file name order.
Just like other implementations (for example vdrctl used by yaVDR),
vdrcm will actually symlink config files from a pool directory
/etc/vdr/conf.avail to ARGSDIR, when it enables a plugin, or delete the
symlink only, when disabling it. It also lets you define the explicit
order of the plugins, by prefixing the symlinks with a number, or fires
up the text editor defined in the EDITOR environment variable, and all
this interactivlely in a CLI console, by using whiptail or dialog, see
sreenshots at . Note that the screenshots are from version 0.0.1,
running with dialog, now I noticed that whiptail looks a lot better and
is now preferred if both are present on the system.
There is also a non-interactive pure CLI-mode supporting enabling or
disabling a plugin by its name, and promoting the order of a plugin
before another one, by the index before re-ordering. These CLI-options
should be suitable for writing a true vdr Plugin for managing plugins,
which should need to call these commands with setuid in order to be able
to execute them, and scan the directories for refreshing the list of
available/active/inactive plugins in the OSD. There were such type of
plugins in the past, but they were too distribution-specific. The
ARGSDIR-feature would allow any distribution to use this type of
VDR/plugins configuration, therefore also the usage of the same
management tools for them. I'm planning to write such a plugin in the
near future, as spare time will permit it.
The runtime dependencies of vdrcm are quite basic:
- pkg-config (optional, see README for a workaround when missing)
- whiptail or dialog (optional if only the CLI-mode is used).
For more information and a short visual usage summary, check the
README.md at the homepage.
vdr mailing list
vdr <at> linuxtv.org