From owner-freebsd-java Thu May 24 12:13:10 2001 Delivered-To: freebsd-java@freebsd.org Received: from kalaid.f2f.com.ua (kalaid.f2f.com.ua [62.149.0.33]) by hub.freebsd.org (Postfix) with ESMTP id 6CF4237B423 for ; Thu, 24 May 2001 12:12:45 -0700 (PDT) (envelope-from sobomax@mail-in.net) Received: from mail.uic-in.net (root@[212.35.189.4]) by kalaid.f2f.com.ua (8.11.3/8.11.1) with ESMTP id f4OJEOa59167; Thu, 24 May 2001 22:14:39 +0300 (EEST) (envelope-from sobomax@mail-in.net) Received: from notebook.vega.com (das0-l103.uic-in.net [212.35.189.230]) by mail.uic-in.net (8.11.3/8.11.3) with ESMTP id f4OJBtS32613; Thu, 24 May 2001 22:11:56 +0300 (EEST) (envelope-from sobomax@mail-in.net) Date: Thu, 24 May 2001 22:11:56 +0300 (EEST) Message-Id: <200105241911.f4OJBtS32613@mail.uic-in.net> To: nsayer@quack.kfu.com Cc: java@FreeBSD.ORG From: Maxim Sobolev Reply-To: sobomax@FreeBSD.ORG Subject: Re: Java port behavior ideas X-Mailer: Pygmy (v0.5.8) In-Reply-To: <3B0C3A63.3020908@quack.kfu.com> Content-type: text/plain Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [thread redirected to java@FreeBSD.org] On Wed, 23 May 2001 15:32:03 -0700, Nick Sayer wrote: > 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. :-) Ok, suggestion noted. I'll think about it. > 2. .jar files should, IMHO, go in a common spot. ${PREFIX}/share/java = > seems quite reasonable. I'm not sure that it is technically possible. Many packages require several levels of directories, thus could be confused with such setup. Java porting rules already require that all java ports go into ${RREFIX}/share/java/${PORTNAME}, which IMO is sufficient to keep all things together. > 3. IS_JAR=3Dyes would be a nice short-hand for having a RUN_DEPENDS of = > javavmwrapper and a JRE and NO_BUILD=3Dyes. Yes, but it would require ports/Mk/bsd.java.mk, which is not there yet. > 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=3D lines= . I would rather like to see the following binding: bin/${PORTNAME} --> share/java/${PORTNAME}/${PORTNAME}.jar (${PORTNAME}.jar could be a symlink to actual .jar if necessary) > Just some ideas to kick around. Your ideas have been added into my already large javavmwrapperNG TODO list ;). Thank you for feedback! -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-java" in the body of the message