From owner-freebsd-ruby@FreeBSD.ORG Wed Mar 16 16:17:45 2011 Return-Path: Delivered-To: ruby@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF8FD106564A for ; Wed, 16 Mar 2011 16:17:45 +0000 (UTC) (envelope-from milki@rescomp.berkeley.edu) Received: from hal.rescomp.berkeley.edu (hal.Rescomp.Berkeley.EDU [169.229.70.150]) by mx1.freebsd.org (Postfix) with ESMTP id AEB168FC19 for ; Wed, 16 Mar 2011 16:17:45 +0000 (UTC) Received: by hal.rescomp.berkeley.edu (Postfix, from userid 1070) id 1A6C2119DD5; Wed, 16 Mar 2011 09:00:49 -0700 (PDT) Date: Wed, 16 Mar 2011 09:00:48 -0700 From: milki To: Eric Message-ID: <20110316160048.GM32667@hal.rescomp.berkeley.edu> References: <1300272269.1973.16.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ruby@FreeBSD.org Subject: Re: making Ruby 1.9 default X-BeenThere: freebsd-ruby@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Ruby discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Mar 2011 16:17:45 -0000 On 11:25 Wed 16 Mar , Eric wrote: > There are plenty of outstanding PRs regarding portupgrade, which does seem > to suffer from being both loved and unloved (in terms of maintenance). I > personally use it, but am wondering if it's time to switch to Doug's > PortMaster now... However given that portupgrade is often noted in > documentation as almost the default tool for doing upgrades of ports then it > does seem sensible that we should all try our best to fix it. I've been hanging out at #bsdports@efnet and I've gathered that is the consensus of committers that portupgrade is no longer maintained and portmaster is the preferred tool. The docs need some patching to reflect this. -- milki