From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 320DF138334 for ; Mon, 9 Dec 2019 21:40:01 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 5B942E089D; Mon, 9 Dec 2019 21:40:00 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2F830E089D for ; Mon, 9 Dec 2019 21:40:00 +0000 (UTC) Received: from oystercatcher.gentoo.org (oystercatcher.gentoo.org [148.251.78.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTPS id ECC8E34D8CA for ; Mon, 9 Dec 2019 21:39:58 +0000 (UTC) Received: from localhost.localdomain (localhost [IPv6:::1]) by oystercatcher.gentoo.org (Postfix) with ESMTP id 8687B8D7 for ; Mon, 9 Dec 2019 21:39:56 +0000 (UTC) From: "Ulrich Müller" To: gentoo-commits@lists.gentoo.org Content-Transfer-Encoding: 8bit Content-type: text/plain; charset=UTF-8 Reply-To: gentoo-dev@lists.gentoo.org, "Ulrich Müller" Message-ID: <1575804723.688b7114682f9faf594d1aa740de1b6dd9c653ac.ulm@gentoo> Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/misc-files/metadata/, ebuild-maintenance/maintenance-tasks/, ... X-VCS-Repository: proj/devmanual X-VCS-Files: ebuild-maintenance/git/text.xml ebuild-maintenance/maintenance-tasks/text.xml ebuild-writing/misc-files/metadata/text.xml X-VCS-Directories: ebuild-maintenance/git/ ebuild-maintenance/maintenance-tasks/ ebuild-writing/misc-files/metadata/ X-VCS-Committer: ulm X-VCS-Committer-Name: Ulrich Müller X-VCS-Revision: 688b7114682f9faf594d1aa740de1b6dd9c653ac X-VCS-Branch: master Date: Mon, 9 Dec 2019 21:39:56 +0000 (UTC) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-commits@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply X-Archives-Salt: 4b3b06ea-4fef-4aed-a2bb-11ed05c4b0d5 X-Archives-Hash: 854471ceb6d68d462b989e49e55364c3 commit: 688b7114682f9faf594d1aa740de1b6dd9c653ac Author: Ulrich Müller gentoo org> AuthorDate: Wed Dec 4 17:06:29 2019 +0000 Commit: Ulrich Müller gentoo org> CommitDate: Sun Dec 8 11:32:03 2019 +0000 URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=688b7114 Elements , , and are not supported. Use instead, which seems to be the most appropriate replacement in their respective contexts. Signed-off-by: Ulrich Müller gentoo.org> ebuild-maintenance/git/text.xml | 2 +- ebuild-maintenance/maintenance-tasks/text.xml | 16 ++--- ebuild-writing/misc-files/metadata/text.xml | 95 +++++++++++++-------------- 3 files changed, 54 insertions(+), 59 deletions(-) diff --git a/ebuild-maintenance/git/text.xml b/ebuild-maintenance/git/text.xml index 70fa46a..ee32c9c 100644 --- a/ebuild-maintenance/git/text.xml +++ b/ebuild-maintenance/git/text.xml @@ -279,7 +279,7 @@ mirrored by Gentoo is referenced, it will be closed (as fixed) automatically with reference to the commit.
  • Package-Manager: This is automatically inserted by repoman commit and it specifies the version of -sys-apps/portage on the system.
    • +sys-apps/portage on the system.
  • RepoMan-Options: This is automatically inserted by repoman commit and records the options passed to repoman (such as --force) for the commit.
    • diff --git a/ebuild-maintenance/maintenance-tasks/text.xml b/ebuild-maintenance/maintenance-tasks/text.xml index 2b16ce3..92dd0a0 100644 --- a/ebuild-maintenance/maintenance-tasks/text.xml +++ b/ebuild-maintenance/maintenance-tasks/text.xml @@ -149,18 +149,16 @@ looking for is not listed then please consult the relevant lead.

    -You should never stabilize packages on -architectures for which you cannot test and instead you should file a bug to -the relevant architecture team, such as -sparc@gentoo.org asking them to stabilize the -ebuild. Alternatively, you may be able to find Gentoo developers on -IRC who could help you with your request. +You should never stabilize packages on architectures for which you +cannot test and instead you should file a bug to the relevant architecture +team, such as sparc@gentoo.org asking them to stabilize the ebuild. +Alternatively, you may be able to find Gentoo developers on IRC who could help +you with your request.

    -It is best to not use -arch-maintainers@gentoo.org, adding architecture teams onto a -bug's CC list individually instead. That way teams can remove +It is best to not use arch-maintainers@gentoo.org, adding architecture +teams onto a bug's CC list individually instead. That way teams can remove themselves from the list when they are done, giving a clear indication of which teams still have to stabilize a package.

    diff --git a/ebuild-writing/misc-files/metadata/text.xml b/ebuild-writing/misc-files/metadata/text.xml index 7260e48..a89a512 100644 --- a/ebuild-writing/misc-files/metadata/text.xml +++ b/ebuild-writing/misc-files/metadata/text.xml @@ -49,71 +49,69 @@ metadata.xml: - <catmetadata> + <catmetadata> This is the root element of the metadata.xml file for categories. It has no attributes. It contains a number of - <longdescription> tags, each for a different - language. + <longdescription> tags, each for a different language. - <pkgmetadata> + <pkgmetadata> This is the root element of the metadata.xml file for packages. It has no attributes. The following subtags are allowed: - <longdescription>, - <maintainer>, - <slots>, - <use>, and - <upstream>. + <longdescription>, + <maintainer>, + <slots>, + <use>, and + <upstream>. While all the subtags are optional, <upstream> may appear at most once. - <longdescription> + <longdescription> This tag contains a description for a category or a package. For packages, it is used to augment the DESCRIPTION field in the ebuilds themselves. This tag has - two optional subtags: <pkg> and - <cat>. + two optional subtags: <pkg> and <cat>. - <maintainer> + <maintainer> This tag specifies the persons and/or projects responsible for the maintenance of a package. The type attribute must - be specified and can be either "person" or - "project". There is one required subtag: - <email>. It has two optional subtags: - <name> and - <description>. + be specified and can be either "person" or "project". + There is one required subtag: + <email>. It has two optional subtags: + <name> and + <description>. - <email> + <email> This contains the e-mail address of the maintainer. It is required. - <name> + <name> This contains freetext with the name of the maintainer. It is optional. - <description> + <description> The description tag contains a description of the maintainership, or for example a remark that someone interested can take over the maintainership. @@ -121,7 +119,7 @@ metadata.xml: - <slots> + <slots> This tag describes the slots of a package. @@ -129,40 +127,40 @@ metadata.xml: - <slot> + <slot> This contains information for a particular slot. The name attribute is mandatory and specifies the name of the slot. - <subslots> + <subslots> Describes the meaning of subslots for the whole package. This tag may appear at most once. - <use> + <use> This tag contains descriptions of USE flags. This tag is optional and, if specified, has one required subtag: - <flag>. + <flag>. - <flag> + <flag> This tag contains a description of how the named USE flag affects this - package. It is required if the <use> tag is specified. + package. It is required if the <use> tag is specified. It also requires the USE flag to be named in the name attribute. - This tag has two optional subtags: <pkg> and - <cat>. + This tag has two optional subtags: <pkg> and + <cat>. - <upstream> + <upstream> This tag contains information about the upstream developers/project. It supports multiple optional subtags: <maintainer>, @@ -171,7 +169,7 @@ metadata.xml: - <maintainer> + <maintainer> Provides information about the upstream maintainer. It requires a <name> subtag to be specified, supports an optional @@ -179,20 +177,20 @@ metadata.xml: - <name> + <name> The name of an upstream maintainer should contain a block of text with upstream's name. This element is mandatory for an upstream maintainer and must appear exactly once. - <email> + <email> The email address of an upstream maintainer. May appear only once. - <changelog> + <changelog> Should contain a URL where the location of the upstream changelog can be found. The URL must be version independent and must point to a changelog which is only @@ -202,7 +200,7 @@ metadata.xml: - <doc> + <doc> Should contain a URL where the location of the upstream documentation can be found. The link must not point to any third party documentation and must be @@ -212,14 +210,14 @@ metadata.xml: - <bugs-to> + <bugs-to> Should contain a place where bugs can be filed, a URL or an e-mail address prefixed with mailto:. May appear at most once. - <remote-id> + <remote-id> Should specify a type of package identification tracker and the identification that corresponds to the package in question. remote-id should make it easier to index @@ -229,13 +227,13 @@ metadata.xml: - <pkg> + <pkg> This tag contains a valid qualified package name. - <cat> + <cat> This tag contains a valid category name as defined in profiles/categories. @@ -256,9 +254,8 @@ There are also some attributes that can be used with these tags: lang - <description>, <longdescription>, - <slots>, - <use>, <doc> + <description>, <longdescription>, + <slots>, <use>, <doc> In every case where a description is required, there must be at @@ -272,8 +269,8 @@ There are also some attributes that can be used with these tags: restrict - <maintainer>, - <longdescription>, <flag> + <maintainer>, + <longdescription>, <flag> The restrict attribute allows one to restrict the application of @@ -289,7 +286,7 @@ There are also some attributes that can be used with these tags: name - <flag>, <slot> + <flag>, <slot> When this attribute is required on the <flag> tag, it @@ -304,7 +301,7 @@ There are also some attributes that can be used with these tags: status - <maintainer> + <maintainer> The upstream maintainer element has a status attribute, which is @@ -318,7 +315,7 @@ There are also some attributes that can be used with these tags: type - <remote-id> + <remote-id> A string identifying the type of upstream source. A list of valid strings are kept in @@ -329,7 +326,7 @@ There are also some attributes that can be used with these tags: type - <maintainer> + <maintainer> Defines the type of the maintainer for a package. There are only