From owner-freebsd-ports@FreeBSD.ORG Mon Sep 8 20:17:46 2008 Return-Path: Delivered-To: ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 637E7106566C; Mon, 8 Sep 2008 20:17:46 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from mail.ipt.ru (mail.ipt.ru [194.62.233.102]) by mx1.freebsd.org (Postfix) with ESMTP id 1E8958FC18; Mon, 8 Sep 2008 20:17:46 +0000 (UTC) (envelope-from bsam@ipt.ru) Received: from sp34.ipt.ru ([194.62.233.107] helo=bs1.sp34.ru) by mail.ipt.ru with esmtp (Exim 4.62 (FreeBSD)) (envelope-from ) id 1KcmlG-000KkL-Qm; Mon, 08 Sep 2008 23:50:58 +0400 Received: from bsam by bs1.sp34.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1Kcmlo-0000Oo-H5; Mon, 08 Sep 2008 23:51:32 +0400 To: Giorgos Keramidas References: <20080908120124.GK23062@droso.net> <87od2y30xp.fsf@kobe.laptop> From: Boris Samorodov Date: Mon, 08 Sep 2008 23:51:32 +0400 In-Reply-To: <87od2y30xp.fsf@kobe.laptop> (Giorgos Keramidas's message of "Mon\, 08 Sep 2008 22\:14\:10 +0300") Message-ID: <70828971@bs1.sp34.ru> User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: ports@freebsd.org Subject: Re: HEADS UP: Ports freeze for 6.4 and 7.0 in effect X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Sep 2008 20:17:46 -0000 Giorgos Keramidas writes: > On Mon, 8 Sep 2008 14:01:25 +0200, Erwin Lansing wrote: >> In preparation for both the 6.4 and 7.1 releases, the ports tree has >> been frozen. All commits have to be approved by portmgr. See the >> portmgr webpage[1] for more information about what is and isn't >> allowed during the freeze. We are aiming for a short freeze period, >> so we will be quite strict in allowing commits during the freeze. Of >> course, we do appreciate any help fixing existing errors in the tree, >> so if anyone is bored, a good starting point will be portsmon[2]. > > Damn :/ > > My emacs-22.3 release update almost made it into ports before the freeze > by 1-2 days. Is there any chance I could bribe you guys to get it in, > so we can have the latest stable 22.X GNU Emacs in the release? > > Having said that, I am a bit unfamiliar with all the work port builders > have to do during the freeze, so if getting a new Emacs in the tree is > completely out of the question because it would create a lot of work for > you guys, that's ok. > > On the other hand, if the ports stay frozen for several weeks and we > still have time to let it settle into the tree, it would be very nice to > include this version. It includes a mildly important fix in the way > Emacs spawns Python processes[1] that would be _very_ nice to have in > ports sooner, rather than a couple of months later. > > http://lists.gnu.org/archive/html/emacs-devel/2008-09/msg00215.html Since it is a security issue it may be resolved before release. Just the patch should be polished a little. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD committer, http://www.FreeBSD.org The Power To Serve