Bug 157994 - [new port] databases/rubygem-dm-rails
Summary: [new port] databases/rubygem-dm-rails
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Steve Wills
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-18 16:40 UTC by Ryan Steinmetz
Modified: 2011-06-18 19:47 UTC (History)
0 users

See Also:

Attachments
file.shar (2.19 KB, text/plain)
2011-06-18 16:40 UTC, Ryan Steinmetz 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Steinmetz 2011-06-18 16:40:06 UTC 
This port is dependent on ports/157993


This gem 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.

WWW: http://rubygems.org/gems/dm-rails

Fix: Patch attached with submission follows:
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2011-06-18 16:40:16 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->ruby

ruby@ wants this port PRs (via the GNATS Auto Assign Tool)
Comment 2 Steve Wills freebsd_committer freebsd_triage 2011-06-18 19:13:49 UTC 
Responsible Changed
From-To: ruby->swills

I'll take it.
Comment 3 Steve Wills freebsd_committer freebsd_triage 2011-06-18 19:47:01 UTC 
State Changed
From-To: open->closed

New port added. Thanks!