diff options
author | Petr Šabata <contyk@redhat.com> | 2020-11-07 12:55:46 +0100 |
---|---|---|
committer | Zac Medico <zmedico@gentoo.org> | 2020-11-21 16:35:49 -0800 |
commit | 222adeecbd72f070eaa05e39b0951cabd6ba8026 (patch) | |
tree | 0bfe3c722d9aa15581f0bca3e5ebb8a7e73936fc /doc | |
parent | Add slot operator := BDEPEND unit tests for bug 752153 (diff) | |
download | portage-222adeecbd72f070eaa05e39b0951cabd6ba8026.tar.gz portage-222adeecbd72f070eaa05e39b0951cabd6ba8026.tar.bz2 portage-222adeecbd72f070eaa05e39b0951cabd6ba8026.zip |
Typofix: Use just one definite article
I first noticed this in make.conf(5) but it turned out there were many
more occurences of these; fixed with find & sed.
Closes: https://github.com/gentoo/portage/pull/634
Signed-off-by: Petr Šabata <contyk@redhat.com>
Signed-off-by: Zac Medico <zmedico@gentoo.org>
Diffstat (limited to 'doc')
-rw-r--r-- | doc/package/ebuild/eapi/4.docbook | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/package/ebuild/eapi/4.docbook b/doc/package/ebuild/eapi/4.docbook index 8dd0f1487..9120c0ff0 100644 --- a/doc/package/ebuild/eapi/4.docbook +++ b/doc/package/ebuild/eapi/4.docbook @@ -153,7 +153,7 @@ This new REQUIRED_USE metadata key is used to specify what USE flag combinations It's a semi common occurrence that an ebuild may need to state that they disallow USE flags in specific combinations- either mysql or sqlite for example, but not both. </para> <para> -Existing solutions rely on checking the the USE configuration in pkg_setup which is non-optimal due to pkg_setup being ran potentially hours after the initial emerge -p invocation. +Existing solutions rely on checking the USE configuration in pkg_setup which is non-optimal due to pkg_setup being ran potentially hours after the initial emerge -p invocation. </para> <para> Current versions of EAPI4 support a phase hook pkg_pretend that is intended to move pre-build checks to just after resolution. It has been proposed that pkg_pretend should continue the tradition of adhoc shell code validating the USE state- this too is non optimal for the following reasons- |