Landon, Here is my advise.
1. Take the OJ nightly build and manually make the changes to create a debian install. Writing down each step 2. Create a ant build script to take a nightly build following those steps to automatically create a debian install 3. Run this daily against the nightly build to create a debian nightly build Paul Sunburned Surveyor wrote: > Larry, > > You can still use the Nightly Build of OJ on Debian, you just can't > install it as part of the traditional Debian Package Management > System. There are other programs that are like that. For example, I > like to use the latest version of Netbeans and Eclipse. There is no > Deb for Netbeans, and the package for Eclipse is always a couple of > version behind the official release you can download online. I keep a > /home/myuser/programs where I can install "unofficial" programs like > these. > > I do the same thing with OpenJUMP, and others can to. I'll try to get > a working package of OpenJUMP put together. It will work in the > package management system, but might not be included in the official > Debian repository. > > Landon > > On Nov 9, 2007 11:33 AM, Larry Becker <[EMAIL PROTECTED]> wrote: > >> Hi SS, >> >> Thanks for the good work. I guess Debian users won't be able to load the >> nightly build unless they treat it as a separate application, or spend some >> time moving all of the files to their proper locations. >> >> Larry >> >> >> >> On Nov 9, 2007 11:14 AM, Sunburned Surveyor <[EMAIL PROTECTED]> >> wrote: >> >>> >>> I got some feedback on the Debian Package for OpenJUMP from some other >>> Debian Package Maintainers. It looks like the JAR containing the main >>> method that launches JUMP will need to be stored in /usr/bin/openjump. >>> This will also be the location where the launch script is stored. It >>> will be O.K. to configure the classpath for JUMP in the launch script >>> as we do currently. (Perhaps this is no longer needed know that the >>> classpath is specified in the Manifest.) >>> >>> I was advised that the proper place for plug-in Jars is >>> /usr/share/openjump or /usr/share/java/openjump. However, I don't >>> think this will work without some modifications to OpenJUMP. We'd have >>> to change where OpenJUMP looks for Extension JAR files. We'd also have >>> to find a hack for plug-ins that use relative paths. This will be a >>> real pain-in-the-butt for plug-ins that can't embedd all of the >>> supporting files they need into their JAR. I really think the only way >>> to accomplish these mods would be in a Debian specific build of >>> OpenJUMP. I'm all for supporting the Debian packaging policy, but not >>> if it means this level of effort. It sort of kills the benefit of >>> cross-platform development. >>> >>> If someone has an alternative to a separate Debian build then I will >>> consider keeping the plug-in jars in /usr/share/openjump or >>> /usr/share/java/openjump. Otherwise I will be placing them in a sub >>> folder of the /usr/bin/openjump directory. >>> >>> I will be extracting common libraries like JTS and Bouy. I'll prepare >>> separate Debian packages for these, if they don't already exist. They >>> will be stored in /usr/share/java. This means other Java programs will >>> be able to use the Debian packages we prepare for common libraries >>> used by OpenJUMP. That is one benefit of the Debian system. >>> >>> Another benefit is that we can prepare separate Debian packages for >>> popular plug-ins. When these are installed using a graphical tool like >>> Synaptic ( http://www.nongnu.org/synaptic/action.html ) eveything will >>> fall into its proper place with no moving files by the user required! >>> >>> I'll see if I can get time to work on the OpenJUMP Debian Package this >>> >> weekend. >> >>> The Sunburned Surveyor >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Splunk Inc. >>> Still grepping through log files to find problems? Stop. >>> Now Search log events and configuration files using AJAX and a browser. >>> Download your FREE copy of Splunk now >> http://get.splunk.com/ >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> Jump-pilot-devel@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >> >> -- >> http://amusingprogrammer.blogspot.com/ >> ------------------------------------------------------------------------- >> This SF.net email is sponsored by: Splunk Inc. >> Still grepping through log files to find problems? Stop. >> Now Search log events and configuration files using AJAX and a browser. >> Download your FREE copy of Splunk now >> http://get.splunk.com/ >> _______________________________________________ >> Jump-pilot-devel mailing list >> Jump-pilot-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >> >> >> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Jump-pilot-devel mailing list > Jump-pilot-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Jump-pilot-devel mailing list Jump-pilot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
