From owner-freebsd-ruby@freebsd.org Mon Jun 20 17:52:31 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 8576EA7A3F4 for ; Mon, 20 Jun 2016 17:52:31 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 6ED371D27 for ; Mon, 20 Jun 2016 17:52:31 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6E38EA7A3F3; Mon, 20 Jun 2016 17:52:31 +0000 (UTC) Delivered-To: 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 6DE26A7A3F0 for ; Mon, 20 Jun 2016 17:52:31 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mouf.net", Issuer "mouf.net" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 1FEF21D22; Mon, 20 Jun 2016 17:52:31 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from [0.0.0.0] (cpe-071-065-239-148.nc.res.rr.com [71.65.239.148] (may be forged)) (authenticated bits=0) by mouf.net (8.14.9/8.14.9) with ESMTP id u5KHq8Nx020135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 20 Jun 2016 17:52:26 GMT (envelope-from swills@FreeBSD.org) Subject: Re: Obsoleting Rails 3: how to handle different cases To: Torsten Zuehlsdorff References: <91f90dee-364b-ead4-2ab1-aa3b69ef755c@FreeBSD.org> From: Steve Wills Cc: "ruby@FreeBSD.org" Message-ID: <74f7f48e-e24d-0056-2ad4-e1341b1617c7@FreeBSD.org> Date: Mon, 20 Jun 2016 13:52:03 -0400 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.1.0 MIME-Version: 1.0 In-Reply-To: <91f90dee-364b-ead4-2ab1-aa3b69ef755c@FreeBSD.org> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3 (mouf.net [199.48.129.64]); Mon, 20 Jun 2016 17:52:26 +0000 (UTC) X-Spam-Status: No, score=2.6 required=4.5 tests=HELO_MISC_IP, RCVD_ILLEGAL_IP, RDNS_NONE autolearn=no autolearn_force=no version=3.4.1 X-Spam-Level: ** X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mouf.net X-Virus-Scanned: clamav-milter 0.99.1 at mouf.net X-Virus-Status: Clean X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Jun 2016 17:52:31 -0000 Hi, On 06/16/16 05:55 AM, Torsten Zuehlsdorff wrote: > Hello, > > while working on obsoleting Rails 3 from the ports, i stumble across > various unclear cases. For example: > > 1) how to handle different copies of an gem with different > rails-dependencies. For example www/rubygem-haml-rails and > www/rubygem-haml-rails-rails4. Both have the same function, but the > first is outdated. > Just remove the rails 3 one. We could rename the -rails4 ones as well, but then we'll have to change all the things that depend on them and it's not worth the effort. Besides, we're likely to hit the same issue with rails5 things so lets just be clear. > 2) how to handle ports which seems not to be required any more. > databases/rubygem-dm-* for example seems to be left alone and there is > no non-rubygem-port requiring this. I would set the complete tree of > ports to expiration in this case. > Up to you and probably best to handle on a case by case basis. For rubygem-dm-* specifically I'd mark it deprecated and if someone speaks up and wants to maintain it, fine. > 3) how to handle slaves? there were -rails4 ports which are purely > slaves to set the dependency to rails 4 instead of 3. Updating the > master to rails 4 dependency obsoletes the slave. I would prefer to: > update the master, obsolete the slave and switch dependencies of ports > from the slaves to the master. > He who does the work makes the rules. :) I'm OK with this too if you're willing to do the work of switching the dependencies. Question: Isn't Rails 3.x still at least updated for security issues (if any are found) until Rails 5 comes out? We'll probably want to add Rails 5 at some point. Steve