#51825: mitmproxy @0.17.1 -- New port ---------------------------+-------------------- Reporter: gavin@… | Owner: petr@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-mitmproxy | ---------------------------+-------------------- Comment (by gavin@…): Sorry for the delay replying... Happy to close this ticket. I submitted it simply because I had already written the portfile after not finding the port. I was limiting my search to the specific name (didn't think to prefix with "py-", or "*mitm*" for that matter). Replying to [comment:2 petr@…]:
The reporter seems to be aware of port `py-mitmproxy`, it is specified as conflicting.
I am not sure what exactly the purpose of the port should be, but the description above indicates that the reporter wants to install a binary build to avoid the dependency on Python. As far as i understand this is not the approach MacPorts uses. Macport's Python packages always install against a set of Python versions provided by Macports and do not rely on system's Python of which the version is not controlled by MacPorts.
I therefore would propose to close this ticket as `invalid`, and only take it as hint to update the existing port. I'll wait for a final comment from the reporter and close this within some days if there is no good reason.
-- Ticket URL: <https://trac.macports.org/ticket/51825#comment:7> MacPorts <https://www.macports.org/> Ports system for OS X