Index: hb-guide-metadata.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/proj/en/devrel/handbook/hb-guide-metadata.xml,v
retrieving revision 1.11
diff -u -B -r1.11 hb-guide-metadata.xml
--- hb-guide-metadata.xml 31 Mar 2008 18:30:36 -0000 1.11
+++ hb-guide-metadata.xml 10 Jul 2008 21:23:59 -0000
@@ -19,9 +19,10 @@
-The metadata.xml file has as its purpose to give extra information about
-ebuilds. The metadata.xml file should exist in every package directory.
-A skel file can be found as skel.metadata.xml in the portage tree.
+The metadata.xml file has as its purpose to give extra information
+about ebuilds. The metadata.xml file should exist in every package
+directory. A skel file can be found as skel.metadata.xml in the
+portage tree.
@@ -34,7 +35,7 @@
-A metadata.xml file can contain a number of tags:
+A metadata.xml file can contain a number of tags:
@@ -47,10 +48,11 @@
<pkgmetadata>
- This is the root element of the metadata.xml file for packages. It has
- no attributes. Its required subtag is: <herd>.
- Furthermore, the following subtags are allowed: <email>
- for a general herd email address, <maintainer>, and
+ This is the root element of the metadata.xml file for
+ packages. It has no attributes. Its required subtag is:
+ <herd>. Furthermore, the following subtags are
+ allowed: <email> for a general herd email address,
+ <maintainer>, and
<longdescription>.
@@ -59,9 +61,9 @@
<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
+ 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.
@@ -72,7 +74,7 @@
There must at least be one herd subtag. The contents of this tag must be
- the name of a herd as specified in the herds.xml
file or the "no-herd" herd. It must occur at least once.
@@ -82,7 +84,7 @@
<maintainer>
- Besides being member of a herd, a package can also be maintained directly.
+ 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:
@@ -231,9 +233,9 @@
-As second example we view the metadata.xml of mirrorselect.
-This ebuild is maintained by the tools-portage herd, but has a separate
-maintainer.
+For the second example, we will examine the metadata.xml of
+app-portage/mirrorselect. This ebuild is maintained by the
+tools-portage herd, but has a separate maintainer.