From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Confessional: how I generally use emerge.
Date: Fri, 18 Mar 2016 23:07:10 +0000 [thread overview]
Message-ID: <20160318230710.674753d8@digimed.co.uk> (raw)
In-Reply-To: <56EC3DD3.6070108@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 828 bytes --]
On Fri, 18 Mar 2016 12:41:39 -0500, Dale wrote:
> I have to add this. From what I understand about the scripts he is
> using, he is blindly letting emerge do updates without checking to see
> if the updates fall into line with what he *needs*. If I read it
> correctly, any USE flag change will be missed until it hits the fan and
> is broken. That would then mean taking a lot of time to go back through
> logs and figuring out just when it went wrong and most importantly, what
> caused it and how to fix it. Since the change could have happened
> several updates ago, that could involve some work and a lot of
> rebuilding.
And deleting the emerge logs as part of that script doesn't make things
any easier. Still, some people like a challenge ;-)
--
Neil Bothwick
Be regular. Eat cron flakes.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-03-18 23:07 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-17 14:55 [gentoo-user] The war continues Alan Grimes
2016-03-17 15:12 ` William Ernesto Cárdenas Gómez
2016-03-17 16:20 ` Max R.D. Parmer
2016-03-18 0:18 ` [gentoo-user] Confessional: how I generally use emerge Alan Grimes
2016-03-18 0:37 ` Alec Ten Harmsel
2016-03-18 1:08 ` Alan Grimes
2016-03-18 1:12 ` Neil Bothwick
2016-03-18 17:41 ` Dale
2016-03-18 23:07 ` Neil Bothwick [this message]
2016-03-19 3:31 ` Alan Grimes
2016-03-19 9:40 ` Neil Bothwick
2016-03-19 14:58 ` Francisco Ares
2016-03-18 18:43 ` [gentoo-user] " »Q«
2016-03-18 21:55 ` Alan McKinnon
2016-03-19 16:43 ` »Q«
2016-03-19 17:03 ` Alan McKinnon
2016-03-19 18:25 ` »Q«
2016-03-20 1:55 ` Dale
2016-03-18 22:00 ` Alec Ten Harmsel
2016-03-20 22:22 ` Jonathan Callen
2016-03-17 15:20 ` [gentoo-user] Re: The war continues Grant Edwards
2016-03-17 16:00 ` [gentoo-user] " Philip Webb
2016-03-18 8:10 ` [gentoo-user] " Nikos Chantziaras
2016-03-18 12:23 ` Philip Webb
2016-03-18 16:29 ` Alan Grimes
2016-03-18 16:43 ` wabenbau
2016-03-18 17:47 ` Dale
2016-03-18 18:29 ` wabenbau
2016-03-18 18:47 ` Mick
2016-03-18 20:37 ` wabenbau
2016-03-18 21:57 ` Alan McKinnon
2016-03-19 3:08 ` wabenbau
2016-03-19 6:37 ` Alan McKinnon
2016-03-19 9:33 ` Neil Bothwick
2016-03-20 16:32 ` wabenbau
2016-03-20 0:37 ` Nikos Chantziaras
2016-03-20 17:01 ` wabenbau
2016-03-18 18:49 ` Dale
2016-03-18 20:36 ` wabenbau
2016-03-18 23:04 ` Neil Bothwick
2016-03-19 2:51 ` Dale
2016-03-19 9:35 ` Neil Bothwick
2016-03-19 9:52 ` Dale
2016-03-19 14:56 ` »Q«
2016-03-19 15:24 ` Daniel Frey
2016-03-19 16:44 ` Dale
2016-03-19 16:50 ` Neil Bothwick
2016-03-18 19:38 ` Philip Webb
2016-03-18 20:34 ` wabenbau
2016-03-18 23:35 ` Philip Webb
2016-03-19 3:34 ` wabenbau
2016-03-17 18:18 ` [gentoo-user] " Neil Bothwick
2016-03-18 0:26 ` Alan Grimes
2016-03-18 0:37 ` Neil Bothwick
2016-03-17 19:23 ` [gentoo-user] Simply approach:: " James
2016-03-19 3:21 ` [gentoo-user] " Fast Turtle
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=20160318230710.674753d8@digimed.co.uk \
--to=neil@digimed.co.uk \
--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