Bug 201039
| Summary: | [new port] devel/rubygem-devise-async-rails4 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Torsten Zühlsdorff <ports> | ||||
| Component: | Individual Port(s) | Assignee: | Philip M. Gollucci <pgollucci> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | mmoll, ports | ||||
| Priority: | --- | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
Take. Same comment. OPTION RAILS4 Yes, rubygem-devise has an option RAILS4. But this option is *not* the default. I'm currently creating a port for gitlab and this needs rails4 and rubygem-devise. To support the creation of binary-packages for pkg, this new port is needed. Packages are created with the default options; which is RAILS3, not 4. A commit references this bug: Author: pgollucci Date: Tue Jun 30 03:26:24 UTC 2015 New revision: 390946 URL: https://svnweb.freebsd.org/changeset/ports/390946 Log: Add two new slave ports for a future gitlabs port Connect them to the build PR: 201038, 201039 Requested by: ports@toco-domains.de Changes: head/devel/Makefile head/devel/rubygem-devise/Makefile head/devel/rubygem-devise-async/Makefile head/devel/rubygem-devise-async-rails4/ head/devel/rubygem-devise-async-rails4/Makefile head/devel/rubygem-devise-rails4/ head/devel/rubygem-devise-rails4/Makefile |
Created attachment 157974 [details] shar with new port devel/rubygem-devise-async-rails4 While working at a port for gitlab, i figured out, that this port is needed to support the creation of an packet for gitlab. The port devel/rubygem-devise-async exists, but just which the default option to use rubygem-devise, which needs rubygem-railties in version 3. gitlab needs version 4, so there will be a conflict by using the existing port.