| Summary: | Using MPC causes too many repositories to be registered | ||
|---|---|---|---|
| Product: | [Technology] MPC | Reporter: | David Green <greensopinion> |
| Component: | wizard | Assignee: | Project Inbox <mpc.wizard-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | steffen.pingel |
| Version: | unspecified | ||
| Target Milestone: | 1.0.0 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
David Green
MPC should only add repositories for solutions that are being installed right? I think that makes sense because P2's check for update functionality needs repositories to be enabled in order to find updates. Repositories must be added in order to resolve a provisioning operation. This is done in MPC whenever the *Next* button is pressed to get to the feature selection page, since the page must know if the provisioning operation can be performed. In other words, the only time repositories are added is when solutions are selected for install and the user decides to proceed with installation. I really don't see a way around this since proceeding with installation requires that the repositories be added. |