Ok, I see the point about generated stubs. But generating linear combinations of nsis compile time options as their own packages, like
nsis nsis-common nsis-log nsis-common-log nsis-8kstr nsis-common-8kstr nsis-log8kstr nsis-common-log8kstr wouldn't that be a bit too exorbitant for the purpose? As far as I can see it, the argument about logging not recommended to be activated by default was a size difference of generated installers being in single digit kB range. And about NSIS_MAX_STRLEN=1024 vs. NSIS_MAX_STRLEN=8192 it seems to be a similar argument, which I guess is slightly reduced RAM usage peaks when executing the generated installer. As long as I am not missing anything here, I would just enable both options by default instead of all the burden of maintaining separate packages for all considerable options.
