HEADS UP: Ports are now frozen

[Ade Lovett]

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