From owner-freebsd-ports  Wed May 23 15:32: 9 2001
Delivered-To: freebsd-ports@freebsd.org
Received: from dargo.talarian.com (dargo.talarian.com [207.5.33.3])
	by hub.freebsd.org (Postfix) with ESMTP id 2412637B424
	for <ports@freebsd.org>; Wed, 23 May 2001 15:32:05 -0700 (PDT)
	(envelope-from nsayer@quack.kfu.com)
Received: from moya.talarian.com (moya.talarian.com [10.4.10.8])
	by dargo.talarian.com (Postfix) with ESMTP id 4763422B0E
	for <ports@freebsd.org>; Wed, 23 May 2001 15:27:35 -0700 (PDT)
Received: from beast.talarian.com (beast.talarian.com [10.4.10.6])
	by moya.talarian.com (Postfix) with ESMTP id 50FFF35
	for <ports@freebsd.org>; Wed, 23 May 2001 15:32:03 -0700 (PDT)
Received: from quack.kfu.com (localhost [127.0.0.1])
	by beast.talarian.com (8.11.3/8.11.3) with ESMTP id f4NMW3711286
	for <ports@freebsd.org>; Wed, 23 May 2001 15:32:03 -0700 (PDT)
	(envelope-from nsayer@quack.kfu.com)
Message-ID: <3B0C3A63.3020908@quack.kfu.com>
Date: Wed, 23 May 2001 15:32:03 -0700
From: Nick Sayer <nsayer@quack.kfu.com>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.3-RELEASE i386; en-US; 0.8.1) Gecko/20010411
X-Accept-Language: en
MIME-Version: 1.0
To: ports@freebsd.org
Subject: Java port behavior ideas
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-ports.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-ports>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-ports>
X-Loop: FreeBSD.org

We're starting to get a number of ports that consist simply of .jar 
files. Each one is currently taking a different approach to how they are 
installed and run and stuff.

I'd like to suggest some additional standards and port plumbing to 
handle this.

1. 'javavm' should take a flag that will do for "old" JREs what the -jar 
flag does. Perhaps this should be a new script in the javavmwrapper port 
called 'runjar' or something like that. Ideally, IMHO, 'javavm -jar 
[jarfile]' should always be sufficient regardless of what JRE is in use. 
Of course, I leave it to the javavmwrapper maintainer(s) to actually do 
this. :-)

2. .jar files should, IMHO, go in a common spot. ${PREFIX}/share/java 
seems quite reasonable.

3. IS_JAR=yes would be a nice short-hand for having a RUN_DEPENDS of 
javavmwrapper and a JRE and NO_BUILD=yes.

4. Most ambitously, it's conceivable that a method could be devised to 
automatically make links from a javavmwrapper helper script to 
${PREFIX}/bin/jarname. The helper script would be argv[0] aware and 
would do the equivalent of 'javavm -jar ${PREFIX}/share/java/$0.jar'.
This could be used in port Makefiles in a manner similar to MANn= lines.

Just some ideas to kick around.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message