Description of problem: In wallaby store there should be no feature which includes the same feature as it depends on. Wallaby should discourage any action which could lead to such situation. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We've made the decision that feature dependencies can be satisfied by immediate or transitive inclusion. Since it is possible that features in the field rely on this behavior, we'd need a very good reason to break the old functionality. Is there such a reason?
OK, agreed, wallaby doesn't necessary have to forbid such action, but at least it could print some warning if it happens.
This is a job for the "wallaby lint" tool that we've talked about in the past; I'm marking this bug as such.