That is a very dangerous flag as it's written today. Imagine this workflow:abique wrote: I added an option --no-presets
This is something like:Code: Select all
if test "$NO_PRESETS" -eq 1 ; then find "$HOME/.u-he/$PRODUCT/Presets/$PRODUCT/" \ \( -type f -a -iname '*.h2p' -a -not -iname 'initialize.h2p' -a -delete \) \ -o \( -empty -a -delete \) fi
1. user installs Zebra without --no-presets to get the factory presets.
2. user customizes the preset directories and makes several custom presets
3. an update comes out and the user wants to upgrade Zebra2 but doesn't want the update to fill the directory with the original factory sounds.
4. user sees --no-presets flag and installs the new update using it.
5. *poof* all presets except one(s) names initialize are deleted.
I'd recommend naming that flag --rm-installed-presets at the very least.
