From owner-svn-ports-head@FreeBSD.ORG Fri Mar 7 09:24:08 2014 Return-Path: Delivered-To: svn-ports-head@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1033) id 1D129658; Fri, 7 Mar 2014 09:24:08 +0000 (UTC) Date: Fri, 7 Mar 2014 09:24:08 +0000 From: Alexey Dokuchaev To: Martin Wilke Subject: Re: svn commit: r347338 - in head/net-p2p: . microdc2 microdc2/files Message-ID: <20140307092408.GA3390@FreeBSD.org> References: <201403070625.s276PGbO062948@svn.freebsd.org> <20140307090840.GB98331@FreeBSD.org> <7A2A804C-B978-4259-9945-27A764EC9AB7@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7A2A804C-B978-4259-9945-27A764EC9AB7@gmail.com> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: "svn-ports-head@FreeBSD.org" , "svn-ports-all@FreeBSD.org" , ports-committers@freebsd.org X-BeenThere: svn-ports-head@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: SVN commit messages for the ports tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Mar 2014 09:24:08 -0000 On Fri, Mar 07, 2014 at 05:12:46PM +0800, Martin Wilke wrote: > Next time you may ask first, the reason is the port got removed for reason, > so if its end up soon or later with ports@ it would have been better to let > it in attic :). Well, this is one of the problem with ports@: it doesn't always mean "not maintained". Sometimes I give my ports to fly solo just because I am quite confident that it's hard to damage them, and do not mind if someone else would update it to next version or something before I have a chance. microdc2 is useful port; and given how easy it was to unbreak it, I don't understand how could it possibly slip into abyss in the first place. :( This is why I generally do not support deprecation due to compile failure. ./danfe