ROOT project has very sophisticated, solid infrastructure and build system, BUT it’s for internal use only by ROOT team experts.
My idea is to take the best from it and create some “skeleton framework” for “public usage” with “golden stamp of guarantee of superior quality” (like this ASCII art) from ROOT experts. I think the code from other frameworks (AliRoot, CMS, FairRoot etc), and even from MicroSoft .NET, Google Android can be used.
We want to stay platform independent, and we use CMake. If you combine these two you’ll end up with what’s called “CMake superbuilds”. And that’s what we are aiming for. It’s very close to what Rene proposed many years back as “BOOT”, which equals superbuilds plus the download of the binaries. But that sounds like something we should be able to address, too.
For “now” (2023…) I’d like to have the first ROOT modules being moved to superbuilds. We will start with those which no other ROOT modules depends on - say Davix, the SQL ones, etc.
Once we have that fully rolled out, people can download / install a small ROOT core, and get whatever else they need on demand. In the beginning by building it, later by downloading the relevant shared library etc (“build artifacts”). Is that along the lines of what you were thinking?
Because we don’t want to / cannot tie our users to any of them, and because it doesn’t solve the underlying issue we have: layered builds where we provide say mysql on top of a minimal ROOT distribution.
That said, ROOT is available through many, many package managers, so if that’s what you’re after, please just make use of it!
Rene say about 10K rootalk and 30K, but as he claim there are millions of students who don won complicity of C++
You know, some time I said Rene every physick hate you cos you kill PAW. I said, give me a chance and I return tis interpreter back
His answer was NOT and he tell every sci must learn the learning curve - Genius idiot