man(1)

NAME
metagen - generate metadata.xml for ebuilds

SYNOPSIS
metagen [options]

DESCRIPTION
metagen will create a valid metadata.xml file in the current directory. If you need multiple elements, such as two email addresses, use a comma to separate them. See EXAMPLES.

OPTIONS
--email | -e email-address
    Package maintainer's email address --name | -n maintainer-name
    Package maintainer's name (used with -e option) --echangelog | -m
    Uses ECHANGELOG_USER variable. Can be used instead of -e and -n --type | -t type
    Maintainer type as of GLEP 67; valid types are: "person", "project", "unknown"
    (required with --email|-e and --echangelog|-m options) --desc | -d description
    Description of maintainership (used with -e option) --long | -l long-description
    Long description of package. --output | -o output-file
    Write to <output-file> instead of ./metadata.xml --force | -f
    Force overwrite of existing metadata --verbose | -v
    Write to stdout as well as disk (default) --quiet | -q
    Don't write to stdout -Q
    Don't write file to disk --help | -h
    show usage help and exit --version
    show version and exit

EXAMPLES
metagen -e pythonhead@gentoo.org -n 'Joe Blow' -d 'The voices in my head told me to maintain this package' -Q maintainer email, maintainer name, description of maintainership, to stdout only metagen -e jo@gentoo.org,flo@gentoo.org -n 'Jo Blo','Flo Blo' -d 'I am maintaining this because foo','I am maintaining this because bar' -l 'This package is yadda yadda yadda, spam and eggs' -Q 2 maintainers with names and maintainer descriptions for each maintainer, only write to stdout

FILES

/usr/bin/metagen /usr/share/man/man1/metagen.1.gz

BUGS
No known bugs at this time.

AUTHOR
Rob 'pythonhead' Cakebread (pythonhead@gentoo.org)
Jesus Rivero (neurogeek@gentoo.org)

HISTORY
2004 - Initial revision