public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jeffrey Smelser" <jsmelser@travelnow.com>
To: <gentoo-portage-dev@gentoo.org>
Subject: RE: [gentoo-portage-dev] emerge interruption - is it/will it bepossible?
Date: Thu, 4 Dec 2003 10:05:57 -0600	[thread overview]
Message-ID: <121DA8C73F98EE409B20AC0065CB93020E7F76@mantaray.tnow.net> (raw)

> On Thu, 2003-12-04 at 07:21, Pavel Vondricka wrote:
> > Hi,
> > I often would like to continue with a partly done emerge 
> (e.g. manually 
> > interrupted compilation or compile failure -because of some 
> stupid USE flag 
> > setting, aso.), without emerge starting from the scratch again. 
> > It is not only "a bad dream at the end of a 12-hour 
> compilation", but I'd also 
> > like to just unpack the sources, stop emerge, edit/patch 
> the sources 
> > manually, and then let emerge continue and compile and 
> install it, sometimes.
> 
> > Is it possible with the current emerge or will it be 
> possible with the future 
> > portage-ng?
> 
> One easy way to get functionality like this is to "emerge 
> ccache". Then
> restarting merges should used previously-cached compiles and 
> make things
> go a lot faster.
> 
> > What is the meaning of emerge -resume? It never did anything for me.

I use it a lot for emerge -e world. If it fails for some reason, do a emerge -e --resume world, will pick up where it left off. 

However, it does restart that package itself.. But at least I don't have to recompile the last 50-70 packages I just did.

--
gentoo-portage-dev@gentoo.org mailing list


                 reply	other threads:[~2003-12-04 16:05 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=121DA8C73F98EE409B20AC0065CB93020E7F76@mantaray.tnow.net \
    --to=jsmelser@travelnow.com \
    --cc=gentoo-portage-dev@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox