openbsd-ports/www/mod_ruby/Makefile

# $OpenBSD: Makefile,v 1.14 2010/11/24 21:35:16 jeremy Exp $

COMMENT=		module that embeds Ruby into Apache

DISTNAME=		mod_ruby-1.2.6
REVISION =		5
CATEGORIES=		www

HOMEPAGE=		http://modruby.net/

MAINTAINER=		Adam Montague <amontague@siriushosting.com>

MODULES=		apache-module lang/ruby

# BSD
PERMIT_PACKAGE_CDROM=	Yes
PERMIT_PACKAGE_FTP=	Yes
PERMIT_DISTFILES_CDROM=	Yes
PERMIT_DISTFILES_FTP=	Yes
WANTLIB=		m ${MODRUBY_WANTLIB}

MODAPACHE_NAME=		ruby

MASTER_SITES=		http://modruby.net/archive/

LIB_DEPENDS=		${MODRUBY_LIB_DEPENDS}

CONFIGURE_STYLE=	simple
CONFIGURE_SCRIPT=	configure.rb
CONFIGURE_ARGS+=	--with-apxs=/usr/sbin/apxs

NO_REGRESS=		Yes

SEPARATE_BUILD=		concurrent
INSTALL_TARGET=		install-ruby

SUBST_VARS=		PKGNAME

post-build:
	@${MODAPACHE_CREATE_ENABLE_SCRIPT}

post-install:
	${INSTALL_DATA_DIR} ${PREFIX}/share/examples/mod_ruby
	${INSTALL_DATA} ${WRKSRC}/examples/httpd.conf ${PREFIX}/share/examples/mod_ruby/
	${MODAPACHE_INSTALL}

.include <bsd.port.mk>
REVISION bump all ruby ports due to a change in the pkgspec. Previously, we were using ruby->=1.8,<=1.9, instead of ruby->=1.8,<1.9. While this wouldn't cause an issue, since our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9, it's still wrong and should be fixed. This also fixes the following minor issues: Switch from using FLAVOR to MODRUBY_FLAVOR for _DEPENDS. Currently we don't have a ruby port that uses FLAVORs that would differ from MODRUBY_FLAVOR, but it's possible we will in the future. Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in REGRESS_DEPENDS. This probably is not strictly necessary, but BUILD_PKGPATH is used in more cases, so it is good for consistency. Switch to new style _DEPENDS, with the version specification at the end. The remaining cases where this is not done is because a specific version is used. Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if the old version is installed when you run a regress test, it will install the new version first. Some conversion of spaces to tabs for consistency. OK landry@ 2010-11-24 16:35:13 -05:00			`# $OpenBSD: Makefile,v 1.14 2010/11/24 21:35:16 jeremy Exp $`
initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00
Remove surrounding quotes from COMMENT-/ERRORS/NO_REGRESS/PERMIT_/REGRESS_IS_INTERACTIVE Change '.include "bsd.port.mk"' to '.include <bsd.port.mk>' while here (ok naddy@) 2007-09-15 16:38:20 -04:00			`COMMENT= module that embeds Ruby into Apache`
initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00
Update to mod_ruby-1.2.6. From maintainer Adam Montague. 2006-10-26 15:45:58 -04:00			`DISTNAME= mod_ruby-1.2.6`
REVISION bump all ruby ports due to a change in the pkgspec. Previously, we were using ruby->=1.8,<=1.9, instead of ruby->=1.8,<1.9. While this wouldn't cause an issue, since our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9, it's still wrong and should be fixed. This also fixes the following minor issues: Switch from using FLAVOR to MODRUBY_FLAVOR for _DEPENDS. Currently we don't have a ruby port that uses FLAVORs that would differ from MODRUBY_FLAVOR, but it's possible we will in the future. Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in REGRESS_DEPENDS. This probably is not strictly necessary, but BUILD_PKGPATH is used in more cases, so it is good for consistency. Switch to new style _DEPENDS, with the version specification at the end. The remaining cases where this is not done is because a specific version is used. Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if the old version is installed when you run a regress test, it will install the new version first. Some conversion of spaces to tabs for consistency. OK landry@ 2010-11-24 16:35:13 -05:00			`REVISION = 5`
initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00			`CATEGORIES= www`

			`HOMEPAGE= http://modruby.net/`

			`MAINTAINER= Adam Montague <amontague@siriushosting.com>`

respect MODRUBY_LIB_DEPENDS, no plist change ok bernd@ 2009-08-10 12:48:27 -04:00			`MODULES= apache-module lang/ruby`
switch to apache-module framework confirmed by Adam Montague (maintainer) 2007-06-21 16:54:33 -04:00
initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00			`# BSD`
			`PERMIT_PACKAGE_CDROM= Yes`
			`PERMIT_PACKAGE_FTP= Yes`
			`PERMIT_DISTFILES_CDROM= Yes`
			`PERMIT_DISTFILES_FTP= Yes`
Handle the rest of the fallout from the splitting of MODRUBY_LIB_DEPENDS into MODRUBY_WANTLIB and using CONFIGURE_STYLE = ruby gem ext. Use the lang/ruby module for all dependent ports, setting MODRUBY_{BUILD,RUN}DEP=No if necessary. ok landry, phessler, sthen 2010-10-26 17:42:13 -04:00			`WANTLIB= m ${MODRUBY_WANTLIB}`
initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00
switch to apache-module framework confirmed by Adam Montague (maintainer) 2007-06-21 16:54:33 -04:00			`MODAPACHE_NAME= ruby`

initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00			`MASTER_SITES= http://modruby.net/archive/`

respect MODRUBY_LIB_DEPENDS, no plist change ok bernd@ 2009-08-10 12:48:27 -04:00			`LIB_DEPENDS= ${MODRUBY_LIB_DEPENDS}`
initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00
			`CONFIGURE_STYLE= simple`
			`CONFIGURE_SCRIPT= configure.rb`
			`CONFIGURE_ARGS+= --with-apxs=/usr/sbin/apxs`

			`NO_REGRESS= Yes`

			`SEPARATE_BUILD= concurrent`
			`INSTALL_TARGET= install-ruby`

SUBST_VARS=PKGNAME from maintainer Adam Montague <amontague at siriushosting.com> 2005-10-28 15:40:32 -04:00			`SUBST_VARS= PKGNAME`

initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00			`post-build:`
switch to apache-module framework confirmed by Adam Montague (maintainer) 2007-06-21 16:54:33 -04:00			`@${MODAPACHE_CREATE_ENABLE_SCRIPT}`
initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00
			`post-install:`
			`${INSTALL_DATA_DIR} ${PREFIX}/share/examples/mod_ruby`
			`${INSTALL_DATA} ${WRKSRC}/examples/httpd.conf ${PREFIX}/share/examples/mod_ruby/`
switch to apache-module framework confirmed by Adam Montague (maintainer) 2007-06-21 16:54:33 -04:00			`${MODAPACHE_INSTALL}`
initial import of mod_ruby, from Adam Montague Mod_ruby embeds the Ruby interpreter into the Apache web server, allowing Ruby CGI scripts to be executed natively. These scripts will start up much faster than without mod_ruby. 2005-01-16 18:44:39 -05:00
			`.include <bsd.port.mk>`