I stumbled a number of times over various influences between multiple activation scripts. At the moment they are simply concatenated strings and have no semantic barriers. I think this is to optimize for performance which I completely support.
However, we had a few scripts that required setting umasks and the activation script early on sets up a umask that is “promised” to the snippets so that one has to take care of not influencing other scripts.
Is there a reason not to simply wrap all snippets into a
() subshell? Would this be prohibitive from a time/space perspective? We started doing so for our individual snippets (and might do this in our wrapper automatically). An alternative option could be to add an option to snippets to “fence” them off by wrapping them, however, having to discover this option would mean someone could just write the
I’d like to consider whether having the activation snippets being fenced off like this by default is worthwhile …