From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path:
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id E86B71381F3
for ; Sun, 11 Nov 2012 19:34:27 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 9B68D21C02F;
Sun, 11 Nov 2012 19:33:40 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
(using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id F0EFC21C02F
for ; Sun, 11 Nov 2012 19:33:39 +0000 (UTC)
Received: from hornbill.gentoo.org (hornbill.gentoo.org [94.100.119.163])
(using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by smtp.gentoo.org (Postfix) with ESMTPS id A561E33D968
for ; Sun, 11 Nov 2012 19:33:38 +0000 (UTC)
Received: from localhost.localdomain (localhost [127.0.0.1])
by hornbill.gentoo.org (Postfix) with ESMTP id 5CD7AE544C
for ; Sun, 11 Nov 2012 19:33:34 +0000 (UTC)
From: "Markos Chandras"
To: gentoo-commits@lists.gentoo.org
Content-Transfer-Encoding: 8bit
Content-type: text/plain; charset=UTF-8
Reply-To: gentoo-dev@lists.gentoo.org, "Markos Chandras"
Message-ID: <1352662344.87754bded18b620fd926426acf0733b8f9a8403e.hwoarang@gentoo>
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/misc-files/metadata/
X-VCS-Repository: proj/devmanual
X-VCS-Files: ebuild-writing/misc-files/metadata/text.xml
X-VCS-Directories: ebuild-writing/misc-files/metadata/
X-VCS-Committer: hwoarang
X-VCS-Committer-Name: Markos Chandras
X-VCS-Revision: 87754bded18b620fd926426acf0733b8f9a8403e
X-VCS-Branch: master
Date: Sun, 11 Nov 2012 19:33:34 +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-Archives-Salt: 7c685703-41c1-4117-ad4f-a223dd5720d9
X-Archives-Hash: 4997d5b72b4a20efdc0b77ae115199b1
commit: 87754bded18b620fd926426acf0733b8f9a8403e
Author: Markos Chandras gentoo org>
AuthorDate: Sat Nov 3 22:20:06 2012 +0000
Commit: Markos Chandras gentoo org>
CommitDate: Sun Nov 11 19:32:24 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/devmanual.git;a=commit;h=87754bde
metadata: Add examples from the devrel handbook
---
ebuild-writing/misc-files/metadata/text.xml | 464 +++++++++++++++++++++++++--
1 files changed, 442 insertions(+), 22 deletions(-)
diff --git a/ebuild-writing/misc-files/metadata/text.xml b/ebuild-writing/misc-files/metadata/text.xml
index 1cd4081..5e6cd52 100644
--- a/ebuild-writing/misc-files/metadata/text.xml
+++ b/ebuild-writing/misc-files/metadata/text.xml
@@ -19,31 +19,452 @@ provided, an English long description must be present. A typical
example might look like:
+
+
+
+
+A metadata.xml file can contain a number of tags:
+
+
+
+
+ tag |
+ description |
+
+
+
+ <pkgmetadata>
+
+
+ This is the root element of the metadata.xml file for
+ packages. It has no attributes. The following subtags are
+ allowed:
+ <herd>,
+ <maintainer>,
+ <longdescription>,
+ <use>, and
+ <upstream>.
+ There should be at least one <herd> or
+ <maintainer> subtag.
+
+
+
+
+ <catmetadata>
+
+
+ This is the root element of the metadata.xml file for
+ categories as per GLEP 34.
+ It has no attributes. It contains a number of
+ <longdescription> tags, each for a different
+ language.
+
+
+
+
+ <herd>
+
+
+ If a package is maintained by one or more herds, names of these herds
+ can be specified with the <herd> tag. The names
+ used in this tag must be the same as specified in the herds.xml
+ file.
+
+
+
+
+ <maintainer>
+
+
+ Besides being part of a herd, a package can also be maintained directly.
+ The maintainers of a package can be specified with the
+ <maintainer> tag. This tag has one required subtag:
+ <email>. It has two optional subtags:
+ <name>, and <description>.
+
+
+
+ <email>
+
+ This contains the e-mail address of the maintainer. It is required.
+
+
+
+ <name>
+
+ This contains freetext with the name of the maintainer. It is optional.
+
+
+
+ <description>
+
+ The description tag contains a description of the maintainership, or for
+ example a remark that someone interested can take over the maintainership.
+ It is optional.
+
+
+
+ <longdescription>
+
+ This tag contains a description of the package. This is to augment the
+ DESCRIPTION field in the ebuilds themselves. This tag has two optional
+ subtags: <pkg> and <cat>.
+
+
+
+ <use>
+
+ This tag contains descriptions of USE flags.
+ This tag is optional and, if specified, has one required subtag:
+ <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.
+ It also requires the USE flag to be named in the name attribute.
+ This tag has two optional subtags: <pkg> and
+ <cat>.
+
+
+
+ <upstream>
+
+ This tag contains information about the upstream developers/project.
+
+
+
+ <maintainer>
+
+ Name and e-mail of an upstream maintainer. May appear more than once.
+
+
+
+ <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 only once.
+
+
+
+ <email>
+
+ The email address of an upstream may appear only once.
+
+
+
+ <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
+ updated on new releases of the corresponding package. (This also implies that
+ one can link to an automatically updated changelog in case of vcs snapshots
+ only.)
+
+
+
+ <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
+ version independent. If the documentation is available in more than one language,
+ a lang attribute can be used which follows the same rules as the one for
+ longdescription.
+
+
+
+ <bugs-to>
+
+ Should contain a place where bugs can be filed, a URL or an e-mail address prefixed
+ with mailto:.
+
+
+
+ <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
+ information such as its Freshmeat ID or its CPAN name.
+
+
+
+ <pkg>
+
+ This tag contains a valid package name in the format of a DEPEND.
+
+
+
+ <cat>
+
+ This tag contains a valid category name as defined in
+ profiles/categories.
+
+
+
+
+
+There are also some attributes that can be used with these tags. They are all
+optional:
+
+
+
+
+ attribute |
+ tags |
+ description |
+
+
+ lang
+
+ <description>, <longdescription>,
+ <use>, <doc>
+
+
+ In every case where a description is required, there must be at
+ least an english description. If an additional description in
+ another language is given, this attribute is used to specify the language
+ used. The format is the two-character language code as defined by the ISO-639-1
+ norm.
+
+
+
+ restrict
+
+ <herd>, <maintainer>,
+ <longdescription>, <flag>
+
+
+ The restrict attribute allows one to restrict the application of certain
+ tags to certain versions of a package. When this attribute is used, a tag
+ without this attribute must also exist. That tag without the restrict
+ attribute will serve as the default. The format of the restrict attribute
+ is that of the DEPEND flag, except that "<" and
+ ">" need to be specified by < and >.
+
+ For example, in the sys-libs/db package,
+ restrict=">=sys-libs/db-3.2.9-r5" on the
+ maintainer tag shows that I'm currently maintaining all
+ versions greater then 3.2.9-r5.
+
+
+
+ name
+
+ <flag>
+
+
+ This attribute is required on the <flag> tag. It
+ simply contains the USE flag.
+
+ For example, in the sys-apps/hal package, <flag name='acpi'>
+ Enables ACPI</flag>
+
+
+
+ status
+
+ <maintainer>
+
+
+ The upstream maintainer element has a status attribute, which is one of active or inactive.
+ This attribute is not mandatory. The absence of it shall be interpreted as unknown.
+ Please note: This attribute is only allowed in the <upstream> <maintainer> element!
+
+
+
+ type
+
+ <remote-id>
+
+
+ A string identifying the type of upstream source. A list of valid strings are kept in metadata.dtd.
+ Developers should email the gentoo-dev mailing list before using a new type value.
+
+
+
+
+
+
+
+
+