Taking Snapshots

If the files you want to package are not already installed on the drive, Composer can take a snapshot of the file system before and after the files have been installed and create a package source based on the changes.

Composer can take two kinds of snapshots:

• Normal snapshots—These snapshots capture any new files on the drive. These snapshots can take anywhere from ten seconds to several minutes depending on your hardware and the number of files on the drive.

• New and modified snapshots—These snapshots capture any new files on the drive, as well as any files that have been modified. These snapshots can take longer than normal snapshots, since Composer records the modifications date of each file while performing the snapshot.

There are several benefits to using the snapshot approach:

• Composer monitors installations in all locations on the drive.

• You can quit Composer during the installation process.

• You can log out or reboot during the installation process.

• If you delete a file while making modifications to a package source, it may be possible to restore the deleted file. For more information about restoring deleted files, see Adding Scripts to Package Sources.

1. Open Composer and authenticate locally.

2. In the toolbar, click New .

3. Under the Monitor Installation heading in the sidebar, select Snapshot.

4. Select Normal Snapshot or New & Modified Snapshot and click Next.

   

5. Enter a name for the package and click Next.
   

6. Install and configure your software, and then click Create Package Source to initiate the “after” snapshot.

   

Monitoring the File System

When creating a package source using file system monitoring, Composer uses the File System Events (FSEvents) framework that is built into macOS to monitor any changes that are made to the file system. Each time a change is made, FSEvents receives a notification. After your software is installed, Composer analyzes the changes and creates a package source based on the results.

The following limitations should be taken into consideration when monitoring the file system to create a package source:

• You cannot quit Composer during the installation process.

• You cannot log in or restart during the installation process.

• It is possible for FSEvents to miss events if there is too much file system activity.

1. Open Composer and authenticate locally.

2. In the toolbar, click New .

3. Under the Monitor Installation heading in the sidebar, select Snapshot.

4. Select Monitor File System Changes and click Next.

   

5. Enter a name for the package and click Next.
   

6. Install and configure your software, and then click Create Package Source.

   

Creating Package Sources From Pre-Installed Software

You can create a package source from software that is currently installed on your computer if Composer contains a package manifest for the software.

1. Open Composer and authenticate locally.

2. In the toolbar, click New .

3. Under the Package Manifests heading in the sidebar, select Pre-Installed Software.
   Composer scans the file system and displays icons for the software it can package.

   Note: To view package manifests for software that is not installed on the computer, click the disclosure triangle next to Pre-Installed Software and select Not Installed.

4. Select the items you want to create a package source from and click Next.

   

Creating Package Sources from the User Environment Settings

You can create a package source that captures the look and feel of your computer’s interface, such as Dashboard, Display, and Global Preference settings. If Composer contains a package manifest for the setting you want to capture, you can create a package source from it.

To determine which of your current settings Composer can package, select User Environment under the Package Manifests heading. Composer scans the file system and displays icons for the settings that it has package manifests for.

1. Open Composer and authenticate locally.

2. In the toolbar, click New .

3. Under the Package Manifests heading in the sidebar, select User Environment.

4. Select the items you want to create a package source from and click Next.

   

Creating Package Sources by Dragging Contents from the Finder

If you already know which item you want to package, you can bypass the snapshot or monitoring process by dragging items from the Finder to the Sources list in Composer.

There are a few ways Composer handles these items:

• If the item is a package (DMG, PKG, or MPKG), it is listed in the sidebar under the Packages heading.

• If the item is a folder, the root of the folder is used as the root of the package if it is one of the following directories:
  /Applications/
  /Developer/
  /Library/
  /System/
  /Users/
  /bin/
  /private/
  /sbin/
  /usr/

• Any other items are copied to their current location.

Creating Package Sources from Existing Packages

Composer allows you to rebuild an existing package (PKG, DMG, or MPKG) by converting it to a package source. After converting it to a package source, you can make changes to its contents and save a new copy of the package.

1. Open Composer and authenticate locally.

2. Drag the package you want to convert from the Finder to the sidebar in Composer.
   The package appears under the Packages heading.

3. Select the package and click Convert to Source.

   

   When the conversion is complete, a new package source is listed in the sidebar under the Sources heading.