From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge util-linx; util-linux and sysvinit block eachother.
Date: Tue, 10 Jun 2014 21:33:16 +0200 [thread overview]
Message-ID: <53975D7C.60305@gmail.com> (raw)
In-Reply-To: <20140610192945.41a94adb@digimed.co.uk>
On 10/06/2014 20:29, Neil Bothwick wrote:
> On Tue, 10 Jun 2014 19:06:19 +0200, Alan McKinnon wrote:
>
>>> What's not to like? Do you like a long emerge list aborting as soon as
>>> you turn your back because of a missing patch file in a minor package?
>>
>> Yes, exactly. For two reasons:
>>
>> 1. In the vast majority of cases, there's something to deal with and I
>> like to deal with it now. Missing patch files are comparatively rare for
>> me, whereas X doesn't build with the latest version of Y is somewhat
>> common. I'd rather mask the new version of Y and let portage re-figure
>> things out.
>
> Yes, but the packages that continue have nothing to do with the error, so
> it makes sense to get them out the way so only the problem packages are
> left. Also, when there's yet-another-bloody-chromium-update and I set it
> running and go to do something useful, I don't want to come back two
> hours later to find it didn't even try to build chromium because
> sys-unrelated/foo failed.
>
> Also, occasionally, I find that running the update again compiles the
> program correctly this time. This happens quite often with KDE updates
> when kdm and one or two others fail on the first pass, but work next
> time.
>
>> 2. My over-the-top OCDness won't let me leave the bloody thing alone and
>> let it finish, if I know there's an error in there I feel compelled to
>> hit Ctrl-C and find out what the error is :-)
>
> I understand that only too well, but I find it less destructive to look
> at the log for the failed build while the others continue :P
>
>
I understand you completely, and I also understand Alan completely :-)
I'm an old fart, set in my ways, I found something long ago that works
for me with unsufficient pain to provoke a change.
So I ain't changin' :-)
--
Alan McKinnon
alan.mckinnon@gmail.com
next prev parent reply other threads:[~2014-06-10 19:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-09 11:28 [gentoo-user] emerge util-linx; util-linux and sysvinit block eachother Alan Mackenzie
2014-06-09 11:41 ` Neil Bothwick
2014-06-09 19:15 ` Andreas K. Huettel
2014-06-09 21:01 ` Alan McKinnon
2014-06-10 10:36 ` thegeezer
2014-06-10 13:35 ` Alan McKinnon
2014-06-10 14:27 ` Neil Bothwick
2014-06-10 17:06 ` Alan McKinnon
2014-06-10 18:29 ` Neil Bothwick
2014-06-10 19:33 ` Alan McKinnon [this message]
2014-06-10 20:12 ` Neil Bothwick
2014-06-09 21:04 ` Alan Mackenzie
2014-06-09 21:37 ` Andreas K. Huettel
2014-06-09 22:44 ` Neil Bothwick
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=53975D7C.60305@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