View | Details | Raw Unified
Collapse All | Expand All

(-) hb-guide-metadata.xml (-16 / +18 lines)
 Lines 19-27    Link Here  
<body>
<body>

        
<p>
<p>

            

              
The <c>metadata.xml</c> file has as its purpose to give extra information about

              
The <path>metadata.xml</path> file has as its purpose to give extra information

            

            

              
ebuilds. The <c>metadata.xml</c> file should exist in every package directory.

              
about ebuilds. The <path>metadata.xml</path> file should exist in every package

            

            

              
A skel file can be found as <c>skel.metadata.xml</c> in the portage tree.

              
directory.  A skel file can be found as <path>skel.metadata.xml</path> in the

            

            

              

              
portage tree.

            

        
</p>
</p>

        

        
</body>
</body>

  

    

    

       Lines 34-40
       
    
  Link Here 
    

  

        
<body>
<body>

        

        
<p>
<p>

            

              
A <c>metadata.xml</c> file can contain a number of tags:

              
A <path>metadata.xml</path> file can contain a number of tags:

            

        
</p>
</p>

        

        
<table>
<table>

  

    

    

       Lines 47-56
       
    
  Link Here 
    

  

        
    <brite>&lt;pkgmetadata&gt;</brite>
    <brite>&lt;pkgmetadata&gt;</brite>

        
  </ti>
  </ti>

        
  <ti>
  <ti>

            

              
    This is the root element of the metadata.xml file for packages. It has 

              
    This is the root element of the <path>metadata.xml</path> file for

            

            

              
    no attributes. Its required subtag is: <brite>&lt;herd&gt;</brite>. 

              
    packages. It has no attributes. Its required subtag is:

            

            

              
    Furthermore, the following subtags are allowed: <brite>&lt;email&gt;</brite> 

              
    <brite>&lt;herd&gt;</brite>.  Furthermore, the following subtags are

            

            

              
    for a general herd email address, <brite>&lt;maintainer&gt;</brite>, and 

              
    allowed: <brite>&lt;email&gt;</brite> for a general herd email address,

            

            

              

              
    <brite>&lt;maintainer&gt;</brite>, and

            

        
    <brite>&lt;longdescription&gt;</brite>.
    <brite>&lt;longdescription&gt;</brite>.

        
  </ti>
  </ti>

        
</tr>
</tr>

  

    

    

       Lines 59-67
       
    
  Link Here 
    

  

        
    <brite>&lt;catmetadata&gt;</brite>
    <brite>&lt;catmetadata&gt;</brite>

        
  </ti>
  </ti>

        
  <ti>
  <ti>

            

              
    This is the root element of the metadata.xml file for categories as per 

              
    This is the root element of the <path>metadata.xml</path> file for

            

            

              
    <uri link="/proj/en/glep/glep-0034.html">GLEP 34</uri>. It has 

              
    categories as per <uri link="/proj/en/glep/glep-0034.html">GLEP 34</uri>.

            

            

              
    no attributes. It contains a number of 

              
    It has no attributes. It contains a number of 

            

        
    <brite>&lt;longdescription&gt;</brite> tags, each for a different 
    <brite>&lt;longdescription&gt;</brite> tags, each for a different 

        
    language.
    language.

        
  </ti>
  </ti>

  

    

    

       Lines 72-78
       
    
  Link Here 
    

  

        
  </ti>
  </ti>

        
  <ti>
  <ti>

        
    There must at least be one herd subtag. The contents of this tag must be
    There must at least be one herd subtag. The contents of this tag must be

            

              
	the name of a herd as specified in the <uri 

              
    the name of a herd as specified in the <uri 

            

        
    link="http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo/xml/htdocs/proj/en/metastructure/herds/herds.xml?content-type=text/plain&amp;rev=HEAD">herds.xml</uri>
    link="http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo/xml/htdocs/proj/en/metastructure/herds/herds.xml?content-type=text/plain&amp;rev=HEAD">herds.xml</uri>

        
    file or the "no-herd" herd. It must occur at least once.
    file or the "no-herd" herd. It must occur at least once.

        
  </ti>
  </ti>

  

    

    

       Lines 82-88
       
    
  Link Here 
    

  

        
    <brite>&lt;maintainer&gt;</brite>
    <brite>&lt;maintainer&gt;</brite>

        
  </ti>
  </ti>

        
  <ti>
  <ti>

            

              
    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 
    The maintainers of a package can be specified with the 

        
    <brite>&lt;maintainer&gt;</brite> tag. This tag has one required subtag: 
    <brite>&lt;maintainer&gt;</brite> tag. This tag has one required subtag: 

        
    <brite>&lt;email&gt;</brite>. It has two optional subtags:
    <brite>&lt;email&gt;</brite>. It has two optional subtags:

  

    

    

       Lines 231-239
       
    
  Link Here 
    

  

        
<body>
<body>

        

        
<p>
<p>

            

              
As second example we view the <path>metadata.xml</path> of <c>mirrorselect</c>.

              
For the second example, we will examine the <path>metadata.xml</path> of

            

            

              
This ebuild is maintained by the <c>tools-portage</c> herd, but has a separate

              
<c>app-portage/mirrorselect</c>.  This ebuild is maintained by the

            

            

              
maintainer.

              
<c>tools-portage</c> herd, but has a separate maintainer.

            

        
</p>
</p>

        

        
<pre caption="Herd &amp; individually maintained package">
<pre caption="Herd &amp; individually maintained package">