From: "Håkon Alstadheim" <hakon@alstadheim.priv.no>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: [OT] How to be a penguin.
Date: Sun, 29 May 2016 10:28:47 +0200 [thread overview]
Message-ID: <574AA83F.1000502@alstadheim.priv.no> (raw)
In-Reply-To: <CAJoOjx96qyKiuizQU-zS8LJLfGxTBCerruF8AeaN=Y0gPq2yjA@mail.gmail.com>
Den 29. mai 2016 03:17, skrev Gregory Woodbury:
>
> WOW!
>
> Alan just wants to start it and walk away, as if Gentoo was a binary
> distribution
> that handles it all upstream. He doesn't want to take the time to
> review what
> emerge is proposing and see if changes are needed first.
>
It IS actually possible to do that, at least for non-critical systems.
Just make sure to mail yourself with the emerge output, so you can fix
things before the next automatic run.
The point being that you don't have to sit and watch while emerge works.
You can have the output of any blocks or failures waiting for you in
your inbox at your convenience.
For this to work in a timely fashion you need to stay on stable packages
as much as possible, and also keep other customizations to a minimum,
e.g. don't use --autounmask-write.
next prev parent reply other threads:[~2016-05-29 8:28 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-28 16:05 [gentoo-user] How to be a penguin Alan Grimes
2016-05-28 16:19 ` [gentoo-user] Re: [OT] " »Q«
2016-05-28 17:06 ` Dale
2016-05-28 18:05 ` Gregory Woodbury
2016-05-28 18:18 ` Neil Bothwick
2016-05-28 18:22 ` Alec Ten Harmsel
2016-05-28 18:33 ` Dale
2016-05-28 18:49 ` Dale
2016-05-28 19:54 ` Volker Armin Hemmann
2016-05-28 20:10 ` Dale
2016-05-29 18:03 ` »Q«
2016-05-28 20:53 ` Neil Bothwick
2016-05-29 1:17 ` Gregory Woodbury
2016-05-29 3:48 ` Daniel Frey
2016-05-29 8:58 ` Neil Bothwick
2016-05-29 9:20 ` Dale
2016-05-29 16:25 ` Daniel Frey
2016-05-29 19:33 ` Dale
2016-05-29 12:18 ` Alan Grimes
2016-05-29 8:28 ` Håkon Alstadheim [this message]
2016-05-29 9:28 ` Dale
2016-05-29 10:26 ` Alan McKinnon
2016-05-29 10:56 ` Neil Bothwick
2016-05-29 17:54 ` Dale
2016-05-29 20:15 ` Alan McKinnon
2016-05-29 21:27 ` Volker Armin Hemmann
2016-05-31 2:14 ` Dale
2016-05-29 12:13 ` Alan Grimes
2016-05-29 17:50 ` »Q«
2016-05-29 19:40 ` Dale
2016-05-29 17:51 ` Dale
2016-05-31 0:32 ` Alan Grimes
2016-05-31 1:00 ` Volker Armin Hemmann
2016-05-31 2:01 ` Dale
2016-05-31 6:02 ` Alan McKinnon
2016-05-31 7:54 ` Neil Bothwick
2016-05-29 21:13 ` Neil Bothwick
2016-05-31 0:48 ` Alan Grimes
2016-05-31 5:31 ` J. Roeleveld
2016-05-31 7:50 ` Neil Bothwick
2016-05-29 23:58 ` Gregory Woodbury
2016-05-30 6:25 ` R0b0t1
2016-05-31 0:57 ` Alan Grimes
2016-05-31 5:34 ` J. Roeleveld
2016-05-31 13:32 ` Alan Grimes
2016-05-31 14:21 ` James
2016-05-31 18:30 ` R0b0t1
2016-05-31 18:44 ` Alan Grimes
2016-05-30 8:30 ` Peter Humphrey
2016-05-28 20:11 ` ng0
2016-05-28 18:20 ` Neil Bothwick
2016-05-28 18:38 ` Dale
2016-05-29 8:45 ` Peter Humphrey
2016-05-29 8:58 ` Peter Humphrey
2016-05-29 17:25 ` [gentoo-user] " Grant Edwards
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=574AA83F.1000502@alstadheim.priv.no \
--to=hakon@alstadheim.priv.no \
--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