From owner-freebsd-ports@FreeBSD.ORG  Thu May 22 23:56:56 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 209CB37B401; Thu, 22 May 2003 23:56:56 -0700 (PDT)
Received: from mail.lovett.com (sentinel.ranger.supernews.net [216.168.1.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 7E2DF43F85; Thu, 22 May 2003 23:56:55 -0700 (PDT)
	(envelope-from ade@lovett.com)
Received: from cs666853-113.austin.rr.com ([66.68.53.113] helo=lovett.com)
	by mail.lovett.com with asmtp (Exim 4.14)
	id 19J6U3-000NtW-5I; Fri, 23 May 2003 06:56:55 +0000
Date: Fri, 23 May 2003 01:57:00 -0500
Content-Type: text/plain; charset=US-ASCII; format=flowed
Mime-Version: 1.0 (Apple Message framework v552)
To: Jens Rehsack <rehsack@liwing.de>
From: Ade Lovett <ade@lovett.com>
In-Reply-To: <3ECDC42E.9040603@liwing.de>
Message-Id: <C09E5BCE-8CEB-11D7-AAF8-000A956B6386@lovett.com>
Content-Transfer-Encoding: 7bit
X-Mailer: Apple Mail (2.552)
cc: ports@FreeBSD.org
cc: Alex Dupre <sysadmin@alexdupre.com>
cc: Dirk Froemberg <dirk@FreeBSD.org>
cc: Doug Barton <DougB@FreeBSD.org>
cc: Kris Kennaway <kris@obsecurity.org>
Subject: Re: HEADS UP: Ports are now frozen
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
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: Fri, 23 May 2003 06:56:56 -0000


On Friday, May 23, 2003, at 01:48 US/Central, Jens Rehsack wrote:
> I ask how is a situation managed when a port patially breaks with
> the base system but the ports tree is frozen. Because of the new
> OpenSSL, mod_php4 in version 4.3.1 won't build with OpenSSL, but
> the upcoming 4.3.2 will do. The php-4.3.2RC4 is out and the
> 4.3.2-RELEASE will come in next 1-3 weeks. Can this port becomes
> committed whether the ports tree is frozen or not or should it marked
> as broken when OpenSSL is used?

Umm.

builder 1% cd /usr/ports/www/mod_php4 && make -V PORTVERSION
4.3.2.r4

So we're at 4.3.2RC4 right now (which works just fine as far as
I can tell).

Regarding the upcoming 4.3.2-RELEASE, it'll surely get committed
as and when it's available.  Unfortunately, with 8700+ ports in
the tree, trying to co-ordinate releases of 3rd party code with
FreeBSD releases is effectively impossible.  Pretty much every time
a FreeBSD release is rolled, there's always one or two ports that
have their own release updates just around the corner.

-aDe