kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/java/javavmwrapper/Makefile

57 lines
1.5 KiB
Makefile
Raw Normal View History

Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
# New ports collection makefile for: javavmwrapper
Whitespace-only: Make indentation uniform across my ports.
2000-11-01 16:51:11 +01:00
# Date created: 10 June 2000
# Whom: Maxim Sobolev <sobomax@FreeBSD.org>
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
#
# $FreeBSD$
#
# This port is self contained in the src directory.
#
PORTNAME= javavmwrapper
. Usher in javavmwrapper 2.0, a rewrite of the wrapper scripts designed to allow the simple use of multiple VMs. Brief detail of the main changes: . When a VM is registered, symbolic links for its executables are created in ${LOCALBASE}/bin. This allows people to just type 'java', 'javac', etc. without having to add the VM installation directory to their PATH. . The actual 'java' that is executed via one of these symlinks is determined by the order of the (sorted) configuration file ${LOCALBASE}/etc/javavms and by the environment variables JAVA_VERSION, JAVA_OS and JAVA_VENDOR which function to select a VM as they do in the ports framework. . There is a new command, checkvms, to sanity check the configuration and symlinks. . The "javavm" executable is currently retained in its original capacity as a synonym for Java for backward compatibility. However, its use is deprecated. . Temporarily set MAINTAINER to myself to make monitoring any initial bug reports easier. The intent is to convert it to java@ at a later date. This is built on the ideas of znerd, hq and Shelton C. Johnson Jr., with hq and Shelton contributing code and reviews. PR: 27079, 39080 Reviewed by: hq, Shelton C. Johnson Jr. <shelton_c_j@yahoo.com>
2004-11-11 20:17:37 +01:00
PORTVERSION= 2.0
One more place to reflect existence of jdk 1.5. Bump PORTREVISION
2005-01-21 11:27:52 +01:00
PORTREVISION= 3
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
CATEGORIES= java
MASTER_SITES= # none
DISTFILES= # none
. Usher in javavmwrapper 2.0, a rewrite of the wrapper scripts designed to allow the simple use of multiple VMs. Brief detail of the main changes: . When a VM is registered, symbolic links for its executables are created in ${LOCALBASE}/bin. This allows people to just type 'java', 'javac', etc. without having to add the VM installation directory to their PATH. . The actual 'java' that is executed via one of these symlinks is determined by the order of the (sorted) configuration file ${LOCALBASE}/etc/javavms and by the environment variables JAVA_VERSION, JAVA_OS and JAVA_VENDOR which function to select a VM as they do in the ports framework. . There is a new command, checkvms, to sanity check the configuration and symlinks. . The "javavm" executable is currently retained in its original capacity as a synonym for Java for backward compatibility. However, its use is deprecated. . Temporarily set MAINTAINER to myself to make monitoring any initial bug reports easier. The intent is to convert it to java@ at a later date. This is built on the ideas of znerd, hq and Shelton C. Johnson Jr., with hq and Shelton contributing code and reviews. PR: 27079, 39080 Reviewed by: hq, Shelton C. Johnson Jr. <shelton_c_j@yahoo.com>
2004-11-11 20:17:37 +01:00
MAINTAINER= glewis@FreeBSD.org
Clear moonlight beckons. Requiem mors pacem pkg-comment, And be calm ports tree. E Nomini Patri, E Fili, E Spiritu Sancti.
2003-03-07 07:14:21 +01:00
COMMENT= Wrapper script for various Java Virtual Machines
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
Take into account the '-devel' package name suffix when registering CONFLICTS with java/kaffe-devel Pointy hat to: me
2004-12-24 16:24:14 +01:00
CONFLICTS= kaffe-1.* kaffe-devel-1.*
- Register CONFLICTS with java/kaffe and java/kaffe-devel
2004-12-24 16:09:16 +01:00
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
NO_BUILD= yes
NO_WRKSUBDIR= yes
. Separate standard variables from variables local to this Makefile.
2005-04-11 22:57:57 +02:00
PKGINSTALL= ${WRKDIR}/pkg-install
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
SRC= ${.CURDIR}/src
Add a classpath script.
2004-04-01 15:40:14 +02:00
SCRIPTS= classpath javavmwrapper
# This is normally defined by bsd.java.mk when USE_JAVA is defined, but
# we can't do that here since it would result in a circular dependency
. JAVALIBDIR is more appropriate than JAVAJARDIR now we have it.
2004-09-03 18:23:01 +02:00
JAVALIBDIR= ${LOCALBASE}/share/java/classes
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
do-fetch:
@${DO_NADA}
do-configure:
Add a classpath script.
2004-04-01 15:40:14 +02:00
.for _script in ${SCRIPTS}
${SED} -e 's|%%PREFIX%%|${PREFIX}|;' \
. JAVALIBDIR is more appropriate than JAVAJARDIR now we have it.
2004-09-03 18:23:01 +02:00
-e 's|%%JAVALIBDIR%%|${JAVALIBDIR}|;' \
. Usher in javavmwrapper 2.0, a rewrite of the wrapper scripts designed to allow the simple use of multiple VMs. Brief detail of the main changes: . When a VM is registered, symbolic links for its executables are created in ${LOCALBASE}/bin. This allows people to just type 'java', 'javac', etc. without having to add the VM installation directory to their PATH. . The actual 'java' that is executed via one of these symlinks is determined by the order of the (sorted) configuration file ${LOCALBASE}/etc/javavms and by the environment variables JAVA_VERSION, JAVA_OS and JAVA_VENDOR which function to select a VM as they do in the ports framework. . There is a new command, checkvms, to sanity check the configuration and symlinks. . The "javavm" executable is currently retained in its original capacity as a synonym for Java for backward compatibility. However, its use is deprecated. . Temporarily set MAINTAINER to myself to make monitoring any initial bug reports easier. The intent is to convert it to java@ at a later date. This is built on the ideas of znerd, hq and Shelton C. Johnson Jr., with hq and Shelton contributing code and reviews. PR: 27079, 39080 Reviewed by: hq, Shelton C. Johnson Jr. <shelton_c_j@yahoo.com>
2004-11-11 20:17:37 +01:00
${SRC}/${_script}.sh >${WRKDIR}/${_script}.sh
Add a classpath script.
2004-04-01 15:40:14 +02:00
.endfor
. Move pkg-install to files/pkg-install.in since it is modified before use. This also fixes a problem that when being modified it wasn't specified by absolute path. Reported by: Robert Backhaus <robbak@robbak.com>
2004-12-16 16:38:17 +01:00
${SED} -e 's|%%LOCALBASE%%|${LOCALBASE}|;' \
${FILESDIR}/pkg-install.in > ${PKGINSTALL}
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
do-install:
Add a classpath script.
2004-04-01 15:40:14 +02:00
${INSTALL_SCRIPT} ${WRKDIR}/classpath.sh ${PREFIX}/bin/classpath
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
${INSTALL_SCRIPT} ${WRKDIR}/javavmwrapper.sh ${PREFIX}/bin/javavm
${LN} -sf ${PREFIX}/bin/javavm ${PREFIX}/bin/registervm
${LN} -sf ${PREFIX}/bin/javavm ${PREFIX}/bin/unregistervm
. Usher in javavmwrapper 2.0, a rewrite of the wrapper scripts designed to allow the simple use of multiple VMs. Brief detail of the main changes: . When a VM is registered, symbolic links for its executables are created in ${LOCALBASE}/bin. This allows people to just type 'java', 'javac', etc. without having to add the VM installation directory to their PATH. . The actual 'java' that is executed via one of these symlinks is determined by the order of the (sorted) configuration file ${LOCALBASE}/etc/javavms and by the environment variables JAVA_VERSION, JAVA_OS and JAVA_VENDOR which function to select a VM as they do in the ports framework. . There is a new command, checkvms, to sanity check the configuration and symlinks. . The "javavm" executable is currently retained in its original capacity as a synonym for Java for backward compatibility. However, its use is deprecated. . Temporarily set MAINTAINER to myself to make monitoring any initial bug reports easier. The intent is to convert it to java@ at a later date. This is built on the ideas of znerd, hq and Shelton C. Johnson Jr., with hq and Shelton contributing code and reviews. PR: 27079, 39080 Reviewed by: hq, Shelton C. Johnson Jr. <shelton_c_j@yahoo.com>
2004-11-11 20:17:37 +01:00
${LN} -sf ${PREFIX}/bin/javavm ${PREFIX}/bin/checkvms
post-install:
. Run the pkg-install script correctly. . Bump PORTREVISION for this change and the previous change to javavmwrapper itself.
2004-12-07 21:18:48 +01:00
${SETENV} PKG_PREFIX=${PREFIX} ${SH} ${PKGINSTALL} ${PKGNAME} \
. Usher in javavmwrapper 2.0, a rewrite of the wrapper scripts designed to allow the simple use of multiple VMs. Brief detail of the main changes: . When a VM is registered, symbolic links for its executables are created in ${LOCALBASE}/bin. This allows people to just type 'java', 'javac', etc. without having to add the VM installation directory to their PATH. . The actual 'java' that is executed via one of these symlinks is determined by the order of the (sorted) configuration file ${LOCALBASE}/etc/javavms and by the environment variables JAVA_VERSION, JAVA_OS and JAVA_VENDOR which function to select a VM as they do in the ports framework. . There is a new command, checkvms, to sanity check the configuration and symlinks. . The "javavm" executable is currently retained in its original capacity as a synonym for Java for backward compatibility. However, its use is deprecated. . Temporarily set MAINTAINER to myself to make monitoring any initial bug reports easier. The intent is to convert it to java@ at a later date. This is built on the ideas of znerd, hq and Shelton C. Johnson Jr., with hq and Shelton contributing code and reviews. PR: 27079, 39080 Reviewed by: hq, Shelton C. Johnson Jr. <shelton_c_j@yahoo.com>
2004-11-11 20:17:37 +01:00
POST-INSTALL
Initial import of javavmwrapper - a simple shell script which would allow Java-based ports to use any of the Java Virtual Machines installed on the system.
2000-06-12 11:42:51 +02:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink