Safari (web browser) – built-in from Mac OS X 10.3, available as a separate download for Mac OS X 10.2; SeaMonkey – open source Internet application suite; Shiira – open source; Sleipnir – free, by Fenrir Inc; Tor (anonymity network) - free, open source; Torch (web browser) - free, by Torch Media Inc. Internet Explorer for Mac – free. Creating 'Native' Java Applications on Mac OS X. If you develop on Mac OS X you can use the Jar Bundler application to turn jar files into Mac OS X applications. Jar Bundler is distributed with the other developer tools and is located in Developer/Applications/.

Check compatibility

You can upgrade to OS Yosemite on any of the following Mac models. Your Mac also needs at least 2GB of memory and 8GB of available storage space.

MacBook introduced in 2009 or later, plus MacBook (13-inch, Aluminum, Late 2008)
MacBook Air introduced in late 2008 or later
MacBook Pro introduced in mid 2007 or later
Mac mini introduced in early 2009 or later
iMac introduced in mid 2007 or later
Mac Pro introduced in early 2008 or later
Xserve models introduced in early 2009

To find your Mac model, memory, storage space, and macOS version, choose About This Mac from the Apple menu . If your Mac isn't compatible with OS X Yosemite, the installer will let you know.

Make a backup

Before installing any upgrade, it’s a good idea to back up your Mac. Time Machine makes it simple, and other backup methods are also available. Learn how to back up your Mac.

Get connected

It takes time to download and install OS X, so make sure that you have a reliable Internet connection. If you're using a Mac notebook computer, plug it into AC power.

Download OS X Yosemite

For the strongest security and latest features, find out whether you can upgrade to macOS Catalina, the latest version of macOS.

If you still need OS X Yosemite, use this link: Download OS X Yosemite. A file named InstallMacOSX.dmg will download to your Mac.

Install the macOS installer

Double-click the downloaded file to open a window showing its contents. Then double-click the file within, named InstallMacOSX.pkg.

Follow the onscreen instructions, which will guide you through the steps necessary to install.

Begin installation

After installation of the installer is complete, open the Applications folder on your Mac, then double-click the file named Install OS X Yosemite.

Click Continue and follow the onscreen instructions. You might find it easiest to begin installation in the evening so that it can complete overnight, if needed.

Allow installation to complete

Please allow installation to complete without putting your Mac to sleep or closing its lid. Your Mac might restart, show a progress bar, or show a blank screen several times as it installs both OS X and related updates to your Mac firmware.

Learn more

OS X Yosemite won't install on top of a later version of macOS, but you can erase your disk first or install on another disk.
You can use macOS Recovery to reinstall macOS.

Bundle
Filename extension	.app, .framework, .kext, .plugin, .docset, .xpc, .qlgenerator, .component, .saver, .mdimporter, etc.
Uniform Type Identifier (UTI)	com.apple.bundle
Container for	executable binary, metadata, other bundles, any other file needed to run the application.

In NeXTSTEP, OPENSTEP, GNUstep, and their lineal descendants macOS and iOS, a bundle is a file directory with a defined structure and file extension, allowing related files to be grouped together as a conceptually single item.

Examples of bundles that contain executable code include applications, frameworks, and plugins. This kind of bundle usually contains one file representing executable code, and files that represent resources such as nibs, templates, images, sounds, and other media. On some other systems, such as Microsoft Windows, these resources are usually included directly in the executable file itself at compile time. On older Macintoshes, a similar technique is used, where additional metadata can be added to a file's resource fork. Similar in concept are the application directories used in RISC OS and on the ROX Desktop.

Examples of bundles that do not contain executable code include document packages (iWork documents) and media libraries (iPhoto Library).

Bundles are programmatically accessed with the NSBundle class in Cocoa, NeXTSTEP and GNUstep's Foundation frameworks, and with CFBundle in Core Foundation. Bundles often include an Info.plist file for metadata.^[1] The Uniform Type Identifier (UTI) for an Apple bundle is com.apple.bundle.^[2]

Application bundles[edit]

Mac Os Install Dvd

Application bundle
Filename extension
Uniform Type Identifier (UTI)	com.apple.application-bundle
Type of format	application software
Container for	executable binary
Extended from	Bundle

Application bundles are directory hierarchies, with the top-level directory having a name that ends with a .app extension. In an application bundle, the first directory in the bundle underneath the top-level directory is usually named Contents. Within Contents there is usually another directory (called MacOS on Macs), which contains the application's executable code. Within the Contents folder there is usually also a directory called Resources, which contains the resources of the application.

Among other things, the Resources folder contains localized versions of the application's nib files.

Other common subdirectories include Plugins, Frameworks, and Shared Frameworks. The Frameworks directory contains frameworks used by the application, and are used even if another version of the framework exists on the system. The Shared Frameworks directory contains frameworks that can be used both by the application that contains them, and other applications; they are used only if a newer version does not exist elsewhere on the system. Plugins contains extensible code used by the application.

By default, the Finder displays application bundles, which can also be referred to as packages, as opaque files with no underlying structure; the contents of the bundle can be shown with the 'Show Package Contents' context menu item.

GNUstep by default uses the name of the application to name the folder that contains application code. An alternative is to name them by the computer architecture and OS the code is intended for to form a fat binary, so the application can be opened on many platforms.^[3]^[4]

macOS framework bundles[edit]

Framework bundle
Filename extension	.framework
Uniform Type Identifier (UTI)	com.apple.framework
Extended from	bundle

macOS frameworks are also stored as bundles;^[5] the top-level directory of a framework bundle has a name that is the name of the framework followed by the extension .framework. In the top-level directory is a Versions directory, with subdirectories for one or more versions of the framework, each subdirectory containing the dynamic library code for the framework, in a file whose name is the same as the name of the framework, possibly with a Headers folder containing header files for the framework, and other subfolders such as Resources. The Versions directory also contains a symbolic link Current to the directory for the current version of the framework. In the top-level directory are symbolic links to the contents of Versions/Current.^[6]

The Finder displays framework bundles as directories rather than as opaque files.

Although GNUstep uses frameworks, they are not usually stored as bundles. This is because the full semantics of framework load

Os X Application