I feel tenshi.conf can be a highly individualized configuration file. It is difficult to quickly evaluate the changes if you compare the new config with your own config (using dispatch-conf or etc-update). I personally prefer to update the new config against the old config and then manually migrate relevant changes into my own config. Hence so far I have manually adjusted the config files before running dispatch-conf. I got tired of it yesterday and changed the start script to read from /etc/conf.d/tenshi what configuration file to use (optionally). Reproducible: Always If you do not have the /etc/conf.d/tenshi configuration (TENSHI_CONFIG=), the init script will do the same as in tenshis current configuration (fallback). I personally have set TENSHI_CONFIG=/etc/tenshi/tenshi_${HOSTNAME}.conf and leave the original configuration file untouched (/etc/tenshi/tenshi.conf).
Created attachment 128740 [details, diff] tenshi_init.d.patch
tenshi supports an 'include' directive that allows you to include other conf files, you can just use that for your own whatever.conf and always ignore new config versions.
