As for how to implement this in Ivy, how about: - Provide an inclusion facility for ivy files to semantically include/merge the contents of some other ivy file, similar as "include" for the settings files. Possibly add an attribute to choose what to do in case of conflicting/non-mergeable specs. IMO *any* configuration/specification file format ought to have such a mechanism.
- Add the possibility to specify any kind of ivy file tags under the "module" tag of a settings file, to be semantically injected into the ivy files of all matched modules. Basically a "reverse-include". As above, possibly add an attribute to choose what to do in case of conflicting/non-mergeable specs. Something along these lines would be more generic/orthogonal/flexible than adding a dedicated construct for the specific use case here. -- Niklas Matthies
