From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] question/feature request: First fetch, then compile...
Date: Wed, 17 Dec 2014 10:22:20 +0200 [thread overview]
Message-ID: <54913D3C.9040808@gmail.com> (raw)
In-Reply-To: <1418802326.30942.0@numa-be>
On 17/12/2014 09:45, Helmut Jarausch wrote:
> On 12/17/2014 06:48:55 AM, meino.cramer@gmx.de wrote:
> ....
>> Is it possible, to do ONE call to emerge, which asks (according
>> to option -a, if set ) and given a yes first fetches ALL necessary
>> files and data and compiles then everything?
>>
>
> With some manual operations:
>
> Capture the output of emerge -vp ....
> Edit it to call
> ebuild <full patch to <package>.ebuild> fetch
> for each package.
>
> Then issue emerge without -p
Way too complicated.
emerge -pvuND world
check list, ensure everything is OK, etc etc. Then
emerge -vunDf world
emerge -vuND world
-f only fetches, it does not compile. When it completes, switch the pc
off. The last emerge compiles and everything has been fetched (well
usually is has been fetched).
What the OP is trying to do is not really possible. Portage is designed
with an assumption in mind: the host is always connected to the internet
and can fetch whatever it needs to fetch whenever it needs to fetch it
based on what is in the ebuilds. 100% off-line operation is not part of
the spec, so the OP is always going to have to deal with occasional
emerge failures due to the host being offline
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2014-12-17 8:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 5:48 [gentoo-user] question/feature request: First fetch, then compile meino.cramer
2014-12-17 6:19 ` Dale
2014-12-17 6:27 ` meino.cramer
2014-12-17 6:34 ` Randolph Maaßen
2014-12-17 6:36 ` Dale
2014-12-17 6:41 ` Dale
2014-12-17 6:53 ` meino.cramer
2014-12-17 9:36 ` Neil Bothwick
2014-12-17 9:52 ` meino.cramer
2014-12-17 10:02 ` Dale
2014-12-17 12:13 ` Neil Bothwick
2014-12-17 13:58 ` Matti Nykyri
2014-12-17 14:31 ` meino.cramer
2014-12-17 15:25 ` Poison BL.
2014-12-17 7:45 ` Helmut Jarausch
2014-12-17 8:22 ` Alan McKinnon [this message]
2014-12-17 8:41 ` meino.cramer
2014-12-17 8:42 ` Alan McKinnon
2014-12-17 18:24 ` Frank Steinmetzger
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=54913D3C.9040808@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@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