Outlined a strategy for a series of meetings in which existing solutions, in use in HEP, would be described. We’ll look for commonality of needed features, describe pros and cons, and try to build consensus on choosing a starting point and adapting it to the needs of all of the interested groups. Ben has volunteered to go first with the following discussion of home-brew.
Home-brew is a Ruby-based package manager see http://brew.sh
It is hosted on gitHub; has 9 contributors and uses a BSD 2 Clause (NetBSD) license.
There is a ruby script for each package that defines it’s “build protocol” see slides for example
Prototypes for SuperNEMO and DUNE on gitHub
- works out of the box
- very easy to use and add new packages
- good support for build variants and c++ standards
provides one single rolling release
no direct support for git tags or rollback on versions
binary packages not relocatable
Discussion: It maybe possible to use taps to support more then one release. All agree that one release would be a show stopper. Most also agree that packaging has to support relocatability.