reinit the tree, so we can have metadata

3 files changed, 98 insertions, 0 deletions

diff --git a/dev-java/jacl/Manifest b/dev-java/jacl/Manifest
new file mode 100644
index 000000000000..9237b23500b3
--- /dev/null
+++ b/dev-java/jacl/Manifest
@@ -0,0 +1,5 @@
+DIST jacl-1.4.1.tar.gz 1921630 SHA256 0edac0a7d2253c29c44ccc92427fa9ad4ee81b6c82142e417f72399a8584b749 SHA512 e4b906efbd3ef4ab9338e8bf2f50c3b820e25b9fbe61f194e90cc0fa128f68d64eb459f7b05171d4b86b4c9635ef483906a02952bdedcee89ccb92256b789247 WHIRLPOOL d40416577c88403a34b3f4c2c7ba45365330690832d4f7c4013a4c17b3ae2e589e99a9d7c8a93d18b4690fdefad1e3298dd28b3b89a467b8dcf2138e3e3b58cf
+EBUILD jacl-1.4.1-r1.ebuild 975 SHA256 3be8ffdcaff7a25e94476b8c7d1d55234abae7778c76070c0e5f655ff16b8af8 SHA512 7114f0f2d99e2a06b58eb5f0b9443e69baaeed5fb81ec7ac1c42a3915db12ba773903536677cdae93aa8a956b87911b8d08291ab9fb4087bcc651d005e0aa4eb WHIRLPOOL fa1beecb81bb3c4446583e436eca3a51ac23e7d626f2e2dd96d1056a77f71ea6c17b64ceddd3bfdf047572a11003dfc50b22be987b5f91f5f2c5bd7e7f24b9e4
+MISC ChangeLog 3572 SHA256 b599992e3059c2e845c5b89bbd86e7c8c106b059be4d0337ab11f479ca9e65c3 SHA512 36b19ed3cdd1b9eda5e19836fa36596d64da41ae15718be96c2ab9aa5f5d52a4361bcb88672db98c5b38ca313a58570d8312594e1a5b0c0d3ebda1a0787b79ff WHIRLPOOL f28d190f35820261b3d7c311d4f218a81ee256aac7d60e3ddc214ada0a7ba029ea9e892542188787144f1acda5dd756ed12a16a8fa164fc0323c2c59227decc1
+MISC ChangeLog-2015 3766 SHA256 cafa0c97efc434a519aa80dd0f407bb52882aee4318e4da62376e5be71e4298e SHA512 07652bf2fd3cff44ec0750a02839fbeba9675cfeefe2ad1fe5d481792ade46677b5b050883578247f33c02152fe75fa5bcdf758e78d8fcaf9e37787914e569be WHIRLPOOL dcbb8c347963dba8be612209fcf67c10b4a594edeae25a96c26b44e12d8235773262eabdc12c8aab3b447d8f4720fb6c80cb17c8ccfae63dd8c9a8698aba053d
+MISC metadata.xml 2116 SHA256 e6456fe3f69a0b874239c1450ba8e354a311cedd280a9d5f34cf2f8e1986ebd6 SHA512 221bd082cf7a036c0417d003a216bd919f8d6391211da62abaf57c560f192bbe27dba23c260a4d731e09e46dd0e30b4a185a45ccf7375908b947667bf5df7966 WHIRLPOOL d51a5381a29273b216abdd1c56199a7c5aeab6313e53b5892c32fcb4180b0fd7475ff826c7e400800c7c0a63415e426903dac4a1c78ec3302c54086393f56b49
diff --git a/dev-java/jacl/jacl-1.4.1-r1.ebuild b/dev-java/jacl/jacl-1.4.1-r1.ebuild
new file mode 100644
index 000000000000..2a090c5d697a
--- /dev/null
+++ b/dev-java/jacl/jacl-1.4.1-r1.ebuild
@@ -0,0 +1,52 @@
+# Copyright 1999-2016 Gentoo Foundation
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=5
+JAVA_PKG_IUSE="doc source"
+
+inherit java-pkg-2 java-pkg-simple
+
+MY_P="${P//-}"
+
+DESCRIPTION="Jacl is an implementation of Tcl written in Java"
+HOMEPAGE="http://tcljava.sourceforge.net"
+SRC_URI="mirror://sourceforge/tcljava/${MY_P}.tar.gz -> ${P}.tar.gz"
+LICENSE="BSD"
+SLOT="0"
+KEYWORDS="amd64 ppc64 x86"
+IUSE="doc"
+
+CDEPEND=">=dev-lang/tcl-8.4.5:*"
+
+RDEPEND="
+	${CDEPEND}
+	>=virtual/jre-1.6"
+
+DEPEND="
+	${CRDEPEND}
+	>=virtual/jdk-1.6"
+
+S="${WORKDIR}/${MY_P}"
+
+JAVA_SRC_DIR="src"
+
+java_prepare() {
+	java-pkg_clean
+}
+
+src_configure() {
+	:
+}
+
+src_compile() {
+	rm -rf src/{Test.java,empty,tests,janino} || die
+	java-pkg-simple_src_compile
+	mv src/jacl/tcl src/ || die
+	java-pkg_addres "${PN}.jar" src/ -name "*.tcl"
+}
+
+src_install() {
+	java-pkg-simple_src_install
+	java-pkg_dolauncher jaclsh --main tcl.lang.Shell
+	dodoc README ChangeLog known_issues.txt || die
+}
diff --git a/dev-java/jacl/metadata.xml b/dev-java/jacl/metadata.xml
new file mode 100644
index 000000000000..3b8f63c2a9f6
--- /dev/null
+++ b/dev-java/jacl/metadata.xml
@@ -0,0 +1,41 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+	<maintainer type="project">
+		<email>java@gentoo.org</email>
+		<name>Java</name>
+	</maintainer>
+	<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>