openbsd-ports/devel/ruby-ref/Makefile

# $OpenBSD: Makefile,v 1.3 2013/10/26 23:55:36 jeremy Exp $

COMMENT =	object reference utilities for ruby

DISTNAME =	ref-1.0.2
REVISION =	0
CATEGORIES =	devel

HOMEPAGE=	https://github.com/bdurand/ref

# MIT
PERMIT_PACKAGE_CDROM =	Yes

MODULES =	lang/ruby
CONFIGURE_STYLE = ruby gem

MODRUBY_TEST = testrb
MODRUBY_TEST_TARGET = test/*_test.rb

.include <bsd.port.mk>
Bump all ruby gem ports supporting rbx FLAVOR due to change to rubinius gem directory when upgrading rubinius from 1.2.4 to 2.1.1. 2013-10-26 23:55:34 +00:00			`# $OpenBSD: Makefile,v 1.3 2013/10/26 23:55:36 jeremy Exp $`
Import ruby-ref-1.0.2. ruby-ref provides object references for Ruby as well as some common utilities for working with references. Object references are used to point to other objects and come in three distinct flavors that interact differently with the garbage collector. * Ref::StrongReference - This is a plain old pointer to another object. * Ref::WeakReference - This is a pointer to another object, but it is not seen by the garbage collector and the memory used by the object can be reclaimed at any time. * Ref::SoftReference - This is similar to a weak reference, but the garbage collector is not as eager to reclaim the referenced object. All of these classes extend from a common Ref::Reference class and have a common interface. Weak and soft references are useful when you have instantiated objects that you may want to use again but can recreate if necessary. Since the garbage collector determines when to reclaim the memory used by the objects, you don't need to worry about bloating the Ruby heap. OK abieber@ 2012-12-12 21:49:37 +00:00
			`COMMENT = object reference utilities for ruby`

			`DISTNAME = ref-1.0.2`
Bump all ruby gem ports supporting rbx FLAVOR due to change to rubinius gem directory when upgrading rubinius from 1.2.4 to 2.1.1. 2013-10-26 23:55:34 +00:00			`REVISION = 0`
Import ruby-ref-1.0.2. ruby-ref provides object references for Ruby as well as some common utilities for working with references. Object references are used to point to other objects and come in three distinct flavors that interact differently with the garbage collector. * Ref::StrongReference - This is a plain old pointer to another object. * Ref::WeakReference - This is a pointer to another object, but it is not seen by the garbage collector and the memory used by the object can be reclaimed at any time. * Ref::SoftReference - This is similar to a weak reference, but the garbage collector is not as eager to reclaim the referenced object. All of these classes extend from a common Ref::Reference class and have a common interface. Weak and soft references are useful when you have instantiated objects that you may want to use again but can recreate if necessary. Since the garbage collector determines when to reclaim the memory used by the objects, you don't need to worry about bloating the Ruby heap. OK abieber@ 2012-12-12 21:49:37 +00:00			`CATEGORIES = devel`

			`HOMEPAGE= https://github.com/bdurand/ref`

			`# MIT`
			`PERMIT_PACKAGE_CDROM = Yes`

			`MODULES = lang/ruby`
			`CONFIGURE_STYLE = ruby gem`

PERMIT_* / REGRESS->TEST sweep 2013-03-11 10:50:00 +00:00			`MODRUBY_TEST = testrb`
			`MODRUBY_TEST_TARGET = test/*_test.rb`
Import ruby-ref-1.0.2. ruby-ref provides object references for Ruby as well as some common utilities for working with references. Object references are used to point to other objects and come in three distinct flavors that interact differently with the garbage collector. * Ref::StrongReference - This is a plain old pointer to another object. * Ref::WeakReference - This is a pointer to another object, but it is not seen by the garbage collector and the memory used by the object can be reclaimed at any time. * Ref::SoftReference - This is similar to a weak reference, but the garbage collector is not as eager to reclaim the referenced object. All of these classes extend from a common Ref::Reference class and have a common interface. Weak and soft references are useful when you have instantiated objects that you may want to use again but can recreate if necessary. Since the garbage collector determines when to reclaim the memory used by the objects, you don't need to worry about bloating the Ruby heap. OK abieber@ 2012-12-12 21:49:37 +00:00
			`.include <bsd.port.mk>`