I’ve come across a couple cases now where a binary-only package that just provides commands need paths
./configured in for state / config, but don’t have any persistent service component.
I’ve been wondering how to approach this besides having a dummy service and requiring it to be started at least once before any of the commands get used. What I’m thinking of doing right now is adding a
setup_runtime_env script to the build artifact that initializes the /hab/svc paths manually and maybe copies some config, and then creating a parallel
bin-wrapped directory that has a copy of every command from the build’s
bin wrapped in a script that calls
setup_runtime_env first to expose instead. That would have the added bonus of making commands work while binlinked that need env
Are there any problems with that approach I’m not seeing? Another approach I’m not considering? More blessed paths on the horizon?