Bug 158035 - [new port] graphics/rubygem-rmagick
Summary: [new port] graphics/rubygem-rmagick
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: Ryan Steinmetz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-19 18:30 UTC by Ryan Steinmetz
Modified: 2011-09-09 01:47 UTC (History)
0 users

See Also:


Attachments
file.shar (1.69 KB, text/plain)
2011-06-19 18:30 UTC, Ryan Steinmetz
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan Steinmetz 2011-06-19 18:30:17 UTC
-Resurrect graphics/rubygem-rmagick
-Update to 2.13.1
-Adopt port (unless garga@ would prefer to have it back)

graphics-ruby-rmagick does not install the gem that is required by other applications, so I do not believe this is a duplicate.

Fix: Patch attached with submission follows:
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2011-06-19 18:30:35 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-19 19:06:47 UTC
Responsible Changed
From-To: ruby->swills

I'll take it.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2011-06-30 04:08:41 UTC
State Changed
From-To: open->feedback

Trying to look over stale/duplicate PRs ... 

The port graphics/rubygem-rmagick used to exist and then was deleted 
about a year ago because it was a duplicate of ruby-rmagick.  Is the 
intention to bring it back under the old name? 

I have to admit confusion here.
Comment 4 Ryan Steinmetz 2011-06-30 12:17:58 UTC
At the moment, swills@ and I are looking into the best way to handle this.  ruby-rmagick installs the library(RMagick2.so), but does not register with the gem framework.  As a result, Ruby apps that depend on the rmagick gem complain that the gem is not installed.

It's on hold at the moment as I look into it a bit more and identify the best way to proceed.
Comment 5 Steve Wills freebsd_committer freebsd_triage 2011-07-17 02:37:22 UTC
Responsible Changed
From-To: swills->zi

Over to submitter who has commit access now
Comment 6 Ryan Steinmetz freebsd_committer freebsd_triage 2011-09-09 01:47:42 UTC
State Changed
From-To: feedback->closed

Closing this for now.