Summary: | www/rubygem-rails4 rubygem-passenger dependency now has flavors | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | Jonas Palm <jonaspalm> |
Component: | Individual Port(s) | Assignee: | Dan Langille <dvl> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | swills |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(ruby) |
Version: | Latest | ||
Hardware: | Any | ||
OS: | Any |
Description
Jonas Palm
2018-01-24 13:07:17 UTC
It should be fixed in r460140 (bug #225465). Do you use the passenger option of the www/rubygem-rails4 port? I'm wondering how useful the option is and if we can remove it. The fix doesn't seem to be enough: PASSENGER_RUN_DEPENDS= rubygem-passenger-*>=2.2.15:www/rubygem-passenger Causes poudriere to install www/rubygem-passenger with the default flavor (apache) which in turn then conflicts with the nginx flavoured port that I want to use. I think it's necessary to add flavors to this port as well. I'm using the passenger option and this rails port to run redmine via passenger via nginx. (In reply to Jonas Palm from comment #3) I'm wondering if the better solution is to remove the passenger option from rails4 and just have you install the web server based on your needs. What do you think? That would be fine with me. www/redmine has the same problem, I've opened another bug report: #226058 A commit references this bug: Author: swills Date: Tue Mar 20 01:31:29 UTC 2018 New revision: 465053 URL: https://svnweb.freebsd.org/changeset/ports/465053 Log: www/rubygem-rails4: Remove passenger option It isn't really needed. PR: 225428 Changes: head/www/rubygem-rails4/Makefile Fix committed |