public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: Gentoo <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] question/feature request: First fetch, then compile...
Date: Wed, 17 Dec 2014 06:48:55 +0100	[thread overview]
Message-ID: <20141217054855.GA4439@solfire> (raw)

Hi,

On my embedded systems (beaglebone black, 2 x Arietta G25) I installed
Gentoo (of course!:).
Since these systems and especially the Ariettas are not as fast as a
PC the greater update, which additionally includes C++ sources to
compile takes time (read: hours) to finish. Often I run this over
night.

Since my PC do the forwarding of requests to the internet, it has to
run the whole time also.

To circumvent this I access the embedded systems via abduco/dvtm, so
I can log out while the process keeps running.

The current (shorted decription) workflow is

eix-sync
emerge ... -f (fetching all items, so the connection to the internet is
               no longer needed)
emerge ...    (starting the compilation, logout and shutdown the PC)


This includes "Calculating dependencies" twice of the same set of
data, which also takes a longer time. This is -- technically -- not
needed.

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?

This would save one "Calculating dependencies" and also reduces writes
to the flash memory.

Is it currently possible somehow and if not: I would like to have it
included as new feature into an upcoming release of emerge?!?!

Thanks a lot in advance! 8)
Best regards,
Meino




             reply	other threads:[~2014-12-17  5:49 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  5:48 meino.cramer [this message]
2014-12-17  6:19 ` [gentoo-user] question/feature request: First fetch, then compile 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
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=20141217054855.GA4439@solfire \
    --to=meino.cramer@gmx.de \
    --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