This is an automated email from the git hooks/post-receive script. guillem pushed a commit to branch main in repository dpkg.
View the commit online: https://git.dpkg.org/cgit/dpkg/dpkg.git/commit/?id=6a2e7711d25e1e17c218f98e004b38396ba67181 commit 6a2e7711d25e1e17c218f98e004b38396ba67181 Author: Guillem Jover <[email protected]> AuthorDate: Sun Sep 17 04:10:30 2023 +0200 doc, man: Use field name or field-name instead of fieldname For symbols in code fieldname is appropriate, but for documentation let's write the more correct «field name» instead. --- man/deb-src-control.pod | 4 ++-- man/deb-substvars.pod | 8 ++++---- scripts/Dpkg/Control/Fields.pm | 4 ++-- scripts/Dpkg/Control/FieldsCore.pm | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/man/deb-src-control.pod b/man/deb-src-control.pod index 7e1d69f6a..18b0da233 100644 --- a/man/deb-src-control.pod +++ b/man/deb-src-control.pod @@ -37,11 +37,11 @@ This file contains at least 2 stanzas, separated by a blank line. The first stanza lists all information about the source package in general, while each following stanza describes exactly one binary package. Each stanza consists of at least one field. -A field starts with a fieldname, such as B<Package> or B<Section> +A field starts with a field name, such as B<Package> or B<Section> (case insensitive), followed by a colon, the body of the field (case sensitive unless stated otherwise) and a newline. Multi-line fields are also allowed, but each supplementary line, without a -fieldname, should start with at least one space. The content of the multi-line +field name, should start with at least one space. The content of the multi-line fields is generally joined to a single line by the tools (except in the case of the B<Description> diff --git a/man/deb-substvars.pod b/man/deb-substvars.pod index 5b74c5df8..a8d98efb4 100644 --- a/man/deb-substvars.pod +++ b/man/deb-substvars.pod @@ -184,19 +184,19 @@ is copied into the B<Installed-Size> control file field. -=item B<S:>I<fieldname> +=item B<S:>I<field-name> The value of the source stanza field -I<fieldname> +I<field-name> (which must be given in the canonical capitalization; since dpkg 1.18.11). Setting these variables has no effect other than on places where they are expanded explicitly. These variables are only available when generating binary control files. -=item B<F:>I<fieldname> +=item B<F:>I<field-name> The value of the output field -I<fieldname> +I<field-name> (which must be given in the canonical capitalization). Setting these variables has no effect other than on places where they are expanded explicitly. diff --git a/scripts/Dpkg/Control/Fields.pm b/scripts/Dpkg/Control/Fields.pm index 8743dc976..a58356699 100644 --- a/scripts/Dpkg/Control/Fields.pm +++ b/scripts/Dpkg/Control/Fields.pm @@ -21,9 +21,9 @@ Dpkg::Control::Fields - manage (list of official) control fields =head1 DESCRIPTION -The module contains a list of vendor-neutral and vendor-specific fieldnames +The module contains a list of vendor-neutral and vendor-specific field names with associated meta-data explaining in which type of control information -they are allowed. The vendor-neutral fieldnames and all functions are +they are allowed. The vendor-neutral field names and all functions are inherited from Dpkg::Control::FieldsCore. =cut diff --git a/scripts/Dpkg/Control/FieldsCore.pm b/scripts/Dpkg/Control/FieldsCore.pm index 32f2c1041..4e213e294 100644 --- a/scripts/Dpkg/Control/FieldsCore.pm +++ b/scripts/Dpkg/Control/FieldsCore.pm @@ -21,7 +21,7 @@ Dpkg::Control::FieldsCore - manage (list of official) control fields =head1 DESCRIPTION -The modules contains a list of fieldnames with associated meta-data explaining +The modules contains a list of field names with associated meta-data explaining in which type of control information they are allowed. The types are the CTRL_* constants exported by Dpkg::Control. -- Dpkg.Org's dpkg
