Re: Obsoleting Rails 3.x?

2016-01-21 Thread Steve Wills
On 01/21/16 02:26 AM, Torsten Zühlsdorff wrote: > Hello, > > 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

FreeBSD ports you maintain which are out of date

2016-01-21 Thread portscout
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you

Re: disabling ri and rdoc by default

2016-01-21 Thread Torsten Zühlsdorff
Hello Steve, I was thinking, maybe we don't need ri and rdoc stuff in packages by default. For servers they aren't that useful and even for development, I get the impression people don't use them much. Anyone have opinions for or against? I have no objections. As you stated: for servers they a

Obsoleting Rails 3.x?

2016-01-21 Thread Torsten Zühlsdorff
Hello, 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 be