#23: suggestion: wildcards for filenames in recipe attributes -------------------------+----------------------- Reporter: olichtne | Owner: somebody Type: enhancement | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | Blocked By: Blocking: | -------------------------+----------------------- Currently we can distribute our recipes into several files by using the attribute source. While this is very useful and can generally make recipes more readable, in some cases you can end up with a number of parent recipes differing in only a few characters in filenames. This can of course continue recursively and will result in a significant number of files that are almost the same.
I discussed this with Jirka and the idea behind solving this problem is to start supporting wildcards for filenames. The implementation also shouldn't be very complex, but will require some changes that can potentially break the existing recipes again.
Since using wildcards basically means to use several different files and therefore recipes, I would first implement support for multiple recipes in one "parent" file like something we can see in beaker recipes. But this would require adding a new tag to our XML scheme and therefore breaking the recipes.
After this part is done implementing support for wildcards should be fairly easy and resolving a wildcard would be represented by creating new recipes each containing a different external file. These recipes would then be parsed sequentially and independently of each other. Wildcard resolving could be done during preprocessing so I imagine this could be added in later when the preprocessor for machine pools is finished.
This feature would also benefit greatly from the other suggestion to improve summary reports.
lnst-developers@lists.fedorahosted.org