peal.preflight.configs_in_script¶
- peal.preflight.configs_in_script(path)[source]¶
Every –config argument a reproduction script passes, in order.
The scripts use shell loops,
for METHOD in ace dime sce; do ... done, so a config path may contain${METHOD}. Reading the literal text would report a config that does not exist when the loop in fact expands to several that do. Loop variables are therefore collected and substituted, one emitted config per value. A variable that is never bound by aforis left as written, so it still shows up as missing rather than being silently dropped.