Date: Wed, 16 Mar 2011 13:42:20 -0700 From: Stanislav Sedov <stas@FreeBSD.org> To: milki <milki@rescomp.berkeley.edu> Cc: ruby@FreeBSD.org Subject: Re: making Ruby 1.9 default Message-ID: <20110316134220.d92eb20d.stas@FreeBSD.org> In-Reply-To: <20110316160048.GM32667@hal.rescomp.berkeley.edu> References: <1300272269.1973.16.camel@localhost> <C9A64EB6.1DFF2%freebsdlists-ruby@chillibear.com> <20110316160048.GM32667@hal.rescomp.berkeley.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Mar 2011 09:00:48 -0700 milki <milki@rescomp.berkeley.edu> mentioned: > 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. > It's not true, it's officially maintained by ruby@, which for portupgrade was effectively mainly me for the past years. Unfortunately, I don't have enough resources to make significant changes there. -- Stanislav Sedov ST4096-RIPE () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110316134220.d92eb20d.stas>