From owner-freebsd-ports@FreeBSD.ORG  Wed Feb 26 17:36:07 2014
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 4DA98351
 for <ports@freebsd.org>; Wed, 26 Feb 2014 17:36:07 +0000 (UTC)
Received: from beefree.free.de (beefree.free.de [91.204.4.132])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 8AE6C1373
 for <ports@freebsd.org>; Wed, 26 Feb 2014 17:36:05 +0000 (UTC)
Received: (qmail 98883 invoked by uid 23); 26 Feb 2014 18:35:55 +0100
Message-ID: <20140226173555.98882.qmail@beefree.free.de>
Date: Wed, 26 Feb 2014 18:35:55 +0100
From: Johannes 5 Joemann <joemann@beefree.free.de>
To: FreeBSD ports <ports@freebsd.org>
Subject: Will net/xorp be deleted tomorrow (in spite of PR ports/186982)?
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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: Wed, 26 Feb 2014 17:36:07 -0000

Hi all,

will net/xorp, which is marked for deletion ...

PORTNAME=	xorp
PORTVERSION=	1.6
[...]
MAINTAINER=	ports@FreeBSD.org
COMMENT=	The eXtensible Open Router Platform
[...]
BROKEN=         Does not build
DEPRECATED=	Broken for more than 6 month
EXPIRATION_DATE=	2014-02-27

... be removed automagically? Tomorrow? Whom should I contact to
prevent its deletion, be it automatic or manual?

The reason for asking is that xorp 1.8.5 works fine for me (on 10.0 and
9.2) using the patch from my PR ports/186982 [1]. So it would be sad if
net/xorp vanished just because no committer has had the time to take
that PR yet.

Sorry if I've missed the appropriate documentation. The most specific
text about my question that I found was from portmgr's QA section:

"Ports that have been marked BROKEN for some time are marked DEPRECATED
(with an EXPIRATION_DATE) and then are removed if no one has fixed them
by that time." [2]

Any hints are appreciated, thank you!
Johannes

ps And so is feedback from other users of xorp (e.g. net/xorp-devel),
  if they still exist;-)

[1] <http://www.freebsd.org/cgi/query-pr.cgi?pr=186982>
[2] <http://www.freebsd.org/portmgr/qa.html>