Skip to main content
14 events
when toggle format what by license comment
S Apr 9, 2019 at 22:09 history edited fra-san CC BY-SA 4.0
Improve inline code formatting
S Apr 9, 2019 at 22:09 history suggested Rotem jackoby CC BY-SA 4.0
Improve description and fix typo.
Apr 9, 2019 at 20:55 review Suggested edits
S Apr 9, 2019 at 22:09
S Jul 26, 2016 at 17:40 history suggested smci CC BY-SA 3.0
clarify 'rarely used'
Jul 26, 2016 at 17:30 review Suggested edits
S Jul 26, 2016 at 17:40
Mar 25, 2016 at 4:55 comment added dspjm @cas What I am expecting is if there are some specific reasons why those packages are not installed under /opt, since according to the definition of the standard, many packages should. If there is no such common reason, and simply just those packages don't want to, then it's fine too, but I wouldn't know if I don't ask. Right?
Mar 25, 2016 at 4:15 comment added cas If it wasn't closed as a dupe, it would have been closed as 'too broad'. There are many different reasons why someone might choose to use /usr/local or /opt or something else entirely. Your question is as un-answerable as 'why do some people prefer vanilla ice-cream over chocolate?'. Also, as @andcoz's answer shows, your premise is just plain wrong - some people DO use /opt. The fact that you haven't personally seen any examples doesn't mean they don't exist.
Mar 25, 2016 at 2:56 review Reopen votes
Mar 25, 2016 at 4:20
Mar 25, 2016 at 2:34 history edited dspjm CC BY-SA 3.0
added 157 characters in body
Mar 24, 2016 at 12:29 history closed cas
Stephen Kitt
andcoz
vonbrand
Jeff Schaller
Duplicate of What is the difference between /opt and /usr/local?
Mar 24, 2016 at 11:51 answer added andcoz timeline score: 6
Mar 24, 2016 at 11:18 review Close votes
Mar 24, 2016 at 12:29
Mar 24, 2016 at 10:57 comment added Centimane Conventions have a way of competing with one another. There are many places people commonly place 3rd party packages, but it's more important to note that there's no need for an /opt/ directory until you use third party packages, so I would say the onus is on the user rather than the OS (since these are packages specifically NOT part of the OS). You can also modify the $PATH globally with sudo/root by editing /etc/bashrc (in RHEL/CentOS/etc, I'm sure an equivalent exists for other distros).
Mar 24, 2016 at 10:50 history asked dspjm CC BY-SA 3.0