From owner-freebsd-java Wed Dec 30 16:06:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20677 for freebsd-java-outgoing; Wed, 30 Dec 1998 16:06:35 -0800 (PST) (envelope-from owner-freebsd-java@FreeBSD.ORG) Received: from fever.semiotek.com (host-062.canadiantire.ca [209.146.201.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20661; Wed, 30 Dec 1998 16:06:33 -0800 (PST) (envelope-from reader@fever.semiotek.com) Received: (from reader@localhost) by fever.semiotek.com (8.8.8/8.8.7) id TAA04896; Wed, 30 Dec 1998 19:06:01 -0500 (EST) (envelope-from reader) Message-ID: <19981230190601.A4424@semiotek.com> Date: Wed, 30 Dec 1998 19:06:01 -0500 From: Justin Wells To: Palle Girgensohn , freebsd-java@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Porting java stuff? Proposal? Mail-Followup-To: Palle Girgensohn , freebsd-java@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG References: <3689A1DB.3B844BF@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <3689A1DB.3B844BF@partitur.se>; from Palle Girgensohn on Wed, Dec 30, 1998 at 04:45:31AM +0100 Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My two cents on the porting issue: Nate is right, there are likely to be multiple versions of Java on any system. The most important differences, though, are the version-of-java differences. Most applications won't care whether their JVM is a JIT, ELF, or what type of thread library it uses. Some will, but not most. I think that means: -- Versions of Java should be installed as /usr/local/jdk.x.y.z -- The most featureful, newest version of Java should be symlinked so that it appears under /usr/local/java, and this should change regularly as Java is upgraded. A port should check if it is highest version of Java installed so far, and if so, symlink /usr/local/java to itself. -- Eventually, the most stable, reliable, and trusted version of Java should appear as /usr/java: whenever it is that the FreeBSD community finds Java useful enough to use for some core functionality. This won't exist for some time, but it's eventual existence justifies the notion that /usr/local/java is the most recent. If you want the most stable, that would be /usr/java--and if /usr/java doesn't exist, that's because there is not yet a version worthy of the "stable" designation. -- People choose what JVM to use by default by setting their CLASSPATH and PATH to reflect their choice. Just because /usr/java and /usr/local/java exist doesn't mean you HAVE to use them -- Core/critical applications would rely on /usr/java. Most userland applications should try and use /usr/local/java. Individual applications that are known not to work with the most recent version of Java should instead rely on the last specific version of Java with which they do work. All other issues, such as what thread library to use, whether to use ELF or a.out, should not be solved using the filesystem layout. Instead they should be determined by the port maintainer, or selected by an environment variable (either during install, or at runtime). Since I'm not doing any of the work, feel free to ignore me. However I have an application I'd like to write a PORT for (webmacro: www.webmacro.org) and without a good underlying JDK port I can't do that :-) Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message