Closed RA80533 closed 3 years ago
Hi!
This issue has been left open with no activity for a while now.
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
/bump
Hi!
This issue has been left open with no activity for a while now.
We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
Hi again!
It’s been 60 days since anything happened on this issue, so we are going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.
As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.
I opened this issue to specifically address a set of problems I came across when examining #13947. The rest of this issue is a duplicate of the content from my comment.
It seems most of the installation logic is supposed to occur after the native installation process of the .pkg file through the post-install script (postinst):
-dumplog
toggle flag.update-alternatives
does not exist on macOS. It's not clear if the script ever worked on macOS for this reason.The installation process itself seems to unnecessarily require sudo simply to write its files in system-wide locations. It's quite a poor design decision.