Summary: | xpdf uses "nomotif" USE flag instead of checking against "motif" USE flag | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Kelly Price <bugs> |
Component: | Current packages | Assignee: | Printing Team <printing> |
Status: | RESOLVED INVALID | ||
Severity: | blocker | CC: | qa |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Kelly Price
2005-01-29 08:39:56 UTC
This doesn't exactly help. Does Xpdf *require* a Motif library? The ebuild is a bit confusing with this. I mean, if it does, it should check to see if OpenMotif or Lesstif (which compiled) is availible and stop compiling if neither are found. this is intended, because the xpdf binary won't be built without motif, but we still want to have the option to disable motif Huh? Wait a min, you want to disable motif, yet stop xpdf from building at all if there's no motif. I hate to be stubborn, but I'm also getting confused. Why is xpdf being compiled in the first place when there's no motif there to let it compile? Right now, I've got xpdf on my system for no good reason, and I'm half tempted to grep through all of portage to find out which dependency is causing it to be brought in and yanking it out. |