- Original Package Contents For Mail App On Mac Download
- Original Package Contents For Mail App On Mac Computer
There is a contextual menu item, 'Show Package Contents' that allows one to drill into the guts of an application and view all its resources. Sow Package Contents on an app. Right click for. May 14, 2019 The Mac’s default Mail application (also referred to as “Mail.app” or “Apple Mail”) has a somewhat checkered past. While Mail.app provides a free, full-featured email client on every Mac and has even pioneered some innovative features over the years (like. In the Mail app on your Mac, choose File Import Mailboxes. Select a source in the list, read the information that appears below the list, then click Continue. If you’re importing a mailbox exported from Mail or a folder in the /Library/Mail/V7 folder on another Mac, select Apple Mail. To get to the Mail folder on a Mac, click the desktop to make sure you’re in the Finder, press and hold the Option key, choose Go.
- About Packages
What is Packages?
You are a software developer who just completed a project and it's time to work on shipping it. Or you are an administrator and you need to deploy a plugin on the Mac computers of your network. Whenever you need to create an installation package or distribution for Mac OS X 10.5 or later, Packages is the powerful and flexible solution you're looking for.
Building payload not load of pain
With Packages, you can define which applications, bundles, documents or folders should be part of the payload of your installation packages and where they should be installed. You can even set what the owner, group or permissions of the payload items should be upon installation. And if you need to also install an existing package, just import it so that it can be added to your distribution.
Presentation Editor
With its WYSIWYG editor, Packages lets you set and localize the customizable panes of your distributions. Checking how your distribution looks like in different languages has never been so easy. You can even add Installer plugins to your distribution.
Dependencies Editor
When you need to define the dependencies between choices of your distribution, you can depend on Packages. You can use its visual editor to build simple or complex dependencies trees. You don't have to worry about looping, Packages automatically checks everything and only offers you viable dependencies.
Requirements Editors
Defining the requirements that should be met by your packages to be installed should not require you to think like a developer if you don't want to. With its user friendly requirements editors, Packages makes simple requirements very easy to define and yet still allow you to write more complex requirements using the JavaScript code editor.
Quick Build
If you need to quickly create an installation package for an application or a plugin, drag the item on the Packages icon in the Dock (or the Finder). Your package will be created. There's no step 2. Quick Build uses smart locators to figure out where the item should be installed. Smart Locators are also available from the payload editor pane.
Certification
To ensure that your distribution or packages are not be tampered with between the time you build them and they are installed, you can sign them. Packages can sign flat packages and distributions with a certificate.
Command Line Tool
Integrating Packages into an automated production workflow is easy with the packagesbuild command line tool. Once you have created your Packages project, the packagesbuild tool will let you build it from the Terminal, a shell script or an Xcode Run Script Build phase.
Eating your own dog food
Packages' distribution is built using Packages. Would you care about a solution that would not do that?
Finder, Mac, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries.
The
Library
directories are where the system and your code store all of their related data and resources. In macOS, this directory can contain many different subdirectories, most of which are created automatically by the system. In iOS, the app installer creates only a few subdirectories in ~/Library
(such as Caches
and Preferences
) and your app is responsible for creating all others.Table A-1 lists some of the common subdirectories you might find in a
Library
directory in macOS along with the types of files that belong there. You should always use these directories for their intended purposes. For information about the directories your app should be using the most, see The Library Directory Stores App-Specific Files. Subdirectory | Directory contents |
---|---|
Application Support | Contains all app-specific data and support files. These are the files that your app creates and manages on behalf of the user and can include files that contain user data. By convention, all of these items should be put in a subdirectory whose name matches the bundle identifier of the app. For example, if your app is named MyApp and has the bundle identifier com.example.MyApp , you would put your app’s user-specific data files and resources in the ~/Library/Application Support/com.example.MyApp/ directory. Your app is responsible for creating this directory as needed. Resources required by the app to run must be placed inside the app bundle itself. |
Assistants | Contains programs that assist users in configuration or other tasks. |
Audio | Contains audio plug-ins, loops, and device drivers. |
Autosave Information | Contains app-specific autosave data. |
Caches | Contains cached data that can be regenerated as needed. Apps should never rely on the existence of cache files. Cache files should be placed in a directory whose name matches the bundle identifier of the app. By convention, apps should store cache files in a subdirectory whose name matches the bundle identifier of the app. For example, if your app is named MyApp and has the bundle identifier com.example.MyApp , you would put user-specific cache files in the ~/Library/Caches/com.example.MyApp/ directory. |
ColorPickers | Contains resources for picking colors according to a certain model, such as the HLS (Hue Angle, Saturation, Lightness) picker or RGB picker. |
ColorSync | Contains ColorSync profiles and scripts. |
Components | Contains system bundles and extensions. |
Containers | Contains the home directories for any sandboxed apps. (Available in the user domain only.) |
Contextual Menu Items | Contains plug-ins for extending system-level contextual menus. |
Cookies | Contains data files with web browser cookies. |
Developer | Contains data used by Xcode and other developer tools. |
Dictionaries | Contains language dictionaries for the spell checker. |
Documentation | Contains documentation files and Apple Help packages intended for the users and administrators of the computer. (Apple Help packages are located in the Documentation/Help directory.) In the local domain, this directory contains the help packages shipped by Apple (excluding developer documentation). |
Extensions | Contains device drivers and other kernel extensions. |
Favorites | Contains aliases to frequently accessed folders, files, or websites. (Available in the user domain only.) |
Fonts | Contains font files for both display and printing. |
Frameworks | Contains frameworks and shared libraries. The Frameworks directory in the system domain is for Apple-provided frameworks only. Developers should install their custom frameworks in either the local or user domain. |
Internet Plug-ins | Contains plug-ins, libraries, and filters for web-browser content. |
Keyboards | Contains keyboard definitions. |
LaunchAgents | Specifies the agent apps to launch and run for the current user. |
LaunchDaemons | Specifies the daemons to launch and run as root on the system. |
Logs | Contains log files for the console and specific system services. Users can also view these logs using the Console app. |
Mail | Contains the user’s mailboxes. (Available in the user domain only.) |
PreferencePanes | Contains plug-ins for the System Preferences app. Developers should install their custom preference panes in the local domain. |
Preferences | Contains the user’s preferences. You should never create files in this directory yourself. To get or set preference values, you should always use the NSUserDefaults class or an equivalent system-provided interface. |
Printers | In the system and local domains, this directory contains print drivers, PPD plug-ins, and libraries needed to configure printers. In the user domain, this directory contains the user’s available printer configurations. |
QuickLook | Contains QuickLook plug-ins. If your app defines a QuickLook plug-in for viewing custom document types, install it in this directory (user or local domains only). |
QuickTime | Contains QuickTime components and extensions. |
Screen Savers | Contains screen saver definitions. See Screen Saver Framework Reference for a description of the interfaces used to create screen saver plug-ins. |
Scripting Additions | Contains scripts and scripting resources that extend the capabilities of AppleScript. |
Sounds | Contains system alert sounds. |
StartupItems | (Deprecated) Contains system and third-party scripts and programs to be run at boot time. (See Daemons and Services Programming Guide for more information about starting up processes at boot time.) |
Web Server | Contains web server content. This directory contains the CGI scripts and webpages to be served. (Available in the local domain only.) |
Original Package Contents For Mail App On Mac Download
Original Package Contents For Mail App On Mac Computer
Copyright © 2018 Apple Inc. All Rights Reserved. Terms of Use | Privacy Policy | Updated: 2018-04-09