Did the behavior of script_files (nee scripts) change? I'm pretty sure that some time ago, everything in bin or scripts was *not* installed by default, and I had to explicitly list what I wanted installed.
I need to duplicate this behavior, but script_files does not follow the principle of least surprise. The situation is that I have a single executable and a handful of symlinks pointing to that executable; when I do the install, I get multiple copies of the executable. What I'm trying to do is create a subclass with a custom ACTION_install that creates those symlinks for me in the destination directory. I need to have the symlinks in $BASEDIR/bin or $BASEDIR/scripts for development, so I don't have to run Build to get stuff into blib every time I want to run the scripts. With 0.30 this just creates a mess in the install destination directory. Ideas?
