Date: Fri, 7 Mar 2014 09:24:08 +0000 From: Alexey Dokuchaev <danfe@FreeBSD.org> To: Martin Wilke <miwi.fbsd@gmail.com> Cc: "svn-ports-head@FreeBSD.org" <svn-ports-head@freebsd.org>, "svn-ports-all@FreeBSD.org" <svn-ports-all@freebsd.org>, ports-committers@freebsd.org Subject: Re: svn commit: r347338 - in head/net-p2p: . microdc2 microdc2/files Message-ID: <20140307092408.GA3390@FreeBSD.org> In-Reply-To: <7A2A804C-B978-4259-9945-27A764EC9AB7@gmail.com> References: <201403070625.s276PGbO062948@svn.freebsd.org> <CAFY%2ByE=w9rvhzdcC8q2tZvyFQrFQMrxjQ1W7JG4s1rsf-kvtnA@mail.gmail.com> <20140307090840.GB98331@FreeBSD.org> <7A2A804C-B978-4259-9945-27A764EC9AB7@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140307092408.GA3390>