On Dienstag, 25. April 2023 13:42:30 CEST Marcus Rückert wrote:
1. not sure that using the same element for multiple build descriptions and flavors within a build description is a good idea
2. how would you define something like
``` foo.spec: - flavor: postgresql15 - flavor: postgresql14
bar.spec: - flavor: postgresql15 - flavor: postgresql14 ```
with your new syntax?
Multiple expansion is currently only possible with package links. If you wan't 4 builds in total *without* links, you have to specify 4 flavors, and either use exactly one spec file (i.e. merge both, use conditionals inside), or create one for each flavor. Therefor my wish for multiple levels of expansion. Another possible syntax may be using nested flavors in the xml file: <flavor name="foo"> <flavor name="postgresql15"> <flavor name="postgresql14"> </flavor> <flavor name="bar"> <flavor name="postgresql15"> <flavor name="postgresql14"> </flavor> @BUILD_FLAVOR@ would be e.g. "foo_postgresql15" (probably also define @BUILD_FLAVOR_{1,2}@ as "foo" resp. "postgresql15"). Spec file lookup is: 1. foo_postgresql15.spec 2. foo.spec (For backwards compatibility, <flavor>foo</flavor> is the same as <flavor name="foo"/>). Regards, Stefan -- Stefan Brüns / Bergstraße 21 / 52062 Aachen phone: +49 241 53809034 mobile: +49 151 50412019