2 ms·

As far as I know, iOS is the only OS that is _not_ like this. macOS has /Applications, /Library, their equivalents under the user's home directory, application

by Macha 4y ago

As far as I know, iOS is the only OS that is _not_ like this. macOS has /Applications, /Library, their equivalents under the user's home directory, applications that ignore macOS conventions and use XDG ones... Windows has AppData in three variations, Program Files, Documents... Android has /Android/data, apps that stick stuff in /storage/emulated

IshKebab 4y ago
None of those are like what Unix does though. I'm not saying you shouldn't store configuration data in some other location to the app itself. That's quite reasonable. What Unix does is mix up the contents of all the apps themselves. All app binaries are in `/usr/bin`. All libraries are in `/usr/lib`. All their data is in `/usr/share`. No other OS does that as far as I am aware.
- icedchai 4y ago
  When I built my own packages, back in the old days, I would never adhere to this standard. I found spreading different pieces and parts of the same app all over the filesystem to be a bit bizarre. If I built Apache, it was built with a prefix of /usr/local/apache_VERSION, with a link from /usr/local/apache. This made it easy to upgrade: I'd build a new version (with a new prefix), migrate the configs (if needed), change the symlink (which was really just for each of tracking the current version), then blow away the old version. This was back in the "servers as pets" days.