Depending on a Component that itself has AutoDependsOn leads to inconsistent state

Depending on a component with AutoDependOn will first install this component, then (in the next run) uninstall it.

What happened

• Component A AutoDependOn B, B is not installed
• Component C added a dependency to A in an Update. A got installed, but not B.
• The next time the PackageManager runs (e.g. to install/deinstall an unrelated component), IFW detects that the dependency from A to B is not satisfied (because B is not installed), automatically uninstalls C, A.

This is of course unfortunate ... What we could do is

• Forbid to depend on a component that has AutoDependOn

This is probably hard to enforce in the current codebase ... but we could do such a sanity checking once we have a unified dependency model.

• Enforce installation of B

That would probably not fit the exact use case where it happened (A was actually Virtual), but would be consistent to.

• Only remove A if there are no dependencies to it

Would require one local change.