9 replies
Sign in or join Beachball Help to reply.
- 0
sig ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
I've never heard of the opt folder. Where on your hard drive is it?
- 0
Klaus1 ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Bit of a mystery that one. Don't delete it even if you can find it!
If I search for 'Gutenprint' in Finder I get the path: Macintosh HD/opt/local/include/gutenprint.
When I go backwards to check the path, after Local, the opt folder is greyed out when I click on Path.
Generally Adobe have a number of opt folders (short for optimization), which can be found if you search for opt.
So, the answer to your question is: yes, leave it alone!
- 0
iBod ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
- 0
Everett Fuller ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Many open-source software projects (like gimp) use the /opt folder. If it's not there, they will create it when you install them.
In a standard unix-like operating system (and darwin, the unix-like foundation of mac os x is no different), the core binaries are installed in /usr/bin or /usr/sbin, and core libraries are installed in /usr/lib, and there are specific directories where the system looks for specific types of information... However there are lots of dependencies amongst this core functionality: more than one binary application can use the same library.
If the user decided to install some additional software, (and usually the admin password is needed to do it, right), the user has authorized the installer to do what it needs to do to get the software installed, even if this means updating one of the libraries to the most recent version. In this case, what happens to all the other software already installed that used the old library? Well... what happens, is none of the old programs work anymore.
The workaround has been to create a separate directory for additional software installs, so that the core functionality in /usr won't be threatened. Many software projects created a directory inside /usr called /usr/local in which they install their components. Other projects use the /opt directory. Others use /opt/local.
This is why, in unix-like operating systems, you find repititions of the same folders in other folders (i.e., there is a /usr/bin and a /usr/local/bin and an /opt/bin). The "bin" is a common name for folders that contain binaries (commands and applications that are executable and built for the specific operating system that they are running under), and "lib" is a common name for folders that contain libraries. You can find "bin" and "lib" folders throughout your system.
One downside to this is that additional programs installed into the "opt" directory could interfere with the ones that are already there, and for this reason, some programs will create their own directory all to themselves and install everything they need there, even if most of it is a copy of libraries that are already present somewhere else on the system--space is less and less of an issue in the age of terrabytes.
If you learn make your own binaries by compiling them from source code (way easier than it sounds, as you usually only have to type "./configure" and wait an hour for it to finish, "make", wait another hour, and then "make install"--really that's all there is to it) then you can control which directories the software uses (whether to use /usr, /opt, or to create a new directory entirely) plus you can run lots of cool free software.
So that's what the opt folder on your hard drive is for.
- 0
Michael Conniff ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Klaus1 wrote:
Generally Adobe have a number of opt folders (short for optimization), which can be found if you search for opt.Well, Adobe may call it that, but the general interpretation is that 'opt' is short for 'optional' 😉
- 0
sig ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
"Well, Adobe may call it that, but the general interpretation is that 'opt' is short for 'optional'"
Or "opt" out. 🙂
- 0
Bruce Bathurst ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
They're great Unix programs; I've leave it alone.
BSD Unix used /usr/local for the directory in which the local system administrator installed applications. Because the non-server version of MacOSX has no system administrator to make sure there are no conflicts with Apple's use of /usr/local and yours, distributors of free software for Darwin have chosen different directories for local installs.
Fink substituted /sw for /usr/local and still distribute both binary and source code for many, free applications using 'Fink Commander', a GUI interface. They couldn't keep up with Apple's rapid changes to X11 they weren't informed of, so their applications stop with 10.3.
MacPorts is more for professionals, but has taken Fink's place for 10.4. It chose to substitute /opt/local for /usr/local. MacPorts offers only the source code for professional Unix applications, so you need to compile them. This requires only the Developer's Kit (which is free), and a comfortableness with Unix. For this reason, MacPorts offers no GUI interface, but a nice command-line one.
In other words, keep /opt. Many of its Unix programs (like GIMP) are wonderful, and you may wish to try building some. The more application-oriented Unix applications use X11 in a Window, are are very professional, like GIMP.
Bruce
Sorry, had I seen Mr Fuller's response first, I wouldn't have replied.
- 0
Bruce Bathurst ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
These 'opt' folders Klaus refers to may well represent 'optimization' (thank, you Adobe, whom I like about as well as Microsoft), for Adobe mustn't use /opt/local.
Those library dependencies Mr Everett refers to are automatically taken care of by MacPorts's installer. Fink's installer looks in /sw to check its libraries for consistency.
If Adobe is using /opt/local for something not installed using MacPorts, this is very bad.
Bruce
- 0
tijames ·
Imported from the Apple Support Forums via the Wayback Machine 🔗
Thanks for the replies, it helped me out a lot. ^__^
~TI-James
