aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2006-10-28 13:06:18 +0000
committerAvatar Ciaran McCreesh <ciaran.mccreesh@googlemail.com> 2006-10-28 13:06:18 +0000
commitf2c2efb21cb67ca47f30e04265a56690f37e5e88 (patch)
tree2cdc539077435d20e942893b03e126a31f7ab708
parent1bea7526f6ef04ab85cdc425a161d3af0a7ce5d2 (diff)
downloadpaludis-f2c2efb21cb67ca47f30e04265a56690f37e5e88.tar.gz
paludis-f2c2efb21cb67ca47f30e04265a56690f37e5e88.tar.xz
Docs tweak from Richard Brown
-rw-r--r--doc/doc_known_issues.doxygen2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/doc_known_issues.doxygen b/doc/doc_known_issues.doxygen
index 6301cf8..615e9db 100644
--- a/doc/doc_known_issues.doxygen
+++ b/doc/doc_known_issues.doxygen
@@ -74,7 +74,7 @@ Rationale: This leads to corruption and wasted bandwidth far too frequently. In
Non-Problem: Paludis doesn't have an equivalent to --resume --skipfirst in Portage.
-Rationale: Too unreliable, too flaky and far too widely abused. There's talk of echoing a command (<code>paludis -i10 =sys-apps/foo-1.23-r1 =app-misc/fnord-2 ...</code>) that can be used to resume if an ebuild exits with an error, but that's not set in stone.
+Rationale: Too unreliable, too flaky and far too widely abused; however, if an ebuild exits with an error, Paludis will echo a resume command (<code>paludis -i10 =sys-apps/foo-1.23-r1 =app-misc/fnord-2 ...</code>) that can be used to resume the build.
\subsection KnownNonIssuesNice Automatic Niceness Support