Summary: | emerge --buildpgkonly --usepkg strangeness | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | b52 <tm-8rjpk> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | adsmith |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
b52
2005-04-20 07:32:29 UTC
You want to compile binaries from binaries? How is this supposed to work? Why don You want to compile binaries from binaries? How is this supposed to work? Why donĀ“t you copy the packages there? *** Bug 89860 has been marked as a duplicate of this bug. *** No yo you didn't understand my point. For example when i want to compile a binary of kde-base then emerge has to compile all packages kde-base depends on. Now emerge should not download and compile packages (which are needed to compile kde-base) it already has as precompiled binaries in the PKGDIR. It has to use the binaries which are already there to solve the depencies of the new binary kde-base. --buildpkgonly with --usepkg doesn't make sense. --buildpkgonly means don't *install* anything whether from source or binary. Hence, it doesn't matter if deps are available in binary packages or not. The bug here is that emerge decides to install all the dependencies (even from ebuilds) when it shouldn't. # emerge --buildpkgonly --usepkg gnome Calculating dependencies ...done! !!! --buildpkgonly requires all dependencies to be merged. !!! Cannot merge requested packages. Merge deps and try again. It works as it should. It is *not possible* to create binaries if the dependencies are not *installed* already. At least, it won't be possible without modifying almost every ebuild. The packages being built need to be able to find their deps' libs which won't happen unless the deps are installed. *** Bug 100114 has been marked as a duplicate of this bug. *** I'll repeat what I said in the duplicate bug report above: An issue that hasn't been addressed here is that this behavior (which I also consider to be a bug) breaks "-B" completely if FEATURES="getbinpkg" is enabled. Since FEATURES="getbinpkg" implies always using "-k", it is impossible to use "-B" in the intended way. That is, there is no way to build binary packages without emerging onto the system. Furthermore, at the very least, a note should be put in the emerge and make.conf manpages regarding this behavior. People keep running into it when making automated emerge scripts, and the man page gives no indication of this conflict. Perhaps --buildpkgonly should disable --usepkg? I think that "-B disables -k" would be an acceptable solution. Just one note: Since -g activates -k and -B would deactivate -k, whoever makes this change has to be sure wierd conflicts don't happen if someone calls -Bg. In particular, -B should probably disable -g and FEATURES="getbipkg" as well. Actually, this is also good to do logically since it doesn't make sense to grab new packages from a server if I really want to build them myself. |