[GH-ISSUE #147] The binary executable name may be conflict while using quick installation script #79

New issue

Closed

opened 2026-02-27 23:15:21 +03:00 by kerem · 1 comment

kerem commented

2026-02-27 23:15:21 +03:00

Owner

Originally created by @okcy1016 on GitHub (Sep 21, 2018).
Original GitHub issue: https://github.com/snail007/goproxy/issues/147

As we can see, the binary named proxy is own by a package named libproxy which is required by "glib-networking, libquvi, openconnect, and other packages.
So when the script download goproxy and place the binary executable at /usr/bin/proxy may cause the broken of package libproxy.
Why don't use "goproxy" as the binary name, I think it's also good ^_^ , or there may be some other way to figure it out.

System infomation while discover this situation: Manjaro linux 64 bit (base on Arch linux), system is up to date.

Originally created by @okcy1016 on GitHub (Sep 21, 2018). Original GitHub issue: https://github.com/snail007/goproxy/issues/147 As we can see, the binary named proxy is own by a package named libproxy which is required by "glib-networking, libquvi, openconnect, and other packages. So when the script download goproxy and place the binary executable at /usr/bin/proxy may cause the broken of package libproxy. Why don't use "goproxy" as the binary name, I think it's also good ^_^ , or there may be some other way to figure it out. System infomation while discover this situation: Manjaro linux 64 bit (base on Arch linux), system is up to date. ![screenshot from 2018-09-21 19-43-50](https://user-images.githubusercontent.com/24411020/45879506-62eb3480-bdd7-11e8-914e-eaf847c1bfce.png)