From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 2E4FC13888F for ; Wed, 21 Oct 2015 05:11:33 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F2DDD21C02D; Wed, 21 Oct 2015 05:11:29 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 6797821C02C for ; Wed, 21 Oct 2015 05:11:29 +0000 (UTC) Received: from [192.168.0.13] (ip174-67-205-96.oc.oc.cox.net [174.67.205.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: zmedico) by smtp.gentoo.org (Postfix) with ESMTPSA id 64F8233BE05 for ; Wed, 21 Oct 2015 05:11:28 +0000 (UTC) Subject: Re: [gentoo-portage-dev] [PATCH] emerge(1): document --oneshot caveats (bug 563482) To: gentoo-portage-dev@lists.gentoo.org References: <1445369394-24758-1-git-send-email-zmedico@gentoo.org> <562699BA.4010901@gentoo.org> <20151021003737.GA12188@fraenk> From: Zac Medico X-Enigmail-Draft-Status: N1110 Message-ID: <56271E7C.60000@gentoo.org> Date: Tue, 20 Oct 2015 22:11:24 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-portage-dev@lists.gentoo.org Reply-to: gentoo-portage-dev@lists.gentoo.org MIME-Version: 1.0 In-Reply-To: <20151021003737.GA12188@fraenk> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Archives-Salt: 0e690a2b-7078-40cc-b68a-5bda96fb05f8 X-Archives-Hash: cdeb874685df6c1ff6e3a7c1de4d740f On 10/20/2015 05:37 PM, Rob Wortman wrote: > On 2015-10-20 at 21:44:58 +0200, bernalex@gentoo.org wrote: >> (since it's describing somewhat complicated functionality) > > So, I'm curious what's actually going on there. If I emerge packages > with --oneshot, does that create the possibility of broken dependencies > for world-reachable packages, or does updating @world create the > possiblity of broken dependencies for oneshot'ed packages? > Any packages that are not reachable from @world are ripe for removal by --depclean, so we allow their dependencies to break in order to satisfy other dependencies (like in bug 563482). If you don't use --deep, then emerge may try to build something that depends on one of these unreachable packages with broken dependencies, such that whatever you are trying to build has broken indirect dependencies (which is likely to trigger a build failure like in bug 563482). -- Thanks, Zac