Hi, Find attached the Ebuild Script for Apache-forrest. Forrest is an XML standards-oriented project documentation framework based on Apache Cocoon, providing XSLT stylesheets and schemas, images and other resources. Forrest uses these to render the XML source content into a website via command-line, robot, or a dynamic web application. Forrest requires a Java development kit and java runtime environment to be installed, >= 1.2. This Ebuild has been tested against Blackdown JDK 1.4.1. This Ebuild is my first Ebuild, and it should be tested (installed) by people who know what they are doing before it is merged in the Portage tree. It installs into /usr/local. It does not yet adjust the path to FORREST_HOME/bin where FORREST_HOME is presently /usr/local/forrest, as I don't know how to do that. Testing requires these variables to be set. A simple test is then to create a new directory, and cd into there. Then type forrest seed; forrest validate and then forrest. forrest -projecthelp gives more help. I would very much like comments and (suggestions for) improvements. I would especially appreciate a pointer on how to set FORREST_HOME/bin to the default user path. Leon Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 25587 [details] forrest-0.5.1.ebuild new Ebuild file, new Package This is the Ebuild file for Apache-forrest. This Ebuild file should be tested before emerging into the Portage tree. I suggest to place this package in net-www, which is were cocoon is found (and forrest incorporates parts of cocoon).
Probably best for our java team to look at this one. Best regards, Stu
Created attachment 31494 [details, diff] ebuild patch Hi Leon, I have made some changes to your ebuild. I will try to describe what I changed and why I did so: 1) removed javac from the IUSE variable as the ebuild does not use it. 2) split up the DEPEND variable into RDEPEND and DEPEND, as I'm quite confident that forrest doesn't need jdk when it is installed. Please correct me if I'm wrong :) 3) changed the installation destination from /usr/local to /usr/share as it seems this is the common location in Gentoo Linux. In addition, now a) build.sh installs directly into $D. b) forrest-bin directory is added to global PATH. c) forrest release notes is added during install. There is a section in the handbook about global variables: http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&chap=6#doc_chap2 By the way, I'm using sun-jdk-1.4.2.04. regards, Thomas
forgot to mention: In its current version the "forrest" script needs to be placed inside the forrest installation, so it is not possible to move or symlink the script into e.g. /usr/bin. This is why I added the forrest-bin directory to the global PATH. I haven't tested the forrest-bot script.
*** Bug 64650 has been marked as a duplicate of this bug. ***
I've looked at this ebuild finally, and can see the following problems that need to be fixed before it's included: 1) The SRC_URI is wrong. The source drop no longer exists upstream. In fact, I can't find any source drops from this project anymore. They must resume releasing source tarballs before we can include it. 2) MYDIR must go. Use a local env var in src_install instead. 3) All bundled .jar files must be replaced with our own packages, using the java-pkg_jar-from, or a build.properties file. 4) All compiled .jar files must be installed using java_pkg-dojar 5) The 'forrest' script should be patched so that it can be installed in /usr/bin 6) The JRE/JDK dependences must probably be updated to 1.3 or 1.4, for the 1.6 (most recent) forrest release. We don't have the time to fix this at the present time, but if any kind benefactor wants to help out, please submit and updated ebuild, and we'll include it ASAP. Closing as REMIND so that it'll show up on the orphaned ebuilds list in the wiki.
Upstream now only releases complete bundles with source, documentation and pre-built code. It seems silly to have to download the pre-built code in order to get the source code, but if it's not very big, I think we can live with it.
