On 25.01.2016 13:01, Torsten Zuehlsdorff wrote:
while working on many ports i figured out there are a bunch of
dependencies to our Rails 3 port. But for many rubygems this is not
needed - they already work with Rails 4.2. Often this results in a port
based on Rails 3 and a slave port with Rails 4.2.
This will become even more bad because Rails 5 is already on its way.
Also when i'm understanding the release notices correct (i found them
quite confusing) they state:
- Rails 3.2 will only fix really bad security issues (while letting
"normal" security issues intact)
- you seem to get the fixes just if you pay
So i would announce, that we go through the gems and do a little
cleanup. If a gem will work with Rails 4.2 we should switch its
dependency to this version instead of Rails 3.
Your thoughts? Objections?
Sounds good, let's do it.
Fine! :) I will start next week!
Okay, i did start, but with another step. First i set all Rails 4.1
ports deprecated. I introduced them just for the GitLab port, which no
longer needs them:
https://github.com/t-zuehlsdorff/freebsd-ports/tree/remove_rails41
I will create review and PR soon. First i need to take care about
another PR.
Here is the PR:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206735
In the next step i will wrote updates for all the ports depending on
Rails 3. When there are no dependencies left, i will write a patch to
expire Rails 3.
Greetings,
Torsten
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ruby
To unsubscribe, send any mail to "[email protected]"
