This is already done in many places in the pipemenus, but if all calls to scripts in bunsen-utilities were preceded by a test before adding the menu item, like this in bl-tint2-pipemenu:
loadRestartmenu(){
if [ "$(pidof tint2)" ];then
if type bl-tint2restart &>/dev/null;then # bl-tint2restart script found
menuItem "Restart Tint2" "bl-tint2restart"
fi
fi
}
then bunsen-utilities would not have to be a hard dependency of bunsen-pipemenus. A Recommends: would be enough, and the menu items needing those scripts would just be missing if the package wasn't installed.
For example, at present there is no such test for bl-tint2zen in the same pipemenu.
This is already done in many places in the pipemenus, but if all calls to scripts in bunsen-utilities were preceded by a test before adding the menu item, like this in bl-tint2-pipemenu:
then bunsen-utilities would not have to be a hard dependency of bunsen-pipemenus. A Recommends: would be enough, and the menu items needing those scripts would just be missing if the package wasn't installed.
For example, at present there is no such test for bl-tint2zen in the same pipemenu.