summaryrefslogtreecommitdiff
path: root/devel/swig
diff options
context:
space:
mode:
authortaca <taca>2011-12-17 17:35:27 +0000
committertaca <taca>2011-12-17 17:35:27 +0000
commitb499073cc2d29d8ec886d1a7de2f06556d8db6dc (patch)
tree23fdefd72f523a9f4630fbfdc4c5c04e9e264b2d /devel/swig
parent1f54fbbf2a75452a10b51f43c4dd67d93ddc53ed (diff)
downloadpkgsrc-b499073cc2d29d8ec886d1a7de2f06556d8db6dc.tar.gz
Importing databases/ruby-dm-rails package version 1.2.0.
Dm-rails provides the railtie that allows datamapper to hook into rails3 and thus behave like a rails framework component. Just like activerecord does in rails, dm-rails uses the railtie API to hook into rails. The two are actually hooked into rails almost identically. Creating new datamapper apps on rails3 from scratch is actually really easy. The following will guide you through the process.
Diffstat (limited to 'devel/swig')
0 files changed, 0 insertions, 0 deletions