From: Beso <givemesugarr@gmail.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] emerge --resume question
Date: Wed, 13 Aug 2008 20:56:21 +0000 [thread overview]
Message-ID: <d257c3560808131356w145f08dfjd0908940c8086e33@mail.gmail.com> (raw)
In-Reply-To: <48A33D3B.9090000@ercbroadband.org>
[-- Attachment #1: Type: text/plain, Size: 975 bytes --]
2008/8/13 Mark Haney <mhaney@ercbroadband.org>
> Typically when I do a massive upgrade (like to KDE) I fetch the files down,
> then do the emerge later when I don't need internet access necessarily.
> However, this time I started the upgrade to KDe4.1 without doing that.
>
> What I want to know is, is it possible for me to do an emerge -f --resume
> to fetch the packages I need /before/ resuming the emerge, say later
> tonight?
>
try doing the emerge of one package in one terminal, then in the other do
the same emerge with fetchonly option after the first one has started
compilation. this will fetch the packages while the other is still building.
the resume also, works only once for what i know. that's why the paludis
hooks that always prints out the packages to install (before actually
installing them and after each time you stop the compile) and the one
installed is a better way to handle the stop and restart of compilation
processes.
--
dott. ing. beso
[-- Attachment #2: Type: text/html, Size: 1306 bytes --]
next prev parent reply other threads:[~2008-08-13 20:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 19:59 [gentoo-amd64] emerge --resume question Mark Haney
2008-08-13 20:56 ` Beso [this message]
2008-08-13 21:04 ` Volker Armin Hemmann
2008-08-14 0:11 ` Juan Fco. Giordana
2008-08-14 3:51 ` Volker Armin Hemmann
2008-08-13 21:19 ` [gentoo-amd64] " Duncan
2008-08-13 21:38 ` andrew
2008-08-14 8:08 ` Duncan
2008-08-14 11:20 ` Mark Haney
2008-08-14 13:23 ` Mark Haney
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=d257c3560808131356w145f08dfjd0908940c8086e33@mail.gmail.com \
--to=givemesugarr@gmail.com \
--cc=gentoo-amd64@lists.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