Date: Tue, 06 Sep 2011 09:44:50 +0400 From: Ruslan Mahmatkhanov <cvs-src@yandex.ru> To: wen heping <wenheping@gmail.com> Cc: FreeBSD Ports Mailing List <ports@freebsd.org>, neal@nelson.name Subject: Re: Maintainership of py-zopetesting and py-zopeevent Message-ID: <4E65B352.3030504@yandex.ru> In-Reply-To: <CACi7718digBBkknROiiMXWKHj9J1dx7jZ_VRGD3Q-Pi6fpLDtQ@mail.gmail.com> References: <4E64C077.8050403@yandex.ru> <CACi7718digBBkknROiiMXWKHj9J1dx7jZ_VRGD3Q-Pi6fpLDtQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
wen heping wrote on 06.09.2011 03:35: > 2011/9/5 Ruslan Mahmatkhanov<cvs-src@yandex.ru>: >> Good day. >> >> I want to grab maintainership of this ports: >> >> devel/py-zopetesting >> devel/py-zopeevent >> net/py-zopeproxy > > Now these 3 ports is yours. > > Would you send a PR of repocopy to rename these ports? > > Thanks. > > wen Thanks. Done. http://bugs.freebsd.org/160499 http://bugs.freebsd.org/160501 http://bugs.freebsd.org/160503 > > > >> >> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E65B352.3030504>