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

diff --git a/app-emacs/ecb/metadata.xml b/app-emacs/ecb/metadata.xml
new file mode 100644
index 000000000000..4858374f9d5b
--- /dev/null
+++ b/app-emacs/ecb/metadata.xml
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+<herd>emacs</herd>
+<longdescription>
+  ECB stands for "Emacs Code Browser". While Emacs already has good editing
+  support for many modes, its browsing support is somewhat lacking. That's
+  where ECB comes in: it displays a number of informational windows that allow
+  for easy source code navigation and overview.
+
+  The informational windows can contain:
+
+    * A directory tree,
+    * a list of source files in the current directory,
+    * a list of functions/classes/methods/... in the current file, (ECB uses
+      the Semantic Bovinator, or Imenu, or etags, for getting this list so all
+      languages supported by any of these tools are automatically supported by
+      ECB too),
+    * a history of recently visited files,
+    * the Speedbar and
+    * output from compilation (the compilation window) and other modes like
+      help, grep etc. or whatever a user defines to be displayed in this
+      window.
+
+  As an added bonus, ECB makes sure to keep these informational windows
+  visible, even when you use C-x 1 and similar commands.
+
+  It goes without saying that you can configure the layout, ie. which
+  informational windows should be displayed where. ECB comes with a number of
+  ready-made window layouts to choose from.
+</longdescription>
+</pkgmetadata>