| 1 |
On 18-11-2012 22:57:49 +0200, Leho Kraav wrote: |
| 2 |
> On a couple of x86_64 Linux boxes, including a Gentoo instance, |
| 3 |
> everything seemed to be going |
| 4 |
> fine until some package bombs out towards the end during "emerge -e |
| 5 |
> system". Restarting the script wants to re-emerge all 92 packages from |
| 6 |
> the start, even though you might have 84 of them already installed. |
| 7 |
> Would it make sense to build binpkgs here btw and make the script do |
| 8 |
> "emerge -ek system" instead? |
| 9 |
> |
| 10 |
> Anyway, what's the sensible action here? I don't want it to start |
| 11 |
> rebuilding a hundred packages when only last 6 might be missing.. |
| 12 |
|
| 13 |
In that stage, I'd just start a login shell from the prefix (e.g. |
| 14 |
/path/to/prefix/bin/bash -l) and run emerge --resume. It may be wise to |
| 15 |
clean your environment, but portage should do that to a certain extent. |
| 16 |
(env -i HOME=$HOME TERM=$TERM USER=$USER /path/to/prefix/bin/bash -l) |
| 17 |
|
| 18 |
After emerge -e it does the startscript thing, but you can do that |
| 19 |
manually too. |
| 20 |
|
| 21 |
-- |
| 22 |
Fabian Groffen |
| 23 |
Gentoo on a different level |
Archives