public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Kevin F. Quinn" <kevquinn@gentoo.org>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Interrupting portage gracefully
Date: Fri, 24 Nov 2006 09:30:21 +0100	[thread overview]
Message-ID: <20061124093021.5f8a2572@c1358217.kevquinn.com> (raw)
In-Reply-To: <7c08b4dd0611231654i14942091q77604ade34023afe@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]

On Thu, 23 Nov 2006 16:54:53 -0800
"Peter Davoust" <worldgnat@gmail.com> wrote:

> I don't know if this helps, but I usually run emerge <package> && init
> 0 so it shuts off after it's finished (it would be nice if portage had
> an --shutdownafter option, but oh well). The only problem is that if
> there's an error in portage it won't shut down.

That's because by using '&&', you are explicitly telling bash to run
the second command only if the first command succeeds.  To run the
second command regardless, use ';' to separate the commands:

emerge <package> ; init 0

It's a good idea to have logging switched on so if stuff failed you can
find out why later.  In make.conf set PORT_LOGDIR to a directory that
exists; also setup the elog stuff, PORTAGE_ELOG_* -
see /etc/make.conf.example (which is the only place they're documented)
- I use:

PORTAGE_ELOG_CLASSES="info warn error log"
PORTAGE_ELOG_SYSTEM="save"

which just dumps the relevant bits into a subdirectory "elog" of
${PORT_LOGDIR}.

-- 
Kevin F. Quinn

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2006-11-24  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-23 18:21 [gentoo-amd64] Interrupting portage gracefully Peter Humphrey
2006-11-23 19:42 ` [gentoo-amd64] " Duncan
2006-11-23 21:15 ` [gentoo-amd64] " Christoph Mende
2006-11-24  0:11   ` Thomas Rösner
2006-11-24  0:54     ` Peter Davoust
2006-11-24  2:31       ` Michael Weyershäuser
2006-11-24  8:30       ` Kevin F. Quinn [this message]
2006-11-24  9:51         ` Rob Lesslie

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=20061124093021.5f8a2572@c1358217.kevquinn.com \
    --to=kevquinn@gentoo.org \
    --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