From: Rob Wortman <wyrm@haell.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] emerge(1): document --oneshot caveats (bug 563482)
Date: Wed, 21 Oct 2015 09:13:34 -0700 [thread overview]
Message-ID: <20151021161334.GA7917@fraenk> (raw)
In-Reply-To: <56271E7C.60000@gentoo.org>
On 2015-10-20 at 22:11:24 -0700, zmedico@gentoo.org wrote:
> 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).
I think I understand. So, one could get the hypothetical scenario:
# emerge --oneshot A # which depends on B
# emerge --update @world # shuffles stuff around breaking B
# emerge C # which depends on A
Package C's dependency is filled, so emerge goes ahead and builds C.
Now, either C fails to build, or it is installed but fails at runtime,
because it depends on a package which depends on a package which is
broken.
Sound about right?
--
There are problems in today's world that cannot be
solved by the level of thinking that created them.
-- Albert Einstein
next prev parent reply other threads:[~2015-10-21 16:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 19:29 [gentoo-portage-dev] [PATCH] emerge(1): document --oneshot caveats (bug 563482) Zac Medico
2015-10-20 19:44 ` Alexander Berntsen
2015-10-21 0:37 ` Rob Wortman
2015-10-21 1:51 ` [gentoo-portage-dev] " Duncan
2015-10-21 5:11 ` [gentoo-portage-dev] " Zac Medico
2015-10-21 16:13 ` Rob Wortman [this message]
2015-10-21 19:26 ` Zac Medico
2015-10-22 2:34 ` [gentoo-portage-dev] " Duncan
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=20151021161334.GA7917@fraenk \
--to=wyrm@haell.com \
--cc=gentoo-portage-dev@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