On Thu, 6 Dec 2012 08:45:10 +0100 Willie WY Wong <wong...@member.ams.org> wrote:
> Hi list, > > Suppose that I tried to emerge a package, and the compilation phase > went through without problems, but it got stopped in the installation > phase. Is there a way to (after I fixed the problem) to tell portage > to install the (now all already compiled binaries sitting in > /var/tmp/portage) directly without having to redo the compiling > phase? not with emerge, but you can use the lower-level command ebuild for that. portage & ebuild are analogous to yum & rpm or to apt* and dpkg man ebuild for more info > > Case in point: > > I just tried to update dev-lib/boost to 1.52. The compilation went > without a hitch, but the installation died because of file collision > against (I think) boost-1.49.0-r1000. Now that the colliding files are > no longer there, is there a way to tell portage to go ahead an install > boost-1.52 from the compiled sources in /var/tmp/portage ? > > Thanks, > > W -- Alan McKinnon alan.mckin...@gmail.com
