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

5 files changed, 165 insertions, 0 deletions

diff --git a/dev-java/jacl/Manifest b/dev-java/jacl/Manifest
new file mode 100644
index 000000000000..299e6721ca74
--- /dev/null
+++ b/dev-java/jacl/Manifest
@@ -0,0 +1 @@
+DIST jacl1.4.1.tar.gz 1921630 SHA256 0edac0a7d2253c29c44ccc92427fa9ad4ee81b6c82142e417f72399a8584b749 SHA512 e4b906efbd3ef4ab9338e8bf2f50c3b820e25b9fbe61f194e90cc0fa128f68d64eb459f7b05171d4b86b4c9635ef483906a02952bdedcee89ccb92256b789247 WHIRLPOOL d40416577c88403a34b3f4c2c7ba45365330690832d4f7c4013a4c17b3ae2e589e99a9d7c8a93d18b4690fdefad1e3298dd28b3b89a467b8dcf2138e3e3b58cf
diff --git a/dev-java/jacl/files/1.3.3-javacflags.patch b/dev-java/jacl/files/1.3.3-javacflags.patch
new file mode 100644
index 000000000000..600cabc2b7e8
--- /dev/null
+++ b/dev-java/jacl/files/1.3.3-javacflags.patch
@@ -0,0 +1,36 @@
+Index: Makefile.in
+===================================================================
+RCS file: /cvsroot/tcljava/tcljava/Makefile.in,v
+retrieving revision 1.60
+diff -u -r1.60 Makefile.in
+--- Makefile.in	5 Aug 2006 01:50:11 -0000	1.60
++++ Makefile.in	3 Apr 2007 08:51:22 -0000
+@@ -54,7 +54,7 @@
+ XTERM			= xterm
+ JAVA_FLAGS		= @JAVA_FLAGS@
+ JAVA_G_FLAGS		= @JAVA_G_FLAGS@
+-JAVAC_FLAGS		= @JAVAC_FLAGS@
++JAVAC_FLAGS		?= @JAVAC_FLAGS@
+ JAVAC_D_FLAG		= @JAVAC_D_FLAG@
+ JAR_EXTRACT_FLAGS	= @JAR_EXTRACT_FLAGS@
+ JAR_COMPRESS_FLAGS	= @JAR_COMPRESS_FLAGS@
+Index: tcljava.m4
+===================================================================
+RCS file: /cvsroot/tcljava/tcljava/tcljava.m4,v
+retrieving revision 1.35
+diff -u -r1.35 tcljava.m4
+--- tcljava.m4	21 Aug 2006 22:26:37 -0000	1.35
++++ tcljava.m4	3 Apr 2007 08:51:28 -0000
+@@ -226,9 +226,9 @@
+     # Look for a setting for the CLASSPATH, we might need one to run JAVAC
+     AC_JAVA_CLASSPATH
+ 
+-    # FIXME : add detection of command line arguments for JAVAC
+-
+-    JAVAC_FLAGS=-g
++    if test "x${JAVAC_FLAGS}" = "x"; then
++        JAVAC_FLAGS=-g
++    fi
+     JAVAC_D_FLAG=-d
+ 
+     dnl Test out the Java compiler with an empty class
diff --git a/dev-java/jacl/files/jacl-1.4.1-build.patch b/dev-java/jacl/files/jacl-1.4.1-build.patch
new file mode 100644
index 000000000000..5f2ccf946492
--- /dev/null
+++ b/dev-java/jacl/files/jacl-1.4.1-build.patch
@@ -0,0 +1,39 @@
+diff -Naur jacl1.4.1.bak/Makefile.in jacl1.4.1/Makefile.in
+--- jacl1.4.1.bak/Makefile.in	2008-09-14 14:44:18.000000000 +1200
++++ jacl1.4.1/Makefile.in	2008-09-14 14:46:31.000000000 +1200
+@@ -54,7 +54,7 @@
+ XTERM			= xterm
+ JAVA_FLAGS		= @JAVA_FLAGS@
+ JAVA_G_FLAGS		= @JAVA_G_FLAGS@
+-JAVAC_FLAGS		= @JAVAC_FLAGS@
++JAVAC_FLAGS		?= @JAVAC_FLAGS@
+ JAVAC_D_FLAG		= @JAVAC_D_FLAG@
+ JAR_EXTRACT_FLAGS	= @JAR_EXTRACT_FLAGS@
+ JAR_COMPRESS_FLAGS	= @JAR_COMPRESS_FLAGS@
+@@ -983,8 +983,8 @@
+ 	$(JAVAC) $(JAVAC_FLAGS) \
+ 	$(JAVAC_D_FLAG) $(TCLJAVA_BUILD_DIR) \
+ 		tcl/lang/*.java
+-	mkdir $(TCLJAVA_BUILD_DIR)/tcl/lang/library
+-	mkdir $(TCLJAVA_BUILD_DIR)/tcl/lang/library/java
++	mkdir -p $(TCLJAVA_BUILD_DIR)/tcl/lang/library
++	mkdir -p $(TCLJAVA_BUILD_DIR)/tcl/lang/library/java
+ 	cp -fr $(TCLJAVA_SRC_DIR)/tcl/lang/library/java/*.tcl \
+ 		$(TCLJAVA_BUILD_DIR)/tcl/lang/library/java
+ 
+diff -Naur jacl1.4.1.bak/tcljava.m4 jacl1.4.1/tcljava.m4
+--- jacl1.4.1.bak/tcljava.m4	2008-09-14 14:44:18.000000000 +1200
++++ jacl1.4.1/tcljava.m4	2008-09-14 14:44:30.000000000 +1200
+@@ -226,9 +226,9 @@
+     # Look for a setting for the CLASSPATH, we might need one to run JAVAC
+     AC_JAVA_CLASSPATH
+ 
+-    # FIXME : add detection of command line arguments for JAVAC
+-
+-    JAVAC_FLAGS=-g
++    if test "x${JAVAC_FLAGS}" = "x"; then
++        JAVAC_FLAGS=-g
++    fi
+     JAVAC_D_FLAG=-d
+ 
+     dnl Test out the Java compiler with an empty class
diff --git a/dev-java/jacl/jacl-1.4.1.ebuild b/dev-java/jacl/jacl-1.4.1.ebuild
new file mode 100644
index 000000000000..983cee4b4928
--- /dev/null
+++ b/dev-java/jacl/jacl-1.4.1.ebuild
@@ -0,0 +1,51 @@
+# Copyright 1999-2014 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+# $Id$
+
+inherit base java-pkg-2
+
+DESCRIPTION="Jacl is an implementation of Tcl written in Java"
+HOMEPAGE="http://tcljava.sourceforge.net"
+MY_P="${P//-}"
+SRC_URI="mirror://sourceforge/tcljava/${MY_P}.tar.gz"
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="amd64 ppc ppc64 x86 ~x86-fbsd"
+IUSE="doc"
+
+RDEPEND=">=dev-lang/tcl-8.4.5
+	>=virtual/jre-1.4"
+DEPEND=">=virtual/jdk-1.4
+	${RDEPEND}"
+
+S=${WORKDIR}/${MY_P}
+
+PATCHES=( "${FILESDIR}/${P}-build.patch" )
+
+# jikes support disabled for now.
+# refer to bug #100020 and bug #89711
+
+src_compile() {
+	local jflags="$(java-pkg_javac-args)"
+	JAVAC_FLAGS="${jflags}" \
+		econf --enable-jacl --without-jikes || die
+	#ali_bush: Fails intermitently with MAKEOPTS="-j3"
+	JAVAC_FLAGS="${jflags}" \
+		emake -j1 DESTDIR="/usr/share/${PN}" || die "emake failed"
+}
+
+RESTRICT="test"
+# Dies with anything else besides 1.4 so more trouble than benefit
+src_test() {
+	emake check || die "Tests failed"
+	einfo "Some tests are known to fail. We didn't restrict them"
+	einfo "because the ebuild doesn't die."
+}
+
+src_install() {
+	#emake DESTDIR="${D}" install || die "emake install failed"
+	java-pkg_dojar *.jar
+	java-pkg_dolauncher jaclsh --main tcl.lang.Shell
+	dodoc README ChangeLog known_issues.txt || die
+	use doc && java-pkg_dohtml -r docs/*
+}
diff --git a/dev-java/jacl/metadata.xml b/dev-java/jacl/metadata.xml
new file mode 100644
index 000000000000..6b283ec84313
--- /dev/null
+++ b/dev-java/jacl/metadata.xml
@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+	<herd>java</herd>
+	<longdescription>
+The Tcl/Java project's goal is to make integrating the Java platform and the
+Tcl scripting language as easy as possible. The project actually consists of
+two distinct packages, called Tcl Blend and Jacl. It is important to
+understand what each package provides and in what situations one might choose
+to use Jacl or Tcl Blend.
+
+Tcl Blend is a Tcl extension that makes use of JNI to facilitate communication
+between a Java interpreter and a Tcl interpreter. Tcl Blend is typically used
+to load a Java interpreter into an existing Tcl process, so that functionality
+implemented in Java can be accessed via Tcl. One can also load Tcl Blend and
+Tcl into a Java process, which is a great way to add scripting functionality
+to an existing Java application. Because Tcl Blend is a normal Tcl extension,
+one can use it with other popular Tcl extensions like Tk, Expect, and Itcl.
+
+Jacl is a self-contained implementation of a Tcl interpreter, written entirely
+in Java. Jacl also includes features that facilitate communication between a
+Java interpreter and a Tcl interpreter. Jacl is typically used to incorporate
+scripting functionality into an existing Java application. For users who want
+to avoid adding any native code to their Java applications, Jacl is the ideal
+solution.
+
+Tcl Blend and Jacl define both a Tcl API and a Java API that make it easy to
+call Java code from Tcl or call Tcl code from Java. For example, one could
+allocate a Java object in a Tcl script and interactively invoke Java methods
+on the object. It is also easy to use the supplied API to evaluate a Tcl
+procedure from a Java method or implement Tcl procudures in Java. The flexible
+API and wealth of implementation options provided by the Tcl/Java project make
+integrating Tcl and Java easy.
+</longdescription>
+	<upstream>
+		<remote-id type="sourceforge">tcljava</remote-id>
+	</upstream>
+</pkgmetadata>