Bug 202439 - [new port] www/rubygem-carrierwave-rails41
Summary: [new port] www/rubygem-carrierwave-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 08:44 UTC by Torsten Zühlsdorff
Modified: 2016-01-04 09:29 UTC (History)
1 user (show)

See Also:


Attachments
shar with new port (1.07 KB, text/plain)
2015-08-19 08:44 UTC, Torsten Zühlsdorff
no flags Details
patch against master for support of slave port (614 bytes, patch)
2015-08-19 08:44 UTC, Torsten Zühlsdorff
no flags Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Torsten Zühlsdorff 2015-08-19 08:44:23 UTC
Created attachment 160025 [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 08:44:40 UTC
Created attachment 160026 [details]
patch against master for support of slave port
Comment 2 Philip M. Gollucci freebsd_committer freebsd_triage 2015-08-21 21:11:22 UTC
Take.
Comment 3 Martin Wilke freebsd_committer freebsd_triage 2015-12-19 07:06:59 UTC
Going to take care of this.
Comment 4 Torsten Zühlsdorff 2016-01-04 09:29:19 UTC
I'm closing this PR, because this slave-port for Rails 4.1 was just created for the new port www/gitlab. This 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! :)