From owner-freebsd-ports@FreeBSD.ORG Mon Jan 7 15:04:48 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 78642210 for ; Mon, 7 Jan 2013 15:04:48 +0000 (UTC) (envelope-from mi+thun@aldan.algebra.com) Received: from smtp02.lnh.mail.rcn.net (smtp02.lnh.mail.rcn.net [207.172.157.102]) by mx1.freebsd.org (Postfix) with ESMTP id 301C4F26 for ; Mon, 7 Jan 2013 15:04:47 +0000 (UTC) Received: from mr16.lnh.mail.rcn.net ([207.172.157.36]) by smtp02.lnh.mail.rcn.net with ESMTP; 07 Jan 2013 10:04:47 -0500 Received: from smtp01.lnh.mail.rcn.net (smtp01.lnh.mail.rcn.net [207.172.4.11]) by mr16.lnh.mail.rcn.net (MOS 4.3.4-GA) with ESMTP id CED96550; Mon, 7 Jan 2013 10:04:46 -0500 X-Auth-ID: anat Received: from pool-173-70-92-11.nwrknj.fios.verizon.net (HELO [192.168.1.8]) ([173.70.92.11]) by smtp01.lnh.mail.rcn.net with ESMTP; 07 Jan 2013 10:04:47 -0500 Message-ID: <50EAE40E.5090300@aldan.algebra.com> Date: Mon, 07 Jan 2013 10:04:46 -0500 From: "Mikhail T." User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120820 Thunderbird/14.0 MIME-Version: 1.0 To: Kimmo Paasiala Subject: Re: Why delete KDE3 ports? References: <50EADA33.9010308@aldan.algebra.com> <50EADEFA.2070201@marino.st> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: John Marino , freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2013 15:04:48 -0000 On 07.01.2013 09:54, Kimmo Paasiala wrote: > Are you willing to step up as the maintainer of the KDE3 ports? Or > anyone else reading this? The situation with ports like KDE3 is that > they are lots of work to keep up in shape and if no one wants to > maintain them they succumb to what is called "bitrot" very quickly > when something changes in dependent ports or in the base system. When/if that happens, we can renew the conversation. For the time being there are no build errors. -mi