Summary: | sys-apps/portage: improve emerge's "Change USE" message | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Martin Mokrejš <mmokrejs> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | CC: | esqualante |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Martin Mokrejš
2009-03-10 20:09:38 UTC
(In reply to comment #0) > However, the message "dev-util/subversion[-dso]" is unclear. Probably a space > is missing? No, that's the actual "dependency atom" syntax that ebuilds use internally. The syntax does not allow any spaces inside a dependency atom. > Few more ideas how I would re-structure the text: > > The following packages have to be build with the following USE flag(s): > "dev-util/subversion [-dso]" You've focused on the internal dependency syntax instead of the part that's supposed to be human readable. > (dependency required by "dev-util/git-1.6.2" [ebuild]) > (dependency required by "world" [argument]) > > Reproducible: Always > > Actual Results: > emerge: there are no ebuilds built with USE flags to satisfy > "dev-util/subversion[-dso]". > !!! One of the following packages is required to complete your request: > - dev-util/subversion-1.5.5 (Change USE: -dso) The above line is the "human readable" part that you're supposed to focus on. See, it's advising you to "Change USE: -dso" for subversion-1.5.5. The output is modeled directly after the "masked packages" message, which is basically the same message as this except that it shows masking reasons instead of required changes to USE. - dev-util/subversion-1.5.5 (Change to USE: -dso) ------------------------------------^^^ so about this? The messaging is all well and good, but why does this happen in the first place? Normally when a use dependency is required, portage just forces the use flag on/off. Why isn't that happening here? (clarification) I had to do USE="-dso" emerge subversion in order to fix this. I shouldn't have to do this and normally portage does it for me. Why didn't it happen this time? (In reply to comment #4) > (clarification) I had to do USE="-dso" emerge subversion in order to fix this. > I shouldn't have to do this and normally portage does it for me. Why didn't it > happen this time? The problem is that the subversion ebuild uses an IUSE default setting to enable the dso flag (it has +dso in its IUSE variable). For bug 258371, there are plans to add automatic USE adjustment. (In reply to comment #2) > - dev-util/subversion-1.5.5 (Change to USE: -dso) > ------------------------------------^^^ so about this? I think the existing message is fine. You're the first person that's reported a misunderstanding like this. Maybe we just need to explain the existing output with some examples in the documentation. (In reply to comment #5) > I think the existing message is fine. You're the first person that's reported a > misunderstanding like this. Maybe we just need to explain the existing output > with some examples in the documentation. > Considering the low number of complains about this output, I'd say no action is needed here. Closing as WONTFIX. |