Created attachment 157973 [details]
shar with new port
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 exists, but just which the default option to use rubygem-railties in version 3. gitlab needs version 4, so there will be a conflict by using the existing port.
This already exists with OPTION RAILS4 here databases/rubygem-dm-devise
rubygem-dm-devise is - as fas as i can see - not the same like rubygem-devise.
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.
Sigh. In that case it would make sense to have SLAVE ports rather than a copy.
also I made a typo with dm-devise
A commit references this bug:
Date: Tue Jun 30 03:26:24 UTC 2015
New revision: 390946
Add two new slave ports for a future gitlabs port
Connect them to the build
PR: 201038, 201039
Requested by: firstname.lastname@example.org
Thank you very much for writing the slave-ports! :)