Thank you Rob for your response.
I thing an important point to not forget is whatever the solution we choice, it must be easy to upgrade to new version for both the user and the maintainer. If possible integrated in the INDI repo and using similar tools.
This introduction to say I have a software resembling your point 6) I do a few years ago that run on Linux and Mac:
github.com/pchev/indistarter/wiki
But written using FreePascal and probably too much dependant on me, this can be use as an option but not as a global solution.
From what I understand, to upgrade a Homebrew recipe to a new version you just have to update the source download url, and eventually the build script to add new drivers.
With Bottles you can save the compilation time by installing directly the binaries instead, I think all the build dependencies I installed use Bottles and this is very quick.
About distributing binaries, what is your experience with INDI binary compatibility across MacOS version? do you use macosx-version-min ?
If automatic compilation is still required for the users it is important this is as simple as possible, for example do not require a full Xcode installation.
I not use Cask but if I understand correctly this just automate the install of an external package. You still need to build this package in some way first. This look more interesting to add something to /Applications.
I never use Craft, so I cannot give an advice here.
I not use them but I see there is build script for Dockers image with the INDI sources. Is Docker easily available on Mac? Is it a possible solution?
Yes, Web Manager is very interesting but this can be done in a second time, after the server command line is available. This can be for example another brew with the command line brew as a dependency.
Do you have a repo somewhere with your scripts to take a look?
Patrick