From owner-freebsd-ruby@freebsd.org Fri Jan 29 11:02:46 2016 Return-Path: Delivered-To: freebsd-ruby@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DC14CA71640 for ; Fri, 29 Jan 2016 11:02:46 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from toco-domains.de (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id AAB4D1E50 for ; Fri, 29 Jan 2016 11:02:46 +0000 (UTC) (envelope-from mailinglists@toco-domains.de) Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6]) by toco-domains.de (Postfix) with ESMTPA id 46FEE1B22069 for ; Fri, 29 Jan 2016 12:02:44 +0100 (CET) Subject: Re: Obsoleting Rails 3.x? To: freebsd-ruby@freebsd.org References: <56A08842.8090105@toco-domains.de> <56A10C9A.3090604@FreeBSD.org> <56A20126.9040901@toco-domains.de> <56A60EAB.9080205@toco-domains.de> From: Torsten Zuehlsdorff Message-ID: <56AB46D3.4090207@toco-domains.de> Date: Fri, 29 Jan 2016 12:02:43 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 MIME-Version: 1.0 In-Reply-To: <56A60EAB.9080205@toco-domains.de> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 29 Jan 2016 11:02:46 -0000 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