Flat Package Editor For Mac Download

Flat Package Format - The missing documentation

Flat Package Editor For Mac Download Mac
Flat Package Editor For Mac Download Free
Free Pdf Editor For Mac
Photo Editor For Mac

Discover our vector icon packs. 76,537 Free icon sets, available in SVG, PSD, PNG, EPS, format or as ICON FONT. Download them now! VideoPad Video Editor. Recommended Video Editing Software. Professional digital video editor. Create videos for DVD, HD, 360, 3D & more. Easily add visual effects and transitions. Supports all popular video formats. The powerhouse of video editing software for Windows and Mac.

Description

This document will try to document the Flat Package Format introduced by Apple in Mac OS X 10.5. Please keep in mind, this is built from reverse-engineering the format so it may contain inaccuracies for options that are both undocumented and kept secret by Apple.

The world is flat, deal with it.

With previous versions of Mac OS X, a package was a Mac OS X bundle that contains a payload, scripts and a description of the package requirements and behavior. This type of package is still supported in Mac OS X 10.5 but a new format of package was introduced: flat packages.

Flat packages are called that way supposedly because the package is now just a file. This file is actually a xar archive.

You can inspect the contents of a flat package 3 ways:

You can open a flat package using the Flat Package Editor application. This will allow you to see which files are within the archive and inspect the contents of some of these files.
This application is within the PackageMaker application bundle so you need to have installed the Developer Tools. Be aware this application is unfinished and buggy.
You can list the contents of a flat package using the xar tool. You can also extract files from the package using this tool.
The latest version of xar at the time of this writing is 1.5.2 and it does not compile correctly on Mac OS X 10.5. The latest available version of the xar source code used by Apple is available on the Apple Open Source website.
You can use Pacifist to see the files from the package, extract the payload or a specific file from the payload.

A flat package can describe either a metapackage or a single package. We won't discuss metapackage in this document for the time being. Here are 3 examples of flat packages:

A minimal flat package

A flat package with scripts

A Leopard update package

As can be seen on these pictures, a flat package can contains 5 different files:

Name	Required	Description
PackageInfo	Yes	This is a XML document that contains information about the package behavior and requirements.
Bom	Yes	This is the Bill of Materials for the files contained in the Payload archive. See mkbom (8).
Payload	Yes	This is an archive of the hierarchy of files to be installed. The hierarchy is saved as cpio archive compressed with gzip (or, recently, compressed as a concatenation of LZMA chunks). See cpio(1), ditto(1), gzip(1).
Scripts	Optional	This is an archive of scripts and additional resources. The hierarchy is saved as cpio archive compressed with gzip. See cpio(1), ditto(1), gzip(1). This file is optional.
RunAtStartup	Optional	This is a shell script that will be supposedly invoked on the next Mac OS X startup.

PackageInfo

The PackageInfo file is a XML document that provides information about the package behavior, requirements and identity.

A PackageInfo skeleton looks like this:

<?xml version='1.0'?>
<pkg-info>
<deferred-install>
...
</deferred-install>
<payload/>
<dont-obsolete>
...
</dont-obsolete>
<patch>
...
</patch>
<scripts>
...
</scripts>
<groups>
...
</groups>
<install-at-startup>
...
</install-at-startup>
<relocate>
...
</relocate>
<locator>
...
</locator>
<bundle/>
...
<bundle-version>
...
</bundle-version>
</pkg-info>

The different elements are the following ones:

Element	Required	PackageMaker Support	Description
pkg-info	Yes	Partial	This element provides information about the authentication requirements, the package behavior after installation succeeded, etc.
deferred-install	Optional	No	This element provides information about files that should be installed after reboot.
payload	Yes	Yes	This element provides information on the number of files in the payload and the size of the payload.
dont-obsolete	Optional	?	Description Forthcoming
patch	Optional	Yes	This element provides information about the files that should be patched.
scripts	Optional	Yes	The children of this element describe what scripts to run before and after installation.
groups	Optional	No	This is used by Apple. Description forthcoming.
install-at-startup	Optional	No	The children of this element describe which files are to be installed on the next Mac OS X startup.
relocate	Optional	Yes	Description Forthcoming.
locator	Optional	Yes	Description Forthcoming.
bundle	Optional	Yes	These elements provide versioning information about bundles within the payload.
bundle-version	Optional	Yes	The children of this element define a list of bundles that can not be downgraded during the installation.

Note: The <?xml version='1.0'?> element is not created by PackageMaker. From a XML point of view, it's probably a bug but yet it still works without it.

pkg-info
The pkg-info element can have the following attributes:

Attribute	Required	PackageMaker Support	Values	Description
format-version	Yes	Yes	2	Defines the format version for the package.
identifier	Yes	Yes	Uniform Type Identifier String	Defines the package identifier. It should ideally be unique for the package.
auth	Yes	Yes	none root	Defines if the user needs to authenticate as an admin user to install the package.
version	Yes	Yes	Version String	Defines the version of the package. The version of the package is specific to your package and should not be related to the version of the applications you install if possible.
install-location	Optional	Yes	Unix file path	Defines the default location where the payload hierarchy should be installed.
relocatable	Optional	Yes	true false	Description forthcoming.
postinstall-action	Optional	Yes	logout restart shutdown	Defines the action to perform after a successful installation.
deleteObsoleteLanguages	Optional	No	true false	Description forthcoming.
overwrite-permissions	Optional	No	true false	Defines if the permissions of existing directories should be updated with the ones of the same directories within the payload archive.
followSymLinks	Optional	No	true false	Defines if when Installer finds a symbolic link when installing files, the link should be resolved instead of being replaced by a real file or folder.
useHFSPlusCompression	Optional	No	true false	Define if the items in the package should be compressed after installation. Not supported on Mac OS X 10.5.
minimumSystemVersion	Optional	No	Version string	Probably defines the minimum OS version on which the package can be installed. Not supported/used by Mac OS X 10.5.
preserve-xattr	Optional	No	true false	Description forthcoming.

payload
The payload element can have the following attributes:

Attribute	Required	PackageMaker Support	Values	Description
installKBytes	Yes	Yes	Integer	Defines the size in Kilobytes of the payload uncompressed.
numberOfFiles	Yes	Yes	Integer	Defines the number of files and folders inside the payload.
external-root	No	No	Absolute Unix File Path	Defines the location of the external payload folder. If defined, the 'Payload' file should not be included in the flat package but the 'Bom' file is required. This is supported on Mac OS X 10.7 or later.

dont-obsolete

Flat Package Editor For Mac Download Mac

?. You can have multiple instances of the file element. Here is an example:

<dont-obsolete>
<file path='/usr/bin/gnutar'/>
<file path='/usr/bin/tar'/>
</dont-obsolete>

File elements of the dont-obsolete element use the following attribute: path.

patch
The patch section contains a list of files to be patched. You can have multiple instances of the file element. Here is an example:

File elements of the patch element use the following attributes: required-sha1, sha1,and path.

scripts
The scripts section contains a list of scripts to be executed before or after installation. You can have multiple instances of the preinstall or postinstall elements. Here is an example:

preinstall
The preinstall element can have the following attributes:

Attribute	Required	PackageMaker Support	Values	Description
file	Yes	Yes	Unix relative file path	Defines the relative path to the pre-installation script. ./ represents the first level of the file hierarchy archived in the Scripts file. This script will be run after the files installation.
component-id	Optional	Yes	Uniform Type Identifier string	Defines the id of a bundle element. The script will be run before the bundle is installed.

postinstall
The postinstall element can have the following attributes:

Attribute	Required	PackageMaker Support	Values	Description
file	Yes	Yes	Unix relative file path	Defines the relative path to the pre-installation script. ./ represents the first level of the file hierarchy archived in the Scripts file. This script will be run after the installation succeeded.
component-id	Optional	Yes	Uniform Type Identifier string	Defines the id of a bundle element. The script will be run before the bundle is installed.

groups
Description forthcoming.

install-at-startup
The install-at-startup section contains a list of files that should be installed on the next startup of the Mac. This works in collaboration with the RunAtStartup script. You can have multiple instances of the file element. Here is an example from the Mac OS X 10.5.6 updater:

<install-at-startup>
<file path='/usr/libexec/oah/translate'/>
<file path='/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CodeResources'/>
<file path='/System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics'/>
...
</install-at-startup>

File elements of the dont-obsolete element use the following attribute: path.

relocate
The relocate element associates a search-id with one (or more) bundle. Here is an example:

Flat Package Editor For Mac Download Free

The relocate element can have the following attribute:

Attribute	Required	PackageMaker Support	Values	Description
search-id	Yes	Yes	String	Identifier of the search element used to find the instances of the bundle(s).

Bundle elements of the relocate element can use the following attribute: CFBundleIdentifier, CFBundleVersion, CFBundleIdentifier, CFBundleShortVersionString, SourceVersion, path or id.

locator
The locator section contains a list of searches used to locate the instances of specified bundles on disk. Here is an example:

<locator>
<search type='component'>
<bundle CFBundleIdentifier='fr.whitebox.Ivanhoe' path='/Applications/Ivanhoe.app'>
</search>
<search type='script' script='findme()'>
<script>
function findme()
{
return my.search.results['CommonSearchPath'];
}
</script>
</search>
</locator>

search
Description Forthcoming

bundle-version
The bundle-version section contains the list of bundles that can not be downgraded by the installation process. Here is an example:

<bundle-version>
<bundle/>
<bundle/>
...
</bundle-version>

Bundle elements of the bundle-version element can use the following attribute: CFBundleIdentifier, CFBundleVersion, CFBundleIdentifier, CFBundleShortVersionString, SourceVersion, path or id.

Common element types

Some element types are used as children of other elements. The attributes used for these elements may wary depending on the parent element.

bundle
A bundle element can include other bundle elements. Once a bundle has been defined, it can be referenced using its id attribute elsewhere. The bundle element can have the following attributes:

Attribute	Required	PackageMaker Support	Values	Description
CFBundleIdentifier	-	Yes	String	Uniform Type Identifier of the bundle. See Runtime Configuration Guidelines for more information.
CFBundleVersion	-	No	String	Build version number of the bundle. This is retrieved from the Info.plist file of the bundle. See Runtime Configuration Guidelines for more information.
CFBundleShortVersionString	-	No	String	Release version of the bundle. This is retrieved from the Info.plist file of the bundle. See Runtime Configuration Guidelines for more information.
SourceVersion	-	?	Unix file path	Description forthcoming
id	-	Yes	Unix file path	This is the identifier for the bundle. It should be a Uniform Type Identifier. It usually is the CFBundleIdentifier value of the bundle.
path	-	Yes	Unix file path	This is the path of the bundle inside the payload. If the bundle element is a child of another bundle element. The path is a relative path to the parent bundle.

file
The file element can have the following attributes:

Attribute	Required	PackageMaker Support	Values	Description
path	-	Yes	Unix file path	Description forthcoming
required-sha1	-	Yes	SHA1 Signature	Signature of the file that should be patched.
sha1	-	Yes	SHA1 Signature	Description forthcoming.

Document Revision History

Date	Notes
2016-08-22	Added entry for the preserve-xattr attribute.
2016-02-22	Added description for the external-root attribute. Added note about the new LZMA compression.
2009-12-19	Added description for the deferred-install element and useHFSPlusCompression attribute. Fix the sample for the search script sample. Re-organize a bit the elements.
2009-03-31	Added description for the locator and relocate elements.
2009-03-16	Added description for the followSymLinks attribute.
2009-03-12	Added the dont-obsolete element and fixed a typo.
2009-02-28	Fixed the description of the bundle-version element.
2009-02-19	Added description for the patch and file elements.
2009-01-25	Added description for the bundle-id attribute.
2009-01-21	Fixed a mistake regarding PackageMaker component-id support. Added descriptions regarding bundle elements.
2008-12-31	Added some information about the bundle-version section. Added the relocate and locator sections.
2008-12-24	Added the Scripts section. Added the note on the xml tag. Begun work on the install-at-startup section.
2008-12-23	First draft

Packages

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

Free Pdf Editor For Mac

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?

Photo Editor For Mac

Finder, Mac, and Xcode are trademarks of Apple Inc., registered in the U.S. and other countries.

Comments are closed.