From: Zac Medico <zmedico@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Cc: Zac Medico <zmedico@gentoo.org>
Subject: [gentoo-portage-dev] [PATCH] emerge(1): document --oneshot caveats (bug 563482)
Date: Tue, 20 Oct 2015 12:29:54 -0700 [thread overview]
Message-ID: <1445369394-24758-1-git-send-email-zmedico@gentoo.org> (raw)
X-Gentoo-Bug: 563482
X-Gentoo-Bug-URL: https://bugs.gentoo.org/show_bug.cgi?id=563482
---
man/emerge.1 | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/man/emerge.1 b/man/emerge.1
index 237fb79..c03f044 100644
--- a/man/emerge.1
+++ b/man/emerge.1
@@ -676,6 +676,13 @@ packages that depend on matching packages due to \fB\-\-rebuild\fR.
.BR "\-\-oneshot " (\fB\-1\fR)
Emerge as normal, but do not add the packages to the world file
for later updating.
+
+\fBWARNING:\fR This option should only be used for packages that are
+reachable from the @world package set (those that would not be removed
+by \fB\-\-depclean\fR), since dependencies of unreachable packages are
+allowed to be broken when satisfying dependencies of other packages.
+Broken dependencies of this sort will invalidate assumptions that make
+it possible for \fB\-\-deep\fR to be disabled by default.
.TP
.BR "\-\-onlydeps " (\fB\-o\fR)
Only merge (or pretend to merge) the dependencies of the packages
--
2.4.9
next reply other threads:[~2015-10-20 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-20 19:29 Zac Medico [this message]
2015-10-20 19:44 ` [gentoo-portage-dev] [PATCH] emerge(1): document --oneshot caveats (bug 563482) 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
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=1445369394-24758-1-git-send-email-zmedico@gentoo.org \
--to=zmedico@gentoo.org \
--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