summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2009-03-27 07:23:22 +0000
committerZac Medico <zmedico@gentoo.org>2009-03-27 07:23:22 +0000
commite21f4cb89864786cc4f2082d9dd4595a9c0e55df (patch)
tree673bfb4c31bdd983fa61058975aea8a26d1ec1f9
parentIn config.setcpv(), make sure the current args are really identical to the (diff)
downloadportage-multirepo-e21f4cb89864786cc4f2082d9dd4595a9c0e55df.tar.gz
portage-multirepo-e21f4cb89864786cc4f2082d9dd4595a9c0e55df.tar.bz2
portage-multirepo-e21f4cb89864786cc4f2082d9dd4595a9c0e55df.zip
Fix typo in comment. (trunk r13230)
svn path=/main/branches/2.1.6/; revision=13231
-rw-r--r--pym/portage/__init__.py2
1 files changed, 1 insertions, 1 deletions
diff --git a/pym/portage/__init__.py b/pym/portage/__init__.py
index 3ff952b7..b209fe65 100644
--- a/pym/portage/__init__.py
+++ b/pym/portage/__init__.py
@@ -5043,7 +5043,7 @@ def eapi_is_supported(eapi):
# Generally, it's best not to assume that cache entries for unsupported EAPIs
# can be validated. However, the current package manager specification does not
-# guarantee that that the EAPI can be parsed without sourcing the ebuild, so
+# guarantee that the EAPI can be parsed without sourcing the ebuild, so
# it's too costly to discard existing cache entries for unsupported EAPIs.
# Therefore, by default, assume that cache entries for unsupported EAPIs can be
# validated. If FEATURES=parse-eapi-* is enabled, this assumption is discarded