From owner-freebsd-ports@FreeBSD.ORG  Mon Nov  2 06:03:07 2009
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 4A4D51065694
	for <freebsd-ports@freebsd.org>; Mon,  2 Nov 2009 06:03:07 +0000 (UTC)
	(envelope-from rea-fbsd@codelabs.ru)
Received: from 0.mx.codelabs.ru (0.mx.codelabs.ru [144.206.177.45])
	by mx1.freebsd.org (Postfix) with ESMTP id F0AB08FC1A
	for <freebsd-ports@freebsd.org>; Mon,  2 Nov 2009 06:03:06 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=codelabs.ru; s=two; h=Date:From:To:Subject:Message-ID:Reply-To:
	MIME-Version:Content-Type:Sender; bh=65P8mUlqrqH7LbEpOraGnPod+uL
	ee4pammBn/Sv1PSo=; b=AZwATh8CgS9kEQkBYCeL5EaVvyWi9GhlTsxO11IUuuV
	orfhgdCEKtHLCw9QrTaWEGj1ZJD11bfC4SfZ6XIluzWdOJZZH5BX+QOHy/VIyidg
	PhmUPdYSBOal9Vzv8xbZFNoyR3qlcdZVybnMo8s7R0U0ZcUYMcPmTagghguPAk74
	fyYMw86jVIK/El3fw2hdIFeibgdTzzJHbKtYWQahmgSp1Ir3vtglfgUN+eSJ8V/v
	ssLiBLXxJwgb2q3JaY8mogg4AXnjOz9Ezwz1LiyOgHpBLvTO4KFWs5eHGtWNet7m
	yfHiFSJOaS8xQrKdFH++wXFzlKiRrWsTEmZ0MPTlbfg==
Received: from void.codelabs.ru (void.codelabs.ru [144.206.177.25])
	by 0.mx.codelabs.ru with esmtpsa (TLSv1:AES256-SHA:256)
	id 1N4pqI-000JfX-0h for freebsd-ports@freebsd.org;
	Mon, 02 Nov 2009 08:52:38 +0300
Date: Mon, 2 Nov 2009 08:52:35 +0300
From: Eygene Ryabinkin <rea-fbsd@codelabs.ru>
To: freebsd-ports@freebsd.org
Message-ID: <YeZ0UD/3YXhjDo1EpRG5kb3dBd4@m7CpruDFVVXtHTpJF1FPSUwA+UQ>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Sender: rea-fbsd@codelabs.ru
Subject: Renaming port when it forks to two different branches
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: rea-fbsd@codelabs.ru
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: Mon, 02 Nov 2009 06:03:07 -0000

Good day.

I am maintaining net-mgmt/pnp and it was recently brought to my
attention that the current port development line (0.4.x) will cease in
some time and now we have 0.6.x that is better, will be supported and
developed further.  But it requires PHP >= 5.2.  I am planning to
upgrade the net-mgmt/pnp to 0.6.x and make request to repocopy the
current (0.4.x-based) port to net-mgmt/pnp-legacy.

Here comes a question: does anyone sees any drawbacks from such
a plan and may be there are better ways to do it?

Thanks!
-- 
Eygene
 _                ___       _.--.   #
 \`.|\..----...-'`   `-._.-'_.-'`   #  Remember that it is hard
 /  ' `         ,       __.--'      #  to read the on-line manual
 )/' _/     \   `-_,   /            #  while single-stepping the kernel.
 `-'" `"\_  ,_.-;_.-\_ ',  fsc/as   #
     _.-'_./   {_.'   ; /           #    -- FreeBSD Developers handbook
    {_.-``-'         {_/            #