From owner-freebsd-python@FreeBSD.ORG Mon Sep 5 14:18:56 2011 Return-Path: Delivered-To: python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9598C106564A; Mon, 5 Sep 2011 14:18:56 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward13.mail.yandex.net (forward13.mail.yandex.net [IPv6:2a02:6b8:0:801::3]) by mx1.freebsd.org (Postfix) with ESMTP id 9E0988FC13; Mon, 5 Sep 2011 14:18:55 +0000 (UTC) Received: from smtp11.mail.yandex.net (smtp11.mail.yandex.net [95.108.130.67]) by forward13.mail.yandex.net (Yandex) with ESMTP id 308E1142444; Mon, 5 Sep 2011 18:18:54 +0400 (MSD) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1315232334; bh=VsFQTJTQnj7PRMUq2ZIO8Zg+z/3ndbBXMkMRZY+YQ7o=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:References: In-Reply-To:Content-Type:Content-Transfer-Encoding; b=N1noyN9LCi+lELu6zNded+W9swxHSMSXi1odAO3uogygt3Fm4lm8I4lO2H8i7Y0MM 996AAOldEjGTcecscOOzbiYNpOXY5lXNFKy9XGZdWBAdYArDP+XM0LGbUhNcEWAEbe EEkL+duyw6WG+nwOtfozIOSQSNRgAkBDgp2XF9eE= Received: from smtp11.mail.yandex.net (localhost [127.0.0.1]) by smtp11.mail.yandex.net (Yandex) with ESMTP id DE4167E03E2; Mon, 5 Sep 2011 18:18:53 +0400 (MSD) Received: from unknown (unknown [213.27.65.65]) by smtp11.mail.yandex.net (nwsmtp/Yandex) with ESMTP id IrEuWrAL; Mon, 5 Sep 2011 18:18:53 +0400 X-Yandex-Spam: 1 Message-ID: <4E64DA46.4000408@yandex.ru> Date: Mon, 05 Sep 2011 18:18:46 +0400 From: Ruslan Mahmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:6.0) Gecko/20110828 Thunderbird/6.0 MIME-Version: 1.0 To: wen heping References: <4E64C077.8050403@yandex.ru> <4E64D5C4.4030706@yandex.ru> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: python@freebsd.org, Li-Wen Hsu , Martin Wilke Subject: Re: Maintainership of py-zopetesting and py-zopeevent X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 14:18:56 -0000 wen heping wrote on 05.09.2011 18:08: > 2011/9/5 Ruslan Mahmatkhanov: >> Hi, Wen. >> >> wen heping wrote on 05.09.2011 17:34: >>> >>> Hi,Ruslan: >>> >>> Do you have the plan to import Zope-2.13 into portstree? >> >> Yes, i am. But work on Zope2.13 and Plone4 is still underway. >> >>> >>> I could run zope-2.13 on FreeBSD correctly with python-2.7, but >>> many new ports should be created if we import zope-2.13. >> >> Yes, here is all of them: >> http://happy-nation.by.ru/ports/zope-deps.tar.gz > > > Seems we have done many duplicate work. > > >> >> Please note that this is just zope deps, plone4 will push many of new ports >> too. >> >>> >>> If you have the plan, give me a message and I am intersting of it. >>> >>> wen >> >> The plan is: >> 1. Commit this two guys: ports/159962 and ports/160434. > > I shall look into these. > > >> 2. I'd prefer to create physical category like `webdevel` and >> move all zope-specific ports there (and all of this django, pyramid, >> pylons, turbogears stuff) to not trash the tree (mainly devel category). > > > I do not believe portmgr@ shall agree with this. Better discuss it > with miwi@ first. It's preferable from my POV, but i'm not insist. >> 3. Rename 4 existing zope ports for consistency. > > I agree with this. > > > >> 4. Push all the dependend ports mentioned before (over 50) to the tree. > > Shall we add these new ports one by one? > I remember it is a hard work to deal with the depend relation, so it > is difficult to add so many new ports at one time. While correct import path may be created, i think that better way - to commit them all, but connect them to Makefile's only after all the dependend ports will be there. This should not break anything as far i understand. > > BTW: I forward this mail to miwi@, lwshu@,python@. > > wen > > > >> 5. Import zope 2.13 and plone4 (i think to www/zope and www/plone, because> they are the only supported versions atm) >> 6. Deprecate old zope/plone ports in three months >> 7. PROFIT >> >> Something like that, but i'm sure there may be some hidden or non-technical >> problems. Surely, after that and after handling remaining >> elementtree/pysqlite2x pr's, we can finally retire python24. >> >>> >>> 2011/9/5 Ruslan Mahmatkhanov: >>>> >>>> Good day. >>>> >>>> I want to grab maintainership of this ports: >>>> >>>> devel/py-zopetesting >>>> devel/py-zopeevent >>>> net/py-zopeproxy >>>> >>>> But i want them to be renamed to py-zope.testing, py-zope.event and >>>> py-zope.proxy respectively to match upstream projectnames and to >>>> consistency >>>> with other current and upcoming zope ports. Is this reasons sounds enough >>>> to >>>> make a repocopy of them? This change is purely cosmetic but will also >>>> ease >>>> maintainership a bit (Makefile vars like DISTNAME etc will not need to be >>>> redefined), but this will require to fix dependencies in all the ports >>>> that >>>> required it. I'm looking forward to your suggestion before sending pr's. >>>> Thanks. >>>> >>>> PS. It would be logical to rename devel/py-zopeInterface to >>>> py-zope.interface too, but this port is maintained and i'm not sure if >>>> maintainer (cc'ed) wishes such change. -- Regards, Ruslan Tinderboxing kills... the drives.