4 ms·
I think you are probably right. Although, with a name like that it could be some post-install cleanup of temporary files (which would explain why it was doing c
by bee_rider 7mo ago
I think you are probably right. Although, with a name like that it could be some post-install cleanup of temporary files (which would explain why it was doing chown, rather than rm, although there are certainly other options!).
- rmunn 7mo agoI wondered about the chown thing myself, but ended up concluding that the author was misremembering the errors. He probably saw some chown messages and didn't read all the hundreds of lines (I certainly don't read every line of hundreds of log lines, I skim looking for key words), meaning many of them could well have been rm failures that he misremembered as chown. But whatever it was doing, the author would have been wise to read it before deleting the directory it contained, as it would have saved him a lot of trouble finding all the bits and pieces he had to hunt down later.
- bee_rider 7mo agoPlus it would be nice to know if the script expected some environment variables or arguments, and what it did in their absence…
- vsl 7mo agoThe author is an unreliable narrator. The very first thing, the location of the script, can’t possibly be true (the app itself won’t be in per-user support data directory). They conflate things, they definitely don’t know enough about macOS to know to use sudo. I mean, they even rant about bog standard localization files…
- dcrazy 7mo agoSadly, there are apps out there whose installers drop helper apps in ~/Library/Application Support. Or worse: Eve Online actually puts the whole game there. The Eve.app in /Applications (or wherever you choose to put it) is just the launcher/downloader.