From owner-freebsd-ports  Tue Oct 31 14:44:17 2000
Delivered-To: freebsd-ports@freebsd.org
Received: from area51.slashnet.org (area51.slashnet.org [208.222.214.95])
	by hub.freebsd.org (Postfix) with ESMTP id 71BBC37B4C5
	for <ports@freebsd.org>; Tue, 31 Oct 2000 14:44:15 -0800 (PST)
Received: from edgemaster.zombie.org (edgemaster.creighton.edu [147.134.107.69])
	by area51.slashnet.org (Postfix) with ESMTP id DA62114D436
	for <ports@freebsd.org>; Tue, 31 Oct 2000 17:44:13 -0500 (EST)
Received: by edgemaster.zombie.org (Postfix, from userid 1001)
	id 99ED698A4; Tue, 31 Oct 2000 16:44:11 -0600 (CST)
Date: Tue, 31 Oct 2000 16:44:11 -0600
From: Sean Kelly <smkelly@zombie.org>
To: ports@freebsd.org
Subject: Roxen Challenger
Message-ID: <20001031164411.A22644@edgemaster.zombie.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
Sender: owner-freebsd-ports@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Seeing that ports will be frozen soon, I was wonderring if anyody was planning
on going through and either updating or deleting ports that are very much out
of date.  An example of this would be www/roxen.  The port is 1.3.111, while
the one available for download is 2.1.135.  That is very much out of date.
I believe I've asked about roxen in the past, and it's still not been updated.
As it is, I'm about to try the FreeBSD version that they offer at www.roxen.com
and bypass ports altogether, which is something I generally don't like to do.
I'm also curious how the PHP4 port will fit in with Roxen, as I know PHP
upports Roxen 2.

-- 
Sean Kelly <smkelly@zombie.org> or <smkelly@slashnet.org>
   PGP KeyID: 4AC781C7        http://www.sean-kelly.org


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ports" in the body of the message