Timeline for Where should I store command line applications?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 27 at 7:26 | comment | added | Basil Bourque |
Update: In macOS Sonoma 14, I did indeed find an existing /opt directory (empty).
|
|
| Apr 5, 2015 at 18:42 | comment | added | рüффп | Thanx for your advices. I personally created the folder /opt/ to put my software and then I just made symbolic links to /usr/local/bin for all the executables... then no need to add the /opt/myspecific-soft in the path environment variable. | |
| Aug 12, 2013 at 10:17 | comment | added | plasmid87 |
/opt/ is very useful for complete applications whereas /usr/local/bin/ is more appropriate for standalone command line scripts. It is often preferable to use /opt/ in instances where a collection of related scripts act as a library (e.g., /opt/myscriptslib/bin/).
|
|
| Aug 11, 2013 at 17:28 | history | answered | Matt Stephenson | CC BY-SA 3.0 |