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, 30 insertions, 0 deletions

diff --git a/dev-python/etsdevtools/metadata.xml b/dev-python/etsdevtools/metadata.xml
new file mode 100644
index 000000000000..c89897249522
--- /dev/null
+++ b/dev-python/etsdevtools/metadata.xml
@@ -0,0 +1,30 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+  <herd>python</herd>
+  <longdescription lang="en">
+    The ETSDevTools project from the Enthought Tool Suite includes a
+    set of packages that can be used during the development of a
+    software project, for understanding, debugging, testing, and
+    inspecting code: 
+    * Enthought Developer Tool Suite (enthought.developer): A
+      collection of utilities, designed to ease the development and
+      debugging of Traits-based programs. They can be used as plug-ins
+      to your Envisage application while you are developing it, and then
+      removed when you are ready to release it.
+    * Endo: A Traits-aware tool for processing API documentation of
+      Python code. It extracts not only docstrings, but also plain
+      comments that immediately precede variable assignments (both
+      module-scope variables and class attributes).
+    * enthought.guitest: A collection of utilities for unit testing
+      user interfaces (translation of the Perl X11::GUITest and
+      Win32::GuiTest modules).
+    * enthought.testing: Scripts related to running unit tests, based
+      on testoob, and also allowing running test suites in separate
+      processes and aggregating the results.
+    * enthought.debug: A collection of debugging tools, not to be
+      included in production code. NOTE: These tools are functional, but
+      are not being developed or supported. They have been mainly
+      superceded by the tools in the Enthought Developer Tool Suite.
+  </longdescription>
+</pkgmetadata>