| Summary: | Removing packages from a build | ||
|---|---|---|---|
| Product: | [Documentation] Development Manual | Reporter: | Mark Morton <mark.morton> |
| Component: | development | Assignee: | Mark Hatle <mark.hatle> |
| Status: | VERIFIED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | High | CC: | alexandru.c.georgescu, jessica.zhang, richard.purdie, sgw |
| Version: | unspecified | ||
| Target Milestone: | 1.5 | ||
| Hardware: | All | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
|
Description
Mark Morton
2013-04-03 20:39:39 UTC
Mark, can you please work with Mark H. to flesh this item out a little further, provide scenario / examples Example: User chooses core-image-minimal on x86_64. Decides they don't want "vte" support. So they should be able to say "remove vte from the list". The vte package will not be installed, nor will any of the dependencies it would have brought it. If removing the vte package causes the rest of the system to be incapable of being installed, the user can either 'force' the system or an error will occur indicating what item(s) require vte. The user can then decide to remove those, or look for an alternative approach (or force it anyway). If the "thing" that required vte was a packagegroup, it would be useful for a way to expand the package group, so the user could choose to 'remove' the packagegroup, and add everything, except 'vte' to the install. This may be a duplicate of 4079. mark as dup *** This bug has been marked as a duplicate of bug 4079 *** Verified as per above comments! |