Maintainership of py-zopetesting and py-zopeevent

[wen heping]

2011/9/5 Ruslan Mahmatkhanov <cvs-src at 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



>
> 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.
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"
>