Date: Sun, 21 Apr 2013 16:27:27 +0100 From: Chris Rees <crees@FreeBSD.org> To: Koichiro IWAO <meta@vmeta.jp>, Steve Wills <swills@freebsd.org> Cc: "ports@freebsd.org" <ports@freebsd.org>, portmgr-feedback@freebsd.org Subject: Re: FreeBSD unmaintained ports which are currently scheduled for deletion Message-ID: <CADLo839S9fEBOst30KuceEN1rX57wxQbjSbw-cX6h1C9Fz2hWw@mail.gmail.com> In-Reply-To: <2b6fbbeb6dcdfe29e3293e08aebf506e@vmeta.jp> References: <201304210829.r3L8TiFX032055@portsmonj.FreeBSD.org> <2b6fbbeb6dcdfe29e3293e08aebf506e@vmeta.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On 21 April 2013 11:55, Koichiro IWAO <meta@vmeta.jp> wrote: > 2013-04-21 17:30 に linimon@FreeBSD.org さんは書きました: >> >> portname: net-im/rubygem-termtter >> description: Terminal based Twitter client >> maintainer: dhn@FreeBSD.org >> >> deprecated because: Does not work with Ruby 1.9 >> expiration date: 2013-05-02 >> build errors: none. >> overview: >> >> http://portsmon.FreeBSD.org/portoverview.py?category=net-im&portname=rubygem-termtter > > > I strongly disagree to delete net-im/rubygem-termtter. > It is mismarked as BROKEN by portmgr for one year even if it perfectly works > with ruby 1.9. Don't worry, GNATS is checked before any ports are deleted; it won't go anywhere. Most of us have a load of commits queued during the hard freeze, and they haven't gone in yet. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo839S9fEBOst30KuceEN1rX57wxQbjSbw-cX6h1C9Fz2hWw>