[MacPorts] #51825: mitmproxy @0.17.1 -- New port
#51825: mitmproxy @0.17.1 -- New port ------------------------+-------------------------------- Reporter: gavin@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Keywords: | Port: mitmproxy ------------------------+-------------------------------- New port for https://mitmproxy.org/ This is a binary release built by the author and does not require the python dependencies that the py-mitmproxy port does. -- Ticket URL: <https://trac.macports.org/ticket/51825> MacPorts <https://www.macports.org/> Ports system for OS X
#51825: mitmproxy @0.17.1 -- New port ---------------------------+------------------------ Reporter: gavin@… | Owner: macports@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-mitmproxy | ---------------------------+------------------------ Changes (by mf2k@…): * owner: macports-tickets@… => macports@… * cc: petr@… (added) * port: mitmproxy => py-mitmproxy Comment: This port already exists as py-mitmproxy. Cc'ing the maintainers. -- Ticket URL: <https://trac.macports.org/ticket/51825#comment:1> MacPorts <https://www.macports.org/> Ports system for OS X
#51825: mitmproxy @0.17.1 -- New port ---------------------------+------------------------ Reporter: gavin@… | Owner: macports@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-mitmproxy | ---------------------------+------------------------ Comment (by 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 to not rely on System Python of which the version 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 report and close this within some days. -- Ticket URL: <https://trac.macports.org/ticket/51825#comment:2> MacPorts <https://www.macports.org/> Ports system for OS X
#51825: mitmproxy @0.17.1 -- New port ---------------------------+------------------------ Reporter: gavin@… | Owner: macports@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-mitmproxy | ---------------------------+------------------------ Comment (by mf2k@…): @ petr: I completely agree with you. -- Ticket URL: <https://trac.macports.org/ticket/51825#comment:3> MacPorts <https://www.macports.org/> Ports system for OS X
#51825: mitmproxy @0.17.1 -- New port ---------------------------+------------------------ Reporter: gavin@… | Owner: macports@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.4 Resolution: | Keywords: Port: py-mitmproxy | ---------------------------+------------------------ Comment (by petr@…): See #51562, which tracks update of port `py-mitmproxy`. -- Ticket URL: <https://trac.macports.org/ticket/51825#comment:4> MacPorts <https://www.macports.org/> Ports system for OS X
#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 | ---------------------------+-------------------- Changes (by petr@…): * cc: petr@… (removed) * cc: macports@… (added) * owner: macports@… => petr@… -- Ticket URL: <https://trac.macports.org/ticket/51825#comment:5> MacPorts <https://www.macports.org/> Ports system for OS X
#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 petr@…): You might already have noted that I upgraded py-mitmproxy. See ticket #51562 for more details. The Portfile provided with this ticket proposes some firewall settings in the activation/deactivation phase. Is this something we want to adopt for the py-mitproxy port? Or do we prefer that users make such settings consciously/manually? -- Ticket URL: <https://trac.macports.org/ticket/51825#comment:6> MacPorts <https://www.macports.org/> Ports system for OS X
#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
#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@…): Maybe the firewall additions could be included as a variant? Replying to [comment:6 petr@…]:
You might already have noted that I upgraded py-mitmproxy. See ticket #51562 for more details.
The Portfile provided with this ticket proposes some firewall settings in the activation/deactivation phase. Is this something we want to adopt for the py-mitproxy port? Or do we prefer that users make such settings consciously/manually?
-- Ticket URL: <https://trac.macports.org/ticket/51825#comment:8> MacPorts <https://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts