Dependency Resolution within content views + associated UI constructs.
Description of problem:
When creating a content view filter, a user can add/remove arbitrary packages/errata to a content view. However, dependency resolution is not completed on the resultant repos. As such, the end user can easily create a non-working CV.
That is, if the user creates a content view filter that includes errata 'foo',
and the packages in that errata require 'bar' and 'baz' as dependencies, 'bar' & 'baz' should end up in the resultant content view.
This RFE requests enabling dependency resolution by default on content views, while giving the user the option via the UI to disable.
Version-Release number of selected component (if applicable):