From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gentoo-user+bounces-181008-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by finch.gentoo.org (Postfix) with ESMTPS id 0D0E7139083
	for <garchives@archives.gentoo.org>; Sun,  3 Dec 2017 12:56:10 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
	by pigeon.gentoo.org (Postfix) with SMTP id 278D7E0ECC;
	Sun,  3 Dec 2017 12:56:03 +0000 (UTC)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pigeon.gentoo.org (Postfix) with ESMTPS id 98985E090A
	for <gentoo-user@lists.gentoo.org>; Sun,  3 Dec 2017 12:56:02 +0000 (UTC)
Received: by mail-yw0-x229.google.com with SMTP id n25so5717253ywh.10
        for <gentoo-user@lists.gentoo.org>; Sun, 03 Dec 2017 04:56:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20161025;
        h=subject:to:references:from:message-id:date:user-agent:mime-version
         :in-reply-to:content-transfer-encoding;
        bh=tKhWNNCg+KKwdxtrBv35GiX7UgOR+upnlEEIKrL9Ims=;
        b=FDKUWTiitJNPBedf0Lt7WlXtRLHaMyJ08EPTKd1jc+Ix2E+KxjbOpQgfxBrY217dID
         aPpi12rlF4ROc0SJqnVE7pTTATxQhDv0MFknATPoD72+/O++xFXu8UGgjqGDZD/ZqdoJ
         yL8MwQzEyZpqGoWvpJBfd/ZSq9YeZj6NibH3P+hsMb6W5oCi+jsfj10vfklnzONOsQGN
         Pwnt9YRCTJ9waJB47kuDYIdur+3uxZY2qGl7osM8hp32Avcs6qeduoB80mlF/g0m0HNC
         Ro0+JIOaaTgvZQs/o+pQyDgxdo1fF21bb1R/DcO+2vaHXeWREkt2zOJGW0AjIZPuUK1l
         74vQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:subject:to:references:from:message-id:date
         :user-agent:mime-version:in-reply-to:content-transfer-encoding;
        bh=tKhWNNCg+KKwdxtrBv35GiX7UgOR+upnlEEIKrL9Ims=;
        b=XFUH/TsT1LIqCNK1jAe9Mn1ITsE4hSkwS2WAp9sPIBLQ9xQV2KMZlDrW+ubZHxzZtS
         8rHmKIRivXOXj5Awhp/uniyDWZxBDSsj60vpEly1k/MXxoP3SAu2k0Ff/curTyjUKavn
         rn0kuuxtZGgsHVju7M0BLhEPABllBPQJQf7yv11HkZG2CmViN20QxEQ+i81rBYiQX4cm
         ngeggHJNhHV7THd4NgODe1NIQGqiFQvJvhmq83fITy4czFK6eR2UK8oB7sWO8l0eHWW3
         0/Pm8vnPy6omE1/RFiNYEggL68sFkqxbDrEx1nAppsOHytQkG1dTlWNRLZSHVOSHW4GF
         GSfg==
X-Gm-Message-State: AJaThX684VKHQ0t1yf2iUMO69/RbzjOoFPW35E9XnSW6Fzda5HRd5Ig6
	VFK5+QdnvMf02cHaJxnM6Wg=
X-Google-Smtp-Source: AGs4zMZq7TJJtc2KxvNSthDP3YkdNuLNWgzgcdyQI5sFkZG6SNPDSunbzwVEyWm6HLawCfW61rSFbg==
X-Received: by 10.129.43.137 with SMTP id r131mr7474990ywr.370.1512305761647;
        Sun, 03 Dec 2017 04:56:01 -0800 (PST)
Received: from [192.168.2.5] (adsl-65-0-93-225.jan.bellsouth.net. [65.0.93.225])
        by smtp.gmail.com with ESMTPSA id u194sm5212270ywe.71.2017.12.03.04.55.59
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Sun, 03 Dec 2017 04:56:00 -0800 (PST)
Subject: Re: [gentoo-user] New profile 17: How urgent is the rebuild of world
 technically?
To: gentoo-user@lists.gentoo.org
References: <20171203021528.xmulbskbadhglyda@solfire>
 <20171203034559.qlwbla6hvkjnpn32@solfire> <20171203051525.4c91fafd@lexx>
 <4413682.jgHyVfB3Vf@peak> <20171203125605.797c0b51@lexx>
From: Dale <rdalek1967@gmail.com>
Message-ID: <1b29fc64-a0fb-1b96-2d50-e75130fbf996@gmail.com>
Date: Sun, 3 Dec 2017 06:55:59 -0600
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Firefox/52.0 SeaMonkey/2.49.4.0
Precedence: bulk
List-Post: <mailto:gentoo-user@lists.gentoo.org>
List-Help: <mailto:gentoo-user+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-user+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-user+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-user.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
Reply-to: gentoo-user@lists.gentoo.org
MIME-Version: 1.0
In-Reply-To: <20171203125605.797c0b51@lexx>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Archives-Salt: 91666cac-a649-4267-a3ef-c389907250bb
X-Archives-Hash: 8aaf17322b28633190beaa042df49484

Heiko Baums wrote:
> Am Sun, 03 Dec 2017 09:53:21 +0000
> schrieb Peter Humphrey <peter@prh.myzen.co.uk>:
>
>> On Sunday, 3 December 2017 04:15:25 GMT Heiko Baums wrote:
>>
>>> Like I said before. emerge always calculates the dependency tree,
>>> which is a lot faster in case of `emerge -e @world` than in case of
>>> `emerge -uDN @world`. And then it knows which packages have already
>>> been installed and which are not.
>>>
>>> That said I haven't run an `emerge -e @world` before. So I'm
>>> actually not sure if this works the same way as with an `emerge
>>> -uDN @world`.  
>> Nope. Empty-tree means empty-tree. That is, whenever you emerge -e
>> world, you start from the beginning every time, regardless of
>> anything you were doing just before that.
> Actually I was talking about the behavior of `emerge --resume` in the
> case of `emerge -e @world` compared to `emerge -uDN @world`. Sorry, if
> this was unclear.
>
> Heiko
>
>

I think I get what you are saying.  If for example you start a emerge -e
world, a emerge -uDN world or something and then stop it before it
finishes, running emerge --resume should pick up where you left off.  In
the past, I have done that after a reboot. I'm not sure if having some
things on tmpfs has a effect on that tho. 

That said, if you start one of those commands, emerge -e world for
example, and then do some other command besides --resume, then most
likely that will clear whatever emerge was doing before which means
--resume won't work because it has been reset/cleared with the second
command. 

As a workaround, I have been known to go to another terminal/konsole and
do a emerge --resume -a and let it get to the point where I need to hit
"y" and enter.  I let it sit there and go back to the original terminal
and emerge with whatever options I need for whatever package needs
attention.  Then when I'm done, I go to the other terminal/konsole and
tell emerge yes to the --resume command.  Once that command figures out
what it needs to do, it already has its list to work with.  However, I
can emerge something in another terminal to fix things and hopefully
carry on with the --resume. 

Sometimes doing that doesn't work but it could be worth a try.  It's
been a while since I've had the need to do that too.  Generally, if a
package fails, it will fail until something is fixed so that in can
complete the process.  As I've said before, emerge and how it does
things has come a long ways in recent years. 

I hope I understood what you meant with all this.  I disturbed quite a
few electrons and stuff with this.  lol

Dale

:-)  :-)