Community
Participate
Working Groups
Take the following common use case. We build a P2 repository that contains a product. Ideally this repository contains launchers for all possible platforms so the build is not targeted against any platform in particular. Next, we want to build zip files that contains ready-to-run products. This build step should be repeated, once for each desired combination of os/ws/arch. The Buckminster CSPEC cannot describe this today. In order to do that, we must add a way to repeat parts of the build using different property sets.
We had a brief design session on this, and here is some more input: - we discussed using either a matrix declaration where combinations are created "automatically" but then requiring excluding "impossible combinations", or explicit stating each combination manually. The manual approach has the advantage of also serving as a location where declarations per combination can be made, and it is also possible to name and reference each combination. Explicit stating each combination seems to be the best option. - it should be possible to declare the combination directly in the spec, but it should also be possible to refer to a property file per combination. - naming each combination should be convenient (it is typically going to include the variables).
dimensions should be specified first, each combination states the values (in the same order). The default name of a combination atribute should be the set of values.
