freebsd-ports/devel/rubygem-open4/Makefile

# Ports collection makefile for:	rubygem-open4
# Date created:				2007-12-17
# Whom:					arved
#
# $FreeBSD$

PORTNAME=	open4
PORTVERSION=	1.3.0
CATEGORIES=	devel rubygems
MASTER_SITES=	RG

MAINTAINER=	sunpoet@FreeBSD.org
COMMENT=	Open4 manages child processes and their io handles

USE_RUBY=	yes
USE_RUBYGEMS=	yes
RUBYGEM_AUTOPLIST=	yes

.include <bsd.port.mk>
Add rubygem-open4, another variant to exeute programs from ruby 2008-01-03 12:34:26 +01:00			`# Ports collection makefile for: rubygem-open4`
			`# Date created: 2007-12-17`
			`# Whom: arved`
			`#`
			`# $FreeBSD$`

			`PORTNAME= open4`
- Update to 1.3.0 - Take maintainership - Add RG link to pkg-descr Changes: https://github.com/ahoward/open4/commits/master PR: ports/165169 Submitted by: sunpoet (myself) Approved by: arved (maintainer) 2012-02-16 16:30:00 +01:00			`PORTVERSION= 1.3.0`
Add rubygem-open4, another variant to exeute programs from ruby 2008-01-03 12:34:26 +01:00			`CATEGORIES= devel rubygems`
Use RG Macro PR: 147039 Submitted by: pgollucci 2010-05-30 15:35:10 +02:00			`MASTER_SITES= RG`
Add rubygem-open4, another variant to exeute programs from ruby 2008-01-03 12:34:26 +01:00
- Update to 1.3.0 - Take maintainership - Add RG link to pkg-descr Changes: https://github.com/ahoward/open4/commits/master PR: ports/165169 Submitted by: sunpoet (myself) Approved by: arved (maintainer) 2012-02-16 16:30:00 +01:00			`MAINTAINER= sunpoet@FreeBSD.org`
Add rubygem-open4, another variant to exeute programs from ruby 2008-01-03 12:34:26 +01:00			`COMMENT= Open4 manages child processes and their io handles`

			`USE_RUBY= yes`
- Add ruby 1.9 support - Implement new knobs for gems and rake (these are included in ruby 1.9 distribution already). Also move gem bits from ruby-gems/Makefile.common to bsd.ruby.mk[1]. Now to depend on gems or rake you should define USE_RUBYGEMS/USE_RAKE accordingly. Also RAKE_BIN variable is provided for pointing to the right rake executable. - Rewrite RUBY_SCHEBANG in awk to eliminate build dependency on ruby. Discussed with: Jonathan Weiss <jw@innerewut.de> [1] (gems maintainer) Tested by: ports@ 2008-04-06 10:58:21 +02:00			`USE_RUBYGEMS= yes`
- convert to RUBYGEM_AUTOPLIST remove x-generate-plist and friends - use RF macro and remove SUBDIR where possible - remove some uneeded GEM_NAME=${DISTNAME} (this c/should be handled better in bsd.*.mk) other deltas specific to individual ports: audio/rubygem-mp3info - unbreak, fix packaging, bump PORTREVISION devel/rubygem-rapt - adopt devel/rubygem-rspec - remove BUILD_DEPENDS=RUN_DEPENDS -- neither set devel/rubygem-ruby2ruby - add #' for vim highlight graphics/rubygem-extifr - drop PORTREVISION=0 graphics/rubygem-gd2 - add #' for vim highlight www/rubygem-rubyfulsoup - swap GEM_NAME / DISTNAME for constistency Sponsored by: RideCharge Inc. Tested on: RideCharge's Tinderbox Reviewed by: stas 2009-04-09 02:11:47 +02:00			`RUBYGEM_AUTOPLIST= yes`
Add rubygem-open4, another variant to exeute programs from ruby 2008-01-03 12:34:26 +01:00
- Add ruby 1.9 support - Implement new knobs for gems and rake (these are included in ruby 1.9 distribution already). Also move gem bits from ruby-gems/Makefile.common to bsd.ruby.mk[1]. Now to depend on gems or rake you should define USE_RUBYGEMS/USE_RAKE accordingly. Also RAKE_BIN variable is provided for pointing to the right rake executable. - Rewrite RUBY_SCHEBANG in awk to eliminate build dependency on ruby. Discussed with: Jonathan Weiss <jw@innerewut.de> [1] (gems maintainer) Tested by: ports@ 2008-04-06 10:58:21 +02:00			`.include <bsd.port.mk>`