| 1 |
On Thu, 6 Dec 2012 08:45:10 +0100 |
| 2 |
Willie WY Wong <wongwwy@××××××××××.org> wrote: |
| 3 |
|
| 4 |
> Hi list, |
| 5 |
> |
| 6 |
> Suppose that I tried to emerge a package, and the compilation phase |
| 7 |
> went through without problems, but it got stopped in the installation |
| 8 |
> phase. Is there a way to (after I fixed the problem) to tell portage |
| 9 |
> to install the (now all already compiled binaries sitting in |
| 10 |
> /var/tmp/portage) directly without having to redo the compiling |
| 11 |
> phase? |
| 12 |
|
| 13 |
not with emerge, but you can use the lower-level command ebuild for |
| 14 |
that. |
| 15 |
|
| 16 |
portage & ebuild are analogous to yum & rpm or to apt* and dpkg |
| 17 |
|
| 18 |
man ebuild for more info |
| 19 |
|
| 20 |
> |
| 21 |
> Case in point: |
| 22 |
> |
| 23 |
> I just tried to update dev-lib/boost to 1.52. The compilation went |
| 24 |
> without a hitch, but the installation died because of file collision |
| 25 |
> against (I think) boost-1.49.0-r1000. Now that the colliding files are |
| 26 |
> no longer there, is there a way to tell portage to go ahead an install |
| 27 |
> boost-1.52 from the compiled sources in /var/tmp/portage ? |
| 28 |
> |
| 29 |
> Thanks, |
| 30 |
> |
| 31 |
> W |
| 32 |
|
| 33 |
|
| 34 |
|
| 35 |
-- |
| 36 |
Alan McKinnon |
| 37 |
alan.mckinnon@×××××.com |
Archives