proj/gentoo: Initial commit

This commit represents a new era for Gentoo:
Storing the gentoo-x86 tree in Git, as converted from CVS.

This commit is the start of the NEW history.
Any historical data is intended to be grafted onto this point.

Creation process:
1. Take final CVS checkout snapshot
2. Remove ALL ChangeLog* files
3. Transform all Manifests to thin
4. Remove empty Manifests
5. Convert all stale $Header$/$Id$ CVS keywords to non-expanded Git $Id$
5.1. Do not touch files with -kb/-ko keyword flags.

Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
X-Thanks: Alec Warner <antarus@gentoo.org> - did the GSoC 2006 migration tests
X-Thanks: Robin H. Johnson <robbat2@gentoo.org> - infra guy, herding this project
X-Thanks: Nguyen Thai Ngoc Duy <pclouds@gentoo.org> - Former Gentoo developer, wrote Git features for the migration
X-Thanks: Brian Harring <ferringb@gentoo.org> - wrote much python to improve cvs2svn
X-Thanks: Rich Freeman <rich0@gentoo.org> - validation scripts
X-Thanks: Patrick Lauer <patrick@gentoo.org> - Gentoo dev, running new 2014 work in migration
X-Thanks: Michał Górny <mgorny@gentoo.org> - scripts, QA, nagging
X-Thanks: All of other Gentoo developers - many ideas and lots of paint on the bikeshed

1 files changed, 43 insertions, 0 deletions

diff --git a/app-admin/salt/metadata.xml b/app-admin/salt/metadata.xml
new file mode 100644
index 000000000000..7b86f458a6ae
--- /dev/null
+++ b/app-admin/salt/metadata.xml
@@ -0,0 +1,43 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+  <maintainer>
+    <email>chutzpah@gentoo.org</email>
+    <name>Patrick McLean</name>
+  </maintainer>
+  <longdescription lang="en">
+Salt is a powerful remote execution manager that can be used to administer
+servers in a fast and efficient way.
+
+Salt allows commands to be executed across large groups of servers. This means
+systems can be easily managed, but data can also be easily gathered. Quick
+introspection into running systems becomes a reality.
+
+Remote execution is usually used to set up a certain state on a remote system.
+Salt addresses this problem as well, the salt state system uses salt state
+files to define the state a server needs to be in.
+
+Between the remote execution system, and state management Salt addresses the
+backbone of cloud and data center management.
+</longdescription>
+  <use>
+    <flag name="api">Enable support for salt-api.</flag>
+    <flag name="cherrypy">Enable support for using cherrypy.</flag>
+    <flag name="libcloud">Enable salt-cloud support via libcloud.</flag>
+    <flag name="libvirt">Support managing virtual machines with app-emulation/libvirt.</flag>
+    <flag name="gnupg">Enable support for gnupg via python-gnupg.</flag>
+    <flag name="keyring">Enable support for keyrings via python-keyring.</flag>
+    <flag name="mako">Add support for using the mako template engine for parsing salt states.</flag>
+    <flag name="mongodb">Support returning data to a mongodb server.</flag>
+    <flag name="neutron">Support the OpenStack neutron network service.</flag>
+    <flag name="nova">Enable support for the OpenStack Nova API</flag>
+    <flag name="openssl">Add support for using TLS via OpenSSL.</flag>
+    <flag name="raet">Add support for the new RAET transport.</flag>
+    <flag name="redis">Support returning data to a redis database.</flag>
+    <flag name="timelib">Use timelib to parse english textual date descriptions.</flag>
+    <flag name="zeromq">Add support for the zeromq transport.</flag>
+  </use>
+  <upstream>
+    <remote-id type="pypi">salt</remote-id>
+  </upstream>
+</pkgmetadata>