summaryrefslogtreecommitdiff
path: root/databases/ruby-dm-rails
AgeCommit message (Collapse)AuthorFilesLines
2015-11-03Add SHA512 digests for distfiles for databases categoryagc1-1/+2
Problems found with existing distfiles: distfiles/D6.data.ros.gz distfiles/cstore0.2.tar.gz distfiles/data4.tar.gz distfiles/sphinx-2.2.7-release.tar.gz No changes made to the cstore or mariadb55-client distinfo files. Otherwise, existing SHA1 digests verified and found to be the same on the machine holding the existing distfiles (morden). All existing SHA1 digests retained for now as an audit trail.
2013-01-31ruby-dm-rails can work with all 3.x versions of Ruby on Rails.taca1-4/+4
Bump PKGREVISION.
2012-06-14Bump PKGREVISION for those RUBY_RAILS_STRICT_DEP is set to no implicitly now.taca1-1/+2
(Relax dependency to Ruby on Rails component packages.)
2012-03-20Update ruby-dm-rails to 1.2.1.taca2-7/+7
* Restrict it to Ruby on Rails 3 instead of 31. * Exact changes are unknown.
2011-12-17Importing databases/ruby-dm-rails package version 1.2.0.taca4-0/+71
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.