Thanks Stefan!
Actually, this is slightly different I guess:
- the installation script you are linking manages the installation and the subsequent steps, but doesn't manage the dependencies: for instance on my machine, it didn't find root and so manalyzer doesn't support root.
Maybe this is just something to adapt?
Brew on the other hand manages root and so knows how to link these two together.
- The nice thing I like about brew is that one can "ship bottles" aka compiled version of the code; it is great and fast for deployment and avoid compilation issues.
- I like that your setup does deploy and launch all the necessary executables! I know brew can do this too via brew services (see an example here: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/r/rabbitmq.rb#L83 ), maybe worth investigating...?



> Hi Mathieu,
> 
> thanks for your contribution. Have you looked at the install.sh script I developed last week:
> 
>    https://daq00.triumf.ca/MidasWiki/index.php/Install_Script
> 
> which basically does the same, plus it modifies the environment and installs mhttpd as a service.
> 
> Actually I modeled the installation after the way Homebrew is installed in the first place (using curl).
> 
> I wonder if the two things can kind of be integrated. Would be great to get with brew always the newest midas version, and it would also 
> check and modify the environment. 
> 
> If you tell me exactly what is wrong MidasConfig.cmake.in I'm happy to fix it.
> 
> Best,
> Stefan