emerge -kp eclipse-sdk returns different dependencies than emerge -p eclipse-sdk Reproducible: Always Steps to Reproduce: 1. I tried emerge -p eclipse-sdk to see what deps were listed 2. Then I tried emerge -k eclipse-sdk to do the actual merge Actual Results: I noticed it was fetching mozilla, which wasn't listed in the emerge -p. So I killed it and emerge -kp'd eclipse-sdk. It had only two packages listed, mozilla and eclipse-sdk itself. Expected Results: I would have thought that -k wouldn't affect the list of dependencies.
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
