Summary: | emerge -kp returns different deps than emerge -p | ||
---|---|---|---|
Product: | Portage Development | Reporter: | michael <michael> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
michael@smith-li.com
2004-11-04 20:22:53 UTC
was the binary package built with different USE flags ? Can't say much without more information, especially the exact output of -p and -kp, emerge --info would be nice too. I had a conversation with carpaski on #gentoo that resolved my question about whether this is a bug or not. I think it's not a bug, and that the different dependencies just reflected the different states of the systems on which the package was compiled and merged, respectively. ...conversation follows... kojiro: carpaski, bit` suggested that you might be the one to whom to ask this question: should 'emerge -kp <package>' return different dependencies than 'emerge -p <package>' ? <snip> carpaski: kojiro: It could. Use flags, rdepends and depends will differ. <snip> carpaski: kojiro: binaries do not use depends. carpaski: kojiro: and their useflags are propogated. <snip> carpaski: Only R and P deoends apply. <snip> kojiro: carpaski, so if I build a package one one system, the USE flags there will carry over to the system in which I merge it? carpaski: yep |