From c08a1dc1072740182e5c4d059967db697897bed6 Mon Sep 17 00:00:00 2001 From: Sebastian Engel Date: Mon, 12 Aug 2024 11:12:05 +0200 Subject: [PATCH] Fix multiple typos and grammatical errors MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Sebastian Engel Signed-off-by: Ulrich Müller --- ebuild-writing/common-mistakes/text.xml | 2 +- ebuild-writing/eapi/text.xml | 2 +- quickstart/text.xml | 2 +- tasks-reference/pam/text.xml | 18 +++++++++--------- tools-reference/echo/text.xml | 4 ++-- tools-reference/find/text.xml | 2 +- 6 files changed, 15 insertions(+), 15 deletions(-) diff --git a/ebuild-writing/common-mistakes/text.xml b/ebuild-writing/common-mistakes/text.xml index e39e2e60..0b6adb86 100644 --- a/ebuild-writing/common-mistakes/text.xml +++ b/ebuild-writing/common-mistakes/text.xml @@ -263,7 +263,7 @@ bug about that ebuild.

You should try not to include version numbers in the SRC_URI and S. Always try to use ${PV} or ${P}. It makes maintaining the ebuild much easier. If a version -number is not consistent with the tarball/source, then use MY_P. An example +number is not consistent with the tarball/source, then use MY_P. For example dev-python/pyopenal fetches a tarball called PyOpenAL, so we redefine it like:

diff --git a/ebuild-writing/eapi/text.xml b/ebuild-writing/eapi/text.xml index 4943dba6..5c2f9b7f 100644 --- a/ebuild-writing/eapi/text.xml +++ b/ebuild-writing/eapi/text.xml @@ -1009,7 +1009,7 @@ pkg_postrm() {

- In the example provided above, the ebuild needs to be update the icon cache + In the example provided above, the ebuild needs to update the icon cache upon being installed or uninstalled. By placing the respective tool in IDEPEND, the ebuild requests it to be available at the time of pkg_postinst. When cross-compiling, the tool will be built for diff --git a/quickstart/text.xml b/quickstart/text.xml index 32e3ede3..9e22dfdb 100644 --- a/quickstart/text.xml +++ b/quickstart/text.xml @@ -74,7 +74,7 @@ At the top of the ebuild is a header block. This is present in all ebuilds.

-Ebuilds are indented using tabs, with each tab representing four places. +Ebuilds are indented using tabs, with each tab representing four spaces. See .

diff --git a/tasks-reference/pam/text.xml b/tasks-reference/pam/text.xml index 3094b20e..2cc794c4 100644 --- a/tasks-reference/pam/text.xml +++ b/tasks-reference/pam/text.xml @@ -80,15 +80,15 @@ The statement is composed of 3 or 4 tokens: methods. Some documentation states that we need to specify the full path of the module, but this creates problems because not all the systems install the modules in the same place: Linux-PAM on Gentoo is generally set up to load - them from /lib/security, but for example on AMD64 this become + them from /lib/security, but for example on AMD64 this becomes /lib64/security. The result is that providing the full path will lead to non-working pamd - files, and the right way to handle this is just states the module name the + files, and the right way to handle this is to just state the module name the PAM implementation will take care of finding the module.
  • - The last token, which can consist of multiple items, describe the parameters - passed to the module. These are module-dependent. + The last token, which can consist of multiple items, describes the + parameters passed to the module. These are module-dependent.
      • @@ -124,7 +124,7 @@ source for some services, such as mail and ftp servers.

      But for desktop systems, all the different services, such as mail servers, ftp -servers, ssh and so on, just need to authenticate in the same way the users logs +servers, ssh and so on, just need to authenticate in the same way the users log in to the system.

      @@ -175,13 +175,13 @@ for pamd files (dopamd and newpamd, whose usage is the same similar do* and new* functions) and the /etc/security files (dopamsecurity and newpamsecurity, which need the first argument to be the subdirectory of /etc/security in which the files are to be installed). -Those groups of functions already takes care of verifying whether the pam +Those groups of functions already take care of verifying whether the pam USE flag is made optional for the package if this is the case, and the flag is disabled, the pamd files are just skipped.

      -Many pamd files just uses one or more auth types from system-auth login class, +Many pamd files just use one or more auth types from system-auth login class, which is the base one which provides login facilities for most services on common desktop systems. Instead of adding a pamd file in ${FILESDIR} for this, one can use the pamd_mimic_system function. This function takes a series @@ -230,8 +230,8 @@ correct directory to use for the current implementation/arch.

      When the PAM module doesn't provide a way to install the package by itself, such as a Makefile or an installation script, there are also the dopammod and -newpammod functions which takes care of install the module in the right -directory. +newpammod functions, which take care of installing the module in the +right directory.

      diff --git a/tools-reference/echo/text.xml b/tools-reference/echo/text.xml index 9a84ab97..f72d833a 100644 --- a/tools-reference/echo/text.xml +++ b/tools-reference/echo/text.xml @@ -29,9 +29,9 @@ the same as the former, but they won't print the trailing newline

      All usage of the form echo ${somevar} | grep substring just to -check if the contents of the ${somevar} variable +check if the content of the ${somevar} variable contains substring, or more often, echo ${somevar} | -command, are deprecated and should be (and in most cases, can be) +command, is deprecated and should be (and in most cases, can be) used as less as possible: doing so involves for no reason an additional shell session and a pipe. The "here strings" section describes the preferred way of dealing with such cases. diff --git a/tools-reference/find/text.xml b/tools-reference/find/text.xml index 5825a390..0abe239e 100644 --- a/tools-reference/find/text.xml +++ b/tools-reference/find/text.xml @@ -77,7 +77,7 @@ Useful rules include: -maxdepth 3 Only descend 3 levels into subdirectories. - -maxdepth 1 will ignore all subdiretories of the specified path. + -maxdepth 1 will ignore all subdirectories of the specified path. no, GNU and BSD