This document tries to answer or provide a solution to the most frequently asked questions.

Why do I have to restart my Macintosh at the end of the Iceberg Installation?

The restart is necessary because Iceberg is using a daemon which is running in the bootstrap context. This avoids to have to enter an admin password every time you want to build a project. This also allows building multiple projects at the same time.

Iceberg requires the presence of the SplitForks tool which is included with the Developer Tools.

Without this tool, Iceberg can not split the forks of Carbon applications. If a Carbon application is using resources files which contain a Resource Fork, the Resource Fork will not be installed and the installation may not properly work.

You can get the Developer tools many ways:

• With every copy of Mac OS X sold (eventually on a specific CD).
• With every new Apple computer: an installation package is available in the /Applications folder.
• On the Apple Developer Connection (ADC) web site where the latest version is available. This requires to register as an Apple developer (it's free).

Iceberg can manage a metapackage and all its components in the same project.

If you need to group existing packages inside a metapackage, Iceberg makes this operation very easy:

The command line tool freeze can be used to build a project from the shell.

1	Launch the Terminal application.
2	Type freeze
3	Drag and drop the Iceberg project from the Finder to the Terminal window.
4	Launch the build by pressing Return. Note: If you launch the tool with no arguments, the freeze usage will be displayed.

$ freeze
usage: freeze [-v] [-d ]  file ...
$ freeze /Users/peter/Documents/PackInstall/PackInstall.packproj

Packages are not the best solution to install files in the home directory of the current logged user.

Yet, it's possible to work around this if you wish the user does not have to choose the destination folder (him|her)self.

1	Open Iceberg.
2	Choose File > New Project… .
3	Select the Core Template > Package template and click Next.
4	Type the name of the project in the Project Name text field and click Finish.
5	Choose View > Configurations.
6	Check the following options Root Volume Only, Overwrite Directory Permissions and Follow Sylbolic Links.
7	Choose View > Scripts.
8	Open TextEdit and type the following text in the new document: #!/bin/sh ln -s $HOME /private/tmp/CurrentUser exit 0
9	Choose File > Save.
10	Save the document in your Iceberg project folder under the name ScriptPreflight.txt and quit TextEdit.
11	Select the line named preflight in the Installation Scripts table and click on Choose… .
12	Select the ScriptPreflight.txt file and click Choose.
13	Check the checkbox for the preflight row.
14	Choose View > Files.
15	Select the / folder.
16	Choose Archive > Show Info.
17	Choose Archive > New Folder.
18	Set the name of the folder to private, choose wheel from the Group pop-up menu and set the permissions to drwxr-xr-x.
19	Choose Archive > New Folder.
20	Set the name of the folder to tmp, choose wheel from the Group pop-up menu and set the permissions to drwxrwxrwt.
21	Choose Archive > New Folder.
22	Set the name of the folder to CurrentUser, choose admin from the Group pop-up menu and set the permissions to drwxrwxr-x.
23	Add into the CurrentUser folder, the files you want to install, imagining this is the current user home folder.

On Mac OS X 10.2 (Jaguar):

1	Select in the Files pane the folder in which you want to add files.
2	Choose Archive > Add Files… .
3	Go to the /bin folder.
4	Select the files you want to add and click Add.
5	Select the Reference Style to use for the files. Note: The default Reference Style can be modified in the Preferences dialog.
6	Click Add.

1	Select in the Files pane the folder in which you want to add files.
2	Choose Archive > Add Files… .
3	Press Command + Shift + G.
4	Type the absolute path name /bin in the Go to the folder text field and click Go.
5	Select the files you want to add and click Add.
6	Select the Reference Style to use for the files. Note: The default Reference Style can be modified in the Preferences dialog.
7	Click Add.

It's not possible to remove these folders from the file hiearchy in the Files pane.

As long as you do not add a file or folder into these folders, they won't be part of the final file archive.

Note: Starting with the 1.0.1 release of Iceber, any folder which won't be part of the final archive is displayed dimmed. If this is not what you're seeing, think about updating your version of the software..

This is due to a bug in the SplitForks tool in Mac OS X 10.0-10.2.x. The bug has been fixed in Mac OS X 10.3.9. Any package build with with this version shall work ok.

If you're using a Mac OS X release prior to Mac OS X 10.3.9, you can work around this bug if you are sure the Developer tools are installed on the targeted machine:

#!/bin/sh

/Developer/Tools/SetFile -a C "/Applications/Adobe Photoshop 7"

exit 0

Attention : The InstallationCheck trick is only working for packages. If you want to do the same thing with a metapackage, you need to add an InstallationCheck script to every package of the metapackage.

1	Create a new metapackage project.
2	Choose View > Components.
3	Choose Project > New Component… .
4	Type the name of the package in the Component Name text field (add a suffix related to the OS version, this will help sorting the packages).
5	Select the new package in the Packages & metapackages column.
6	Choose View > Scripts.
7	Using a text editor, write a script which decides whether the OS version is ok. The script shall be named InstallationCheck and the returned value shall be 0 if the package can be installed, 64 otherwise.
8	In Iceberg, click Add… under the Addition Resources table.
9	Select the InstallationCheck and click Add.
10	Choose View > Files.
11	Add the application you wish to install via this package.
12	Select the Components row in the Packages & metapackages column.
13	To add a different version of the application for another version of Mac OS X, add a new package and start over from step 3. Important: Do not forget to create an InstallationCheck script for each package.

This problem was fixed in version 1.0.1.

Note : If you're still experiencing this problem, you may still be using the 1.0 release of Iceberg. It would be a good idea to update the software so that you can benefit from new features and bug fixes.

The latest version of Iceberg is available at the following URL: http://s.sudre.free.fr/Software/Iceberg.html.

You can contact the author of this software ath the following e-mail address: s.sudre@free.fr

A rather complete documentation is available on the Apple Developer Site: Software Distribution.