Sat Dec 17 17:26:54 2011 UTC ()
Importing databases/ruby-dm-is-state_machine package version 1.2.0.


DataMapper plugin that adds state machine functionality to your models.

== Why is this plugin useful?

Your DataMapper resource might benefit from a state machine if it:

* has different "modes" of operation
* has discrete behaviors
* especially if the behaviors are mutually exclusive

And you want a clean, high-level way of describing these modes / behaviors
and how the resource moves between them.  This plugin allows you to
declaratively describe the states and transitions involved.

Status:

Vendor Tag:	TNF
Release Tags:	pkgsrc-base


(taca)
diff -r0 -r1.1.1.1 pkgsrc/databases/ruby-dm-is-state_machine/Makefile
diff -r0 -r1.1.1.1 pkgsrc/databases/ruby-dm-is-state_machine/PLIST
diff -r0 -r1.1.1.1 pkgsrc/databases/ruby-dm-is-state_machine/distinfo
diff -r0 -r1.1.1.1 pkgsrc/databases/ruby-dm-is-state_machine/DESCR

File Added: pkgsrc/databases/ruby-dm-is-state_machine/Makefile
# $NetBSD: Makefile,v 1.1.1.1 2011/12/17 17:26:53 taca Exp $

DISTNAME=	dm-is-state_machine-1.2.0
CATEGORIES=	databases

MAINTAINER=	pkgsrc-users@NetBSD.org
HOMEPAGE=	http://github.com/datamapper/dm-is-state_machine
COMMENT=	DataMapper plugin for creating state machines
LICENSE=	mit

DEPENDS+=	${RUBY_PKGPREFIX}-dm-core>=1.2.0<1.3:../../databases/ruby-dm-core

.include "../../lang/ruby/gem.mk"
.include "../../mk/bsd.pkg.mk"

File Added: pkgsrc/databases/ruby-dm-is-state_machine/PLIST
@comment $NetBSD: PLIST,v 1.1.1.1 2011/12/17 17:26:53 taca Exp $
${GEM_HOME}/cache/${GEM_NAME}.gem
${GEM_LIBDIR}/Gemfile
${GEM_LIBDIR}/LICENSE
${GEM_LIBDIR}/README.rdoc
${GEM_LIBDIR}/Rakefile
${GEM_LIBDIR}/VERSION
${GEM_LIBDIR}/dm-is-state_machine.gemspec
${GEM_LIBDIR}/lib/dm-is-state_machine.rb
${GEM_LIBDIR}/lib/dm-is-state_machine/is/data/event.rb
${GEM_LIBDIR}/lib/dm-is-state_machine/is/data/machine.rb
${GEM_LIBDIR}/lib/dm-is-state_machine/is/data/state.rb
${GEM_LIBDIR}/lib/dm-is-state_machine/is/dsl/event_dsl.rb
${GEM_LIBDIR}/lib/dm-is-state_machine/is/dsl/state_dsl.rb
${GEM_LIBDIR}/lib/dm-is-state_machine/is/state_machine.rb
${GEM_LIBDIR}/spec/examples/invalid_events.rb
${GEM_LIBDIR}/spec/examples/invalid_states.rb
${GEM_LIBDIR}/spec/examples/invalid_transitions_1.rb
${GEM_LIBDIR}/spec/examples/invalid_transitions_2.rb
${GEM_LIBDIR}/spec/examples/light_switch.rb
${GEM_LIBDIR}/spec/examples/slot_machine.rb
${GEM_LIBDIR}/spec/examples/traffic_light.rb
${GEM_LIBDIR}/spec/integration/inheritance_spec.rb
${GEM_LIBDIR}/spec/integration/invalid_events_spec.rb
${GEM_LIBDIR}/spec/integration/invalid_states_spec.rb
${GEM_LIBDIR}/spec/integration/invalid_transitions_spec.rb
${GEM_LIBDIR}/spec/integration/slot_machine_spec.rb
${GEM_LIBDIR}/spec/integration/traffic_light_spec.rb
${GEM_LIBDIR}/spec/rcov.opts
${GEM_LIBDIR}/spec/spec.opts
${GEM_LIBDIR}/spec/spec_helper.rb
${GEM_LIBDIR}/spec/unit/data/event_spec.rb
${GEM_LIBDIR}/spec/unit/data/machine_spec.rb
${GEM_LIBDIR}/spec/unit/data/state_spec.rb
${GEM_LIBDIR}/spec/unit/dsl/event_dsl_spec.rb
${GEM_LIBDIR}/spec/unit/dsl/state_dsl_spec.rb
${GEM_LIBDIR}/spec/unit/state_machine_spec.rb
${GEM_LIBDIR}/tasks/spec.rake
${GEM_LIBDIR}/tasks/yard.rake
${GEM_LIBDIR}/tasks/yardstick.rake
${GEM_HOME}/specifications/${GEM_NAME}.gemspec

File Added: pkgsrc/databases/ruby-dm-is-state_machine/distinfo
$NetBSD: distinfo,v 1.1.1.1 2011/12/17 17:26:53 taca Exp $

SHA1 (dm-is-state_machine-1.2.0.gem) = 68283fe6314ecd2c6c5c0e6dc6d309e17c39db6e
RMD160 (dm-is-state_machine-1.2.0.gem) = b52f20bb7952d79c991c4c6bff20a19a24e19372
Size (dm-is-state_machine-1.2.0.gem) = 14336 bytes

File Added: pkgsrc/databases/ruby-dm-is-state_machine/DESCR
DataMapper plugin that adds state machine functionality to your models.

== Why is this plugin useful?

Your DataMapper resource might benefit from a state machine if it:

* has different "modes" of operation
* has discrete behaviors
* especially if the behaviors are mutually exclusive

And you want a clean, high-level way of describing these modes / behaviors
and how the resource moves between them.  This plugin allows you to
declaratively describe the states and transitions involved.