From owner-freebsd-zope@FreeBSD.ORG Mon May 28 18:51:25 2012 Return-Path: Delivered-To: zope@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D7D6106566B; Mon, 28 May 2012 18:51:25 +0000 (UTC) (envelope-from lwhsu.freebsd@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id ABB3B8FC16; Mon, 28 May 2012 18:51:24 +0000 (UTC) Received: by vcbfy7 with SMTP id fy7so2042003vcb.13 for ; Mon, 28 May 2012 11:51:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=TNj9EFDx5KE+1OOVjrW6z8xy+4dC+FNCAH59sMb1YN4=; b=TOt95SBRXomd9/ma4/i4Wf8KbMkkstxHO0n66UmgoENnHUi414qhcXoFlTktHZM7G0 iIFAacqYnLSuVrW6oBXEq1lgmIuM3ReSWm+FMspNlZRQ1ZpMVVxb01gJw88RkhgrpnIF MFqIYE4++0w/Ve4XRO/VqxSubm0CyibtP0lr+DmXNppnvswdnAR7o46/Ab8bpYbuQXGo sSoKgLtSojZ07s7z8gvvqIbcIHKmcP2w4o32aKxlDpCqkG+H3GFiHjnn2Tpla/Eh0sa0 cPeI7Zr/xmHl9ZLfPDQ3DlNC1Et0yi/UYmEzy365zcysb6R4BSqnz2MpsW7JNkt3CdSu UJfA== MIME-Version: 1.0 Received: by 10.52.27.244 with SMTP id w20mr8208472vdg.67.1338231083729; Mon, 28 May 2012 11:51:23 -0700 (PDT) Sender: lwhsu.freebsd@gmail.com Received: by 10.220.7.82 with HTTP; Mon, 28 May 2012 11:51:23 -0700 (PDT) In-Reply-To: <4FC3B25A.2020004@yandex.ru> References: <20120528174458.5300cfbd.miwi@FreeBSD.org> <4FC3B25A.2020004@yandex.ru> Date: Tue, 29 May 2012 02:51:23 +0800 X-Google-Sender-Auth: ll07MWHz6x4rBWyoiREgZNMH3Ao Message-ID: From: Li-Wen Hsu To: Ruslan Mahmatkhanov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: skreuzer@FreeBSD.org, zope@freebsd.org, python@freebsd.org Subject: Re: [PATCH] python2.4 removal zope and zope211 affected X-BeenThere: freebsd-zope@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Zope for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2012 18:51:25 -0000 Hi, On Tue, May 29, 2012 at 1:14 AM, Ruslan Mahmatkhanov wr= ote: > Hi, Martin, > > Martin Wilke wrote on 28.05.2012 13:44: > >> Hi, >> >> Finally I'm working on to remove python 24 from the ports tree, and the >> reasons are clear. Support was dropped by 2008, and there are a lot of >> unpatched security holes. We have warned about this since 2 years ago, >> and now I will really take action to drop it from the ports tree. > > I have no objections, but know people that do :). I ever know FreeBSD > committer that using old zope. I apologies jumping to conclusion too quick, and totally forget about setti= ng DEPRECATED thing. I agree to set it as an official announcement, and we ca= n wait another month, I believe this is the final time of postpone. > We have only three ports, that wish exactly python 2.4 version: > > net/honeyd (skreuzer@FreeBSD.org) > www/zope =C2=A0 (estartu@augusta.de) > www/zope211 (estartu@augusta.de) miwi has written a mail to estartu@augusta.de, I am not sure about if skreuzer (CC'd) know this plan. www/zope and www/zope211 can also be set deprecated, how about net/honeyd? can it work with newer Python? I looked at the project site, it seems move= d to somewhere else. > And only one port that depends on exact 2.5 version: > > www/google-appengine (nivit@FreeBSD.org) I think we don't have a exact plan to remove 2.5 currently, do we? > I prefer to remove both of python24 and python25 because they both EOL. B= ut > I'd still set them all to expiration period of month or two. We have such= a > tradition. I agree to remove python24, and not object to remove python25, newer google-appengine can run with python27 and I would like to use python27 to develop new system, and users have python25 apps deployed are not affected. Is there anybody still using develop/maintaining systems with python25 on appengine? >> So here is the final patch [1] that has already been reviewed by lwshu@ >> and wen@, but I would like to discuss regarding the zope ports. >> >> First of all I will clean up the zope version from the bsd.python.mk. >> Now I would like to know what you guys think if I were to remove >> www/zope and keep www/zope213. Another option is to merge www/zope213 >> to www/zope and just remove www/zope211 and www/zope213 completely. >> What do you think about this? >> >> Thanks Martin >> >> [1] >> http://miwifbsd.dyndns.org/patches/py24rm-3.diff > > > > Our zope213 port didn't use ZOPESKELDIR, SZOPEBASEDIR so it may look like > this: > > +if ${ZOPE_VERSION} =3D=3D "2.13" > +ZOPE_PORTSDIR=3D =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= ${PORTSDIR}/www/zope213 > =C2=A0.else You are the Zope expert! > I prefer to keep it as zope213 for some time. We do, too. Do you have a plan for updating www/zope to 2.13? BTW, what's the status of BlueBream? Thanks, Li-Wen --=20 Li-Wen Hsu http://lwhsu.org