Date: Tue, 19 Jun 2001 03:50:06 -0700 (PDT) From: Johann Visagie <johann@egenetics.com> To: freebsd-ports@FreeBSD.org Subject: Re: ports/27955: Update & New port : net/py-xmlrpc and net/py-fastxmlrpc Message-ID: <200106191050.f5JAo6E73545@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/27955; it has been noted by GNATS. From: Johann Visagie <johann@egenetics.com> To: perky@python.or.kr Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: ports/27955: Update & New port : net/py-xmlrpc and net/py-fastxmlrpc Date: Tue, 19 Jun 2001 12:44:21 +0200 perky@python.or.kr on 2001-06-08 (Fri) at 01:05:56 -0700: > > I think it's rather to move that ports. like this: > net/py-xmlrpc -> net/py-fastxmlrpc > PythonWare's -> net/py-xmlrpc To recap and clarify: - Your port of the (fast) Sourceforge-based project has been committed from PR 26769 as net/py-xmlrpc. - My suggested port of the (more general) PythonWare project in PR 27737 has NOT YET been committed as net/py-xmlrpclib. You're suggesting: - Change net/py-xmlrpc to become a port of the PythonWare project. - Commit a new port of the Sourceforge project as net/py-fastxmlrpc. This doesn't really correspond to "how things are done" in ports, methinks. IF you're particularly keen on the name change, then the procedure should probably be: - Ask for a repo copy of net/py-xmlrpc to net/py-fastxmlrpc - Commit the port of the PythonWare module as net/py-xmlrpc Personally, I don't oppose the name change, though I think it unnecessary since the Sourceforge project is officially known as "py-xmlrpc", whereas the PythonWare project is generally referred to as "xmlrpclib", even on its own web site. Comments? -- V To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200106191050.f5JAo6E73545>