Re: [gentoo-user] continue an installation
Willie WY Wong writes: 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? 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 ? FEATURES=keepwork emerge -1ua boost If you also want to avoid collisions: FEATURES=keepwork -collision-protect -protect-owned emerge -1ua boost Wonko
Re: [gentoo-user] continue an installation
On Thu, Dec 06, 2012 at 05:18:24PM -0600, Penguin Lover Kevin Brandstatter squawked: coorect, you could concievable run something like ebuild ebuildname qmerge if all the steps have been completed I will give something like this a try next time. W
Re: [gentoo-user] continue an installation
coorect, you could concievable run something like ebuild ebuildname qmerge if all the steps have been completed -Kevin On Thu, Dec 6, 2012 at 1:44 AM, Alan McKinnon alan.mckin...@gmail.comwrote: 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
[gentoo-user] continue an installation
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? 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 -- Data aequatione quotcunque fluentes quantitae involvente fluxiones invenire et vice versa ~~~ I. Newton
Re: [gentoo-user] continue an installation
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
