From owner-freebsd-ports@FreeBSD.ORG  Thu Nov 30 21:01:00 2006
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@freebsd.org
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id A066316A415
	for <freebsd-ports@freebsd.org>; Thu, 30 Nov 2006 21:01:00 +0000 (UTC)
	(envelope-from pankov_p@mail.ru)
Received: from mx5.mail.ru (mx5.mail.ru [194.67.23.25])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6782A43CCD
	for <freebsd-ports@freebsd.org>; Thu, 30 Nov 2006 21:00:50 +0000 (GMT)
	(envelope-from pankov_p@mail.ru)
Received: from [80.71.243.234] (port=62214 helo=[172.16.1.13])
	by mx5.mail.ru with asmtp 
	id 1Gpt1e-000BAr-00; Fri, 01 Dec 2006 00:00:58 +0300
Message-ID: <456F4684.3050104@mail.ru>
Date: Fri, 01 Dec 2006 00:00:52 +0300
From: Pankov Pavel <pankov_p@mail.ru>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: freebsd-ports@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: net-p2p/microdc: port is no longer in development, but there is a
 successor
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Nov 2006 21:01:00 -0000

The port net-p2p/microdc is no longer in development and it's author 
recommends to use more functional and supported fork called microdc2 
instead (see http://www.nongnu.org/microdc/ and 
http://corsair626.no-ip.org/microdc/).

I'm currently the maintainer of net-p2p/microdc and like to move to 
microdc2, but I don't know how to be with the port. I can see several 
posibilities:
1) net-p2p/microdc can be simply updated to microdc2's latest version 
(IMO it's bad: package/port name would be microdc instead of logical 
microdc2)
2) net-p2p/microdc can be repo-copied to something like 
net-p2p/microdc2, which later will be updated to microdc2's latest version
3) add new port net-p2p/microdc2 with the microdc2 fork (and 
net-p2p/microdc can be optionally marked as depriciated in favour of 
net-p2p/microdc2)

As for me, I prefer the 3) variant, but I'm sure this isn't the first 
dead project and there is some examples that should be done in such cases.