From owner-freebsd-ports@FreeBSD.ORG Fri May 23 10:50:26 2003 Return-Path: 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 4A94837B401 for ; Fri, 23 May 2003 10:50:26 -0700 (PDT) Received: from mail.dt.e-technik.uni-dortmund.de (krusty.dt.E-Technik.Uni-Dortmund.DE [129.217.163.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1352D43FAF for ; Fri, 23 May 2003 10:50:25 -0700 (PDT) (envelope-from ma@dt.e-technik.uni-dortmund.de) Received: from m2a2.dyndns.org (krusty.dt.e-technik.uni-dortmund.de [129.217.163.1])D7923A381D for ; Fri, 23 May 2003 19:50:23 +0200 (CEST) Received: by merlin.emma.line.org (Postfix, from userid 500) id 40970829B3; Fri, 23 May 2003 19:50:21 +0200 (CEST) To: Jens Rehsack In-Reply-To: <3ECDC42E.9040603@liwing.de> (Jens Rehsack's message of "Fri, 23 May 2003 08:48:14 +0200") References: <20030523035931.GA44629@rot13.obsecurity.org> <3ECDBAB7.80005@liwing.de> <20030523062705.GA45408@rot13.obsecurity.org> <3ECDC1A4.6000502@liwing.de> <20030523064250.GA59823@rot13.obsecurity.org> <3ECDC42E.9040603@liwing.de> From: Matthias Andree Date: Fri, 23 May 2003 19:50:21 +0200 Message-ID: User-Agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: ports@freebsd.org cc: Alex Dupre cc: Doug Barton cc: Kris Kennaway 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 May 2003 17:50:26 -0000 Jens Rehsack writes: > 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? Well, the ports freeze is meant to stabilize ports that ship with FreeBSD 5.1-RELEASE to give a somewhat stable collection of packages, rather than a snapshot with a lot of ports broken. This does NOT imply that the port is never updated after that. I myself have committed bogofilter 0.13.0 + FreeBSD-specific fixes because bogofilter 0.13.1 would not have made FreeBSD 5.1 in time, and the features of this beta-state software in 0.13.0 have been requested by many and have had some testing already, so this was hopefully a safe bet (no complaints yet). Same with PHP: 4.3.2r4 is in the ports, and appears to be good enough. _critical_ fixes will be accepted into the ports tree if you ask the right person (who is authorized to commit during freeze, likely this takes release engineer or portsmgr approval or something), but if it is not broken, now is _not_ the time to change it. -- Matthias Andree