Summary: | emerge --autounmask does not attempt to solve unsatisfied REQUIRED_USE | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Till Schäfer <till2.schaefer> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | enhancement | CC: | jarauh, pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Till Schäfer
2012-03-07 14:57:17 UTC
I had the same problem with libreoffice. There the issue is a bit more subtle, because the use requirement is: The following REQUIRED_USE flag constraints are unsatisfied: kde? ( !gnome ) gnome? ( !kde ) In other words, portage cannot always resolve the issue. It should, however, be able to solve the simple issues, and, more importantly, it should give a meaningful error message. (In reply to comment #1) > It should, however, be able to solve the simple issues, Yes, that would be a nice enhancement. > and, more importantly, it should give a meaningful error message. It attempts to do this by separating the part of the REQUIRED_USE expression that is unsatisfied, and displaying it separately. For example, in comment #0 the REQUIRED_USE message shows that "xvmc? ( g3dvl )" is unsatisfied, which is just a small part of the complete expression. (In reply to comment #2) > > and, more importantly, it should give a meaningful error message. > > It attempts to do this by separating the part of the REQUIRED_USE expression > that is unsatisfied, and displaying it separately. For example, in comment > #0 the REQUIRED_USE message shows that "xvmc? ( g3dvl )" is unsatisfied, > which is just a small part of the complete expression. Yes, I agree that that's a useful feature. What I meant, however, was that the first error message, before unmasking the ebuild manually, should explain the problem properly. The first error message just tells the user that a keyword is missing. This is confusing if the --autounmask --autounmask-write options are used, since in this case a missing keyword should be be added automatically. (In reply to comment #3) > The first error message just tells the user that a keyword is missing. That's just a symptom of the fact that --autounmask currently makes no attempt to satisfy REQUIRED_USE. After we have enhanced it to satisfy REQUIRED_USE, it will satisfy it together with the keyword mask in a single step. This looks similar to bug 403207 *** This bug has been marked as a duplicate of bug 403207 *** |