| Summary: | app-emulation/open-vm-tools: Incorrect meaning of 'xinerama' flag causes build failure | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | John Brooks <special> |
| Component: | Current packages | Assignee: | Gentoo VMWare Bug Squashers [disabled] <vmware+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
John Brooks
2008-11-18 11:24:22 UTC
Thanks, I'm not sure that's the best solution, since people who set -xinerama +unity might wonder why xinerama's needed. I'll probably add a check to ensure that unity is never on when xinerama is off, and give a warning message otherwise... I'm not sure a warning is quite right either - with unity enabled and xinerama unavailable, the build *will* fail to compile, or use xinerama anyway if those files happen to be available. I agree that it could be confusing to have xinerama pulled in with the xinerama flag unset, though. I think either solution would probably be acceptable, if there aren't any other applicable options. Ok, the ebuild now dies with an error if USE="unity -xinerama". Without the error, the latest upstream would simply turn off unity support (they fixed it, so it won't fail to compile anymore). Either way, it would confuse a fair number of people, so I went with the error... |