Bug 202444 - [new port] www/rubygem-acts-as-taggable-on3-rails41
Summary: [new port] www/rubygem-acts-as-taggable-on3-rails41
Status: Closed Overcome By Events
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: Martin Wilke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-19 10:04 UTC by Torsten Zühlsdorff
Modified: 2016-01-04 09:31 UTC (History)
1 user (show)

See Also:

Attachments
shar with new port (964 bytes, text/plain)
2015-08-19 10:04 UTC, Torsten Zühlsdorff 		no flags Details
patch against master for support of slave port (682 bytes, patch)
2015-08-19 10:04 UTC, Torsten Zühlsdorff 		no flags Details | Diff
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 Torsten Zühlsdorff 2015-08-19 10:04:21 UTC 
Created attachment 160034 [details]
shar with new port

This is a new Slaveport depending on Rails 4.1. It is needed as run dependency for the new GitLab port (www/gitlab).
Comment 1 Torsten Zühlsdorff 2015-08-19 10:04:37 UTC 
Created attachment 160035 [details]
patch against master for support of slave port
Comment 2 Philip M. Gollucci freebsd_committer freebsd_triage 2015-08-21 21:11:28 UTC 
Take.
Comment 3 Martin Wilke freebsd_committer freebsd_triage 2015-12-19 07:07:36 UTC 
Going to take care of this.
Comment 4 Torsten Zühlsdorff 2016-01-04 09:31:15 UTC 
I'm closing this PR, because this slave-port for Rails 4.1 was just created for the new port www/gitlab. Last month a new version of GitLab was released, which is based on Rails 4.2. Therefore we can just use the already existing master-port for www/gitlab! :)