Bug 747308
Summary: | [RFE] wallaby lint: warn when including and depending on the same feature | ||
---|---|---|---|
Product: | Red Hat Enterprise MRG | Reporter: | Lubos Trilety <ltrilety> |
Component: | wallaby | Assignee: | grid-maint-list <grid-maint-list> |
Status: | CLOSED WONTFIX | QA Contact: | MRG Quality Engineering <mrgqe-bugs> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | Development | CC: | matt |
Target Milestone: | --- | Keywords: | FutureFeature |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-05-26 20:10:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Lubos Trilety
2011-10-19 13:09:37 UTC
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. |