PB: We should add new recipe for AliRoot in O2 to include ZeroMQ as dependency.
BvH: What should we do for the packages that depend on Root? They are the same both for O2 and AliRoot/AliPhysics.
PB: We also should provide separate directory tree in CVMFS. In this way we will disentangle O2 and GRID, otherwise we may get confusion in the GRID environment. A dedicated discussion will be organised to clarify the details.
BvH: We also have to keep the O2 branch in GitHub since the versions we need in O2 and AliRoot may differ.
PB: Another related question is the future of the AliRoot/AliPhysics in Run3. Most probably we have to freeze them and provide a convertor for the old data to be able to use them in O2.
GE: One can use architecture switch to freeze the old code.
MR: What kind of dependency do we have in O2 on AliRoot? This is the HLT code we use via the HLT wrapper. Since it is only run-time dependency via the loading of a library, we better remove the compilation of AliRoot in O2. Only if somebody wants to use it, the compilation should be requested explicitly.
PH: Until we convert the HLT algorithms to O2, we should be able to use them from AliRoot.
MR: Another argument to remove the AliRoot as dependency of O2 is to make clear separation between the past and the future.
Action item: get rid of AliRoot as dependency in O2.
PH: What is still needed in the build system:
BvH: How is the software distributed on GRID?
Action item: Dario will present the software distribution on GRID.
PB: How is the single executable accessing the libraries with the actual code? Each library provides single entry point.
AM: Probably a single executable will cause difficulties to debug the code.
MA-T: Lets discuss the technical questions during the dedicated meeting.
GE: The set of steps in my example contains start, load, init of state machine.
MA-T: We have al least three different approaches. Anar uses preprocessor macros to compile different executables, Giulio has single executable with options, and Alexey is preparing similar example. Matthias also have example from HLT components. We have to provide the examples and the design descriptions in the beginning of next week before the meeting next Friday.
MR: It would be useful to have also summary slides for each approach.
MA-T: The main idea of this development is to reduce the copy/paste pattern.
Action item: make Indico page and book 53-R-044 for next Friday, 10:00 -12:30
MA-T: The progress with the Root CMake modules is slow since they do not support installations with separate prefixes for includes, executables, etc. One should use the FairRoot CMake modules for the moment.
Action item: merge the pull request of Barth after squashing. Reject Root5 if somebody tries to use it with O2.