From owner-freebsd-ruby@freebsd.org  Thu Jun 16 09:55:07 2016
Return-Path: <owner-freebsd-ruby@freebsd.org>
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 8B131A475A5
 for <freebsd-ruby@mailman.ysv.freebsd.org>;
 Thu, 16 Jun 2016 09:55:07 +0000 (UTC) (envelope-from tz@FreeBSD.org)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 7B2EE1CB3
 for <freebsd-ruby@freebsd.org>; Thu, 16 Jun 2016 09:55:07 +0000 (UTC)
 (envelope-from tz@FreeBSD.org)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 7A903A475A4; Thu, 16 Jun 2016 09:55:07 +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 7A3A3A475A3
 for <ruby@mailman.ysv.freebsd.org>; Thu, 16 Jun 2016 09:55:07 +0000 (UTC)
 (envelope-from tz@FreeBSD.org)
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 4A3F61CB2
 for <ruby@freebsd.org>; Thu, 16 Jun 2016 09:55:07 +0000 (UTC)
 (envelope-from tz@FreeBSD.org)
Received: from [0.0.0.0] (mail.toco-domains.de [IPv6:2a01:4f8:150:50a5::6])
 by toco-domains.de (Postfix) with ESMTPA id 9161C1AAF017
 for <ruby@freebsd.org>; Thu, 16 Jun 2016 11:55:05 +0200 (CEST)
To: ruby@freebsd.org
From: Torsten Zuehlsdorff <tz@FreeBSD.org>
Subject: Obsoleting Rails 3: how to handle different cases
Message-ID: <91f90dee-364b-ead4-2ab1-aa3b69ef755c@FreeBSD.org>
Date: Thu, 16 Jun 2016 11:55:05 +0200
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101
 Thunderbird/45.1.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ruby>,
 <mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby/>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
 <mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Jun 2016 09:55:07 -0000

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.

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.

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.

What is your opinion?

Greetings,
Torsten