Timeline for Where to install folder of a command-line app in macOS, to be available by default in my shell?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 5 at 14:48 | history | edited | benwiggy | CC BY-SA 4.0 |
added 1 character in body
|
| May 5 at 13:15 | comment | added | nohillside♦ | By alias, you mean symlink I assume? Might be worth being specific. | |
| May 5 at 12:49 | history | edited | benwiggy | CC BY-SA 4.0 |
deleted 35 characters in body
|
| May 5 at 11:46 | history | edited | benwiggy | CC BY-SA 4.0 |
added 304 characters in body
|
| May 5 at 11:37 | comment | added | benwiggy | @BasilBourque See my revised answer. | |
| May 4 at 21:41 | comment | added | Basil Bourque |
/usr/local/bin exists on my Mac. Several exiting items are found there, all related to Docker (presumably from my install of Docker Desktop app). All of those items are reported by the Finder.app as being "Alias", though I suspect they are actually symlinks. Placing my Kiota folder hierarchy does not result in putting kiota on the default PATH in Terminal.app, even after a system restart.
|
|
| May 4 at 21:27 | comment | added | David Anderson |
@BasilBourque: /usr/local is the root. Executables would go in /usr/local/bin. Manual pages would go in /usr/local/share/man/. The PATH should already have /usr/local/bin included. You may need to create some of these directories.
|
|
| May 4 at 21:05 | comment | added | Basil Bourque |
Nope. I put the folder containing my app in /usr/local. The app does not automatically became available via the PATH, even after a system restart.
|
|
| May 4 at 20:58 | history | answered | benwiggy | CC BY-SA 4.0 |