cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2ed4ce70f8
openbsd-ports/net/ruby-amqp-utils/Makefile

29 lines
634 B
Makefile
Raw Normal View History

normalize pkgpath
2011-09-16 07:13:37 -04:00
# $OpenBSD: Makefile,v 1.8 2011/09/16 11:13:40 espie Exp $
initial import of ruby-amqp-utils-0.1.2 CLI utility programs for interacting with an AMQP queue. Using these utilities, one can interact with an AMQP queue from the command line or via a shell script. These utilities have been tested against RabbitMQ, but they should work with other AMQP compliant queues. They depend on the amqp gem available at <http://github.com/tmm1/amqp>. ok bernd@
2009-11-22 01:52:36 -05:00
COMMENT = AMQP command line utilities
Bump version to 0.2.3. Remove MASTER_SITE_RUBYFORGE, in favor of the default MASTER_SITE_RUBYGEMS. Add PKG_ARCH=* since this is a pure ruby package. Remove now unneeded patch. ok landry
2010-10-15 11:40:07 -04:00
DISTNAME = amqp-utils-0.2.3
normalize pkgpath
2011-09-16 07:13:37 -04:00
REVISION = 3
initial import of ruby-amqp-utils-0.1.2 CLI utility programs for interacting with an AMQP queue. Using these utilities, one can interact with an AMQP queue from the command line or via a shell script. These utilities have been tested against RabbitMQ, but they should work with other AMQP compliant queues. They depend on the amqp gem available at <http://github.com/tmm1/amqp>. ok bernd@
2009-11-22 01:52:36 -05:00
CATEGORIES = net
# MIT
PERMIT_PACKAGE_CDROM= Yes
PERMIT_PACKAGE_FTP= Yes
PERMIT_DISTFILES_CDROM= Yes
PERMIT_DISTFILES_FTP= Yes
MODULES = lang/ruby
CONFIGURE_STYLE = ruby gem
BUILD_DEPENDS = ${RUN_DEPENDS}
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
RUN_DEPENDS = devel/ruby-facets,${MODRUBY_FLAVOR}>=2.7.0 \
devel/ruby-trollop,${MODRUBY_FLAVOR}>=1.10.2 \
net/ruby-amqp,${MODRUBY_FLAVOR}>=0.6.0 \
converters/ruby-json,${MODRUBY_FLAVOR}>=1.1.6 \
devel/ruby-clio,${MODRUBY_FLAVOR}
Bump version to 0.2.3. Remove MASTER_SITE_RUBYFORGE, in favor of the default MASTER_SITE_RUBYGEMS. Add PKG_ARCH=* since this is a pure ruby package. Remove now unneeded patch. ok landry
2010-10-15 11:40:07 -04:00
MODRUBY_REGRESS = rake
initial import of ruby-amqp-utils-0.1.2 CLI utility programs for interacting with an AMQP queue. Using these utilities, one can interact with an AMQP queue from the command line or via a shell script. These utilities have been tested against RabbitMQ, but they should work with other AMQP compliant queues. They depend on the amqp gem available at <http://github.com/tmm1/amqp>. ok bernd@
2009-11-22 01:52:36 -05:00
.include <bsd.port.mk>
Reference in New Issue Copy Permalink