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

diff --git a/licenses/RASLIC b/licenses/RASLIC
new file mode 100644
index 00000000000..eac150132f6
--- /dev/null
+++ b/licenses/RASLIC
@@ -0,0 +1,59 @@
+
+Creative endeavors depend on the lively exchange of ideas. There are laws
+and customs which establish rights and responsibilities for authors and the
+users of what authors create. This notice is not intended to prevent you
+from using the software and documents in this package, but to ensure that
+there are no misunderstandings about terms and conditions of such use.
+
+Please read the following notice carefully. If you do not understand any
+portion of this notice, please seek appropriate professional legal advice
+before making use of the software and documents included in this software
+package. In addition to whatever other steps you may be obliged to take to
+respect the intellectual property rights of the various parties involved, if
+you do make use of the software and documents in this package, please give
+credit where credit is due by citing this package, its authors and the URL
+or other source from which you obtained it, or equivalent primary references
+in the literature with the same authors.
+
+Some of the software and documents included within this software package are
+the intellectual property of various parties, and placement in this package
+does not in any way imply that any such rights have in any way been waived
+or diminished.
+
+With respect to any software or documents for which a copyright exists, ALL
+RIGHTS ARE RESERVED TO THE OWNERS OF SUCH COPYRIGHT.
+
+Even though the authors of the various documents and software found here
+have made a good faith effort to ensure that the documents are correct and
+that the software performs according to its documentation, and we would
+greatly appreciate hearing of any problems you may encounter, the programs
+and documents any files created by the programs are provided **AS IS**
+without any warranty as to correctness, merchantability or fitness for any
+particular or general use.
+
+THE RESPONSIBILITY FOR ANY ADVERSE CONSEQUENCES FROM THE USE OF PROGRAMS OR
+DOCUMENTS OR ANY FILE OR FILES CREATED BY USE OF THE PROGRAMS OR DOCUMENTS
+LIES SOLELY WITH THE USERS OF THE PROGRAMS OR DOCUMENTS OR FILE OR FILES AND
+NOT WITH AUTHORS OF THE PROGRAMS OR DOCUMENTS.
+
+Subject to your acceptance of the conditions stated above, and your respect
+for the terms and conditions stated in the notices below, if you are not
+going to make any modifications or create derived works, you are given
+permission to freely copy and distribute this package, provided you do the
+following:
+
+   * 1. Either include the complete documentation, especially the file
+     NOTICE, with what you distribute or provide a clear indication where
+     people can get a copy of the documentation; and
+   * 2. Give credit where credit is due citing the version and original
+     authors properly; and
+   * 3. Do not give anyone the impression that the original authors are
+     providing a warranty of any kind.
+
+In addition, you may also modify this package and create derived works
+provided you do the following:
+
+   * 4. Explain in your documentation how what you did differs from this
+     version of RasMol; and
+   * 5. Make your modified source code available.
+