directory-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From pamarce...@apache.org
Subject svn commit: r632339 - in /directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg: ./ Resources/ Resources/en.lproj/ root/
Date Fri, 29 Feb 2008 15:10:00 GMT
Author: pamarcelot
Date: Fri Feb 29 07:09:57 2008
New Revision: 632339

URL: http://svn.apache.org/viewvc?rev=632339&view=rev
Log:
Added Apache Directory Server Mac OS X installer package generation script.

Added:
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Info.plist
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/README
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/Description.plist
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/License.rtf
  (with props)
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/background.tiff
  (with props)
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/createPKG.sh   (with props)
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/man_packagemaker.txt
    directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/root/

Added: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Info.plist
URL: http://svn.apache.org/viewvc/directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Info.plist?rev=632339&view=auto
==============================================================================
--- directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Info.plist (added)
+++ directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Info.plist Fri Feb 29 07:09:57
2008
@@ -0,0 +1,44 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>CFBundleGetInfoString</key>
+	<string>1.5.2, Copyright © 2008 Apache Software Foundation</string>
+	<key>CFBundleIdentifier</key>
+	<string>org.apache.directory.server</string>
+	<key>CFBundleShortVersionString</key>
+	<string>1.5.2</string>
+	<key>IFMajorVersion</key>
+	<integer>1</integer>
+	<key>IFMinorVersion</key>
+	<integer>5</integer>
+	<key>IFPkgFlagAllowBackRev</key>
+	<false/>
+	<key>IFPkgFlagAuthorizationAction</key>
+	<string>AdminAuthorization</string>
+	<key>IFPkgFlagBackgroundAlignment</key>
+	<string>topleft</string>
+	<key>IFPkgFlagBackgroundScaling</key>
+	<string>none</string>
+	<key>IFPkgFlagDefaultLocation</key>
+	<string>/</string>
+	<key>IFPkgFlagFollowLinks</key>
+	<true/>
+	<key>IFPkgFlagInstallFat</key>
+	<false/>
+	<key>IFPkgFlagIsRequired</key>
+	<false/>
+	<key>IFPkgFlagOverwritePermissions</key>
+	<false/>
+	<key>IFPkgFlagRelocatable</key>
+	<false/>
+	<key>IFPkgFlagRestartAction</key>
+	<string>NoRestart</string>
+	<key>IFPkgFlagRootVolumeOnly</key>
+	<true/>
+	<key>IFPkgFlagUpdateInstalledLanguages</key>
+	<false/>
+	<key>IFPkgFormatVersion</key>
+	<real>0.10000000149011612</real>
+</dict>
+</plist>

Added: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/README
URL: http://svn.apache.org/viewvc/directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/README?rev=632339&view=auto
==============================================================================
--- directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/README (added)
+++ directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/README Fri Feb 29 07:09:57 2008
@@ -0,0 +1,7 @@
+The createPKG.sh shell script creates the PKG (installer package) for a release of Apache
Directory Server on Mac OS X.
+
+To create a new PKG, you have to put in the "root" folder the Apache Directory Server release
files.
+
+Then, you can launch the shell script: ./createPKG.sh
+
+An "Apache_Directory_Server_Installer.pkg" installer package will be generated.
\ No newline at end of file

Added: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/Description.plist
URL: http://svn.apache.org/viewvc/directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/Description.plist?rev=632339&view=auto
==============================================================================
--- directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/Description.plist
(added)
+++ directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/Description.plist
Fri Feb 29 07:09:57 2008
@@ -0,0 +1,10 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+	<key>IFPkgDescriptionDescription</key>
+	<string></string>
+	<key>IFPkgDescriptionTitle</key>
+	<string>Apache Directory Server 1.5.2</string>
+</dict>
+</plist>

Added: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/License.rtf
URL: http://svn.apache.org/viewvc/directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/License.rtf?rev=632339&view=auto
==============================================================================
--- directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/License.rtf
(added)
+++ directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/License.rtf
Fri Feb 29 07:09:57 2008
@@ -0,0 +1,80 @@
+{\rtf1\mac\ansicpg10000\cocoartf824\cocoasubrtf440
+{\fonttbl\f0\fswiss\fcharset77 Helvetica-Bold;\f1\fswiss\fcharset77 Helvetica;}
+{\colortbl;\red255\green255\blue255;}
+\paperw11899\paperh16839\margl1440\margr1440\vieww14860\viewh11540\viewkind0
+\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\qc\pardirnatural
+
+\f0\b\fs24 \cf0 Apache License\
+Version 2.0, January 2004\
+
+\f1\b0 http://www.apache.org/licenses/\
+\pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\ql\qnatural\pardirnatural
+\cf0 \
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION\
+\
+
+\f0\b 1. Definitions.
+\f1\b0 \
+\
+"License" shall mean the terms and conditions for use, reproduction, and distribution as
defined by Sections 1 through 9 of this document.\
+\
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that
is granting the License.\
+\
+"Legal Entity" shall mean the union of the acting entity and all other entities that control,
are controlled by, or are under common control with that entity. For the purposes of this
definition, "control" means (i) the power, direct or indirect, to cause the direction or management
of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%)
or more of the outstanding shares, or (iii) beneficial ownership of such entity.\
+\
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted
by this License.\
+\
+"Source" form shall mean the preferred form for making modifications, including but not limited
to software source code, documentation source, and configuration files.\
+\
+"Object" form shall mean any form resulting from mechanical transformation or translation
of a Source form, including but not limited to compiled object code, generated documentation,
and conversions to other media types.\
+\
+"Work" shall mean the work of authorship, whether in Source or Object form, made available
under the License, as indicated by a copyright notice that is included in or attached to the
work (an example is provided in the Appendix below).\
+\
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on
(or derived from) the Work and for which the editorial revisions, annotations, elaborations,
or other modifications represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain separable from, or merely
link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.\
+\
+"Contribution" shall mean any work of authorship, including the original version of the Work
and any modifications or additions to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner or by an individual
or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of
this definition, "submitted" means any form of electronic, verbal, or written communication
sent to the Licensor or its representatives, including but not limited to communication on
electronic mailing lists, source code control systems, and issue tracking systems that are
managed by, or on behalf of, the Licensor for the purpose of discussing and improving the
Work, but excluding communication that is conspicuously marked or otherwise designated in
writing by the copyright owner as "Not a Contribution."\
+\
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a
Contribution has been received by Licensor and subsequently incorporated within the Work.\
+\
+
+\f0\b 2. Grant of Copyright License.
+\f1\b0  Subject to the terms and conditions of this License, each Contributor hereby grants
to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright
license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense,
and distribute the Work and such Derivative Works in Source or Object form.\
+\
+
+\f0\b 3. Grant of Patent License.
+\f1\b0  Subject to the terms and conditions of this License, each Contributor hereby grants
to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except
as stated in this section) patent license to make, have made, use, offer to sell, sell, import,
and otherwise transfer the Work, where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination
of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a cross-claim or counterclaim in
a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes
direct or contributory patent infringement, then any patent licenses granted to You under
this License for that Work shall terminate as of the date such litigation is filed.\
+\
+
+\f0\b 4. Redistribution.
+\f1\b0  You may reproduce and distribute copies of the Work or Derivative Works thereof in
any medium, with or without modifications, and in Source or Object form, provided that You
meet the following conditions:\
+\
+   1. You must give any other recipients of the Work or Derivative Works a copy of this License;
and\
+\
+   2. You must cause any modified files to carry prominent notices stating that You changed
the files; and\
+\
+   3. You must retain, in the Source form of any Derivative Works that You distribute, all
copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding
those notices that do not pertain to any part of the Derivative Works; and\
+\
+   4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative
Works that You distribute must include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative
Works, in at least one of the following places: within a NOTICE text file distributed as part
of the Derivative Works; within the Source form or documentation, if provided along with the
Derivative Works; or, within a display generated by the Derivative Works, if and wherever
such third-party notices normally appear. The contents of the NOTICE file are for informational
purposes only and do not modify the License. You may add Your own attribution notices within
Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from
the Work, provided that such additional attribution notices cannot be construed as modifying
the License.\
+\
+You may add Your own copyright statement to Your modifications and may provide additional
or different license terms and conditions for use, reproduction, or distribution of Your modifications,
or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution
of the Work otherwise complies with the conditions stated in this License.\
+\
+
+\f0\b 5. Submission of Contributions.
+\f1\b0  Unless You explicitly state otherwise, any Contribution intentionally submitted for
inclusion in the Work by You to the Licensor shall be under the terms and conditions of this
License, without any additional terms or conditions. Notwithstanding the above, nothing herein
shall supersede or modify the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.\
+\
+
+\f0\b 6. Trademarks.
+\f1\b0  This License does not grant permission to use the trade names, trademarks, service
marks, or product names of the Licensor, except as required for reasonable and customary use
in describing the origin of the Work and reproducing the content of the NOTICE file.\
+\
+
+\f0\b 7. Disclaimer of Warranty.
+\f1\b0  Unless required by applicable law or agreed to in writing, Licensor provides the
Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES
OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties
or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
You are solely responsible for determining the appropriateness of using or redistributing
the Work and assume any risks associated with Your exercise of permissions under this License.\
+\
+
+\f0\b 8. Limitation of Liability.
+\f1\b0  In no event and under no legal theory, whether in tort (including negligence), contract,
or otherwise, unless required by applicable law (such as deliberate and grossly negligent
acts) or agreed to in writing, shall any Contributor be liable to You for damages, including
any direct, indirect, special, incidental, or consequential damages of any character arising
as a result of this License or out of the use or inability to use the Work (including but
not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction,
or any and all other commercial damages or losses), even if such Contributor has been advised
of the possibility of such damages.\
+\
+
+\f0\b 9. Accepting Warranty or Additional Liability.
+\f1\b0  While redistributing the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations
and/or rights consistent with this License. However, in accepting such obligations, You may
act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor,
and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason of your accepting any
such warranty or additional liability. \
+}
\ No newline at end of file

Propchange: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/License.rtf
------------------------------------------------------------------------------
    svn:executable = *

Added: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/background.tiff
URL: http://svn.apache.org/viewvc/directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/background.tiff?rev=632339&view=auto
==============================================================================
Binary file - no diff available.

Propchange: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/background.tiff
------------------------------------------------------------------------------
    svn:executable = *

Propchange: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/Resources/en.lproj/background.tiff
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/createPKG.sh
URL: http://svn.apache.org/viewvc/directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/createPKG.sh?rev=632339&view=auto
==============================================================================
--- directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/createPKG.sh (added)
+++ directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/createPKG.sh Fri Feb 29 07:09:57
2008
@@ -0,0 +1 @@
+/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker --root root/
--resources Resources/ --info Info.plist --out Apache_Directory_Server_Installer.pkg
\ No newline at end of file

Propchange: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/createPKG.sh
------------------------------------------------------------------------------
    svn:executable = *

Added: directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/man_packagemaker.txt
URL: http://svn.apache.org/viewvc/directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/man_packagemaker.txt?rev=632339&view=auto
==============================================================================
--- directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/man_packagemaker.txt (added)
+++ directory/sandbox/pamarcelot/trunks/apacheds-macos-pkg/man_packagemaker.txt Fri Feb 29
07:09:57 2008
@@ -0,0 +1,363 @@
+packagemaker(1)           BSD General Commands Manual          packagemaker(1)
+
+NAME
+     packagemaker, PackageMaker -- Installation-package creation tool
+
+SYNOPSIS
+     packagemaker --root root-path [options]
+
+     packagemaker --doc pmdoc-path [options]
+
+     packagemaker --watch [options]
+
+     packagemaker -build --f root-path [old-pkg-options]
+
+     packagemaker -build -mi | -mc | -ms packages-path [old-mpkg-options]
+
+     packagemaker --sign flat-pkg-or-distribution-path --certificate
+                  certificate-name [--out destination-path]
+
+     packagemaker -help
+
+DESCRIPTION
+     packagemaker allows you to package files in a way that makes it easy for
+     end users to install them on their computers.
+
+     The packagemaker tool provides five pieces of functionality:
+
+     1. Build a PackageMaker document (.pmdoc) using the --doc flag
+
+     2. Build a package or flat package from a root using the --root flag
+
+     3. Build a snapshot package based on filesystem changes using the --watch
+              flag
+
+     4. Sign a flat package, flat metapackage or distribution file using the
+              --sign flag
+
+     5. A backwards-compatibility mode for building packages and metapackages
+              using the old -build flag
+     The sections below describe each of these types of functionality.
+
+BUILDING USING --root OR --doc
+     If a PackageMaker document (.pmdoc) file is provided via the --doc flag,
+     packagemaker will build whatever is specified in that document. If the
+     document specifies a package, you can also use any of the options
+     described below to override certain settings in the document.
+
+     Alternatively, you can provide a directory to packagemaker using the
+     --root flag and packagemaker will construct a package from that root. In
+     this case, an identifier must be provided with the --id flag or specified
+     in the info file provided by the --info flag. You may use the other
+     options described below to customize the package.
+
+     Options:
+
+     --root, -r root-path
+              A path to a directory to package. Either this or the --doc flag
+              must be specified.
+
+     --doc, -d pmdoc-path
+              A path to a .pmdoc file built using the PackageMaker GUI. Either
+              this or the --root flag must be specified.
+
+     --id, -i package-identifier
+              A package identifier, which should be unique for this package.
+              For example, com.apple.packagemaker. If --root is specified,
+              either this or the --info flag must be specified.
+
+     --info, -f info-path
+              A path to an Info.plist file for a bundle package or a Package-
+              Info file for a flat package. If --root is specified, either
+              this or the --id flag must be specified. If specified along with
+              --doc, the provided info file will be merged with the file gen-
+              erated by packagemaker
+
+     [--out, -o destination-path]
+              If specified, the build result will be output to destination-
+              path. If not specified, the build result will be output into the
+              present working directory with a name derived from the input
+              file.
+
+     [--version, -n version]
+              The version number that will be given to your package. If not
+              specified, will default to "1". Will override the version speci-
+              fied in a pmdoc for a package. However, if the pmdoc specifies a
+              metapackage or distribution, this flag will have no effect.
+
+     [--title, -t title]
+              The title that will be given to your package. If not specified,
+              the title will be derived from the root path (for 10.3 or 10.4
+              target) or from the package file name (for 10.5 target). If
+              specified, a distribution will be created. Will override the
+              title specified in a pmdoc.
+
+     [--resources, -e resources-path]
+              A path to a directory of resources to be copied into the pack-
+              age. The directory should be structured as you want it to be in
+              the package. For example, localized resources should be in the
+              appropriate lproj directory and all resources should have the
+              appropriate names. See the Installer documentation for more
+              information. If specified along with --doc, the resources will
+              be merged with any specified in the document.
+
+     [--scripts, -s scripts-path]
+              A path to a directory of scripts to be copied into the package.
+              The directory should be structured as you want it to be in the
+              package. For example, scripts should have appropriate names. See
+              the Installer documentation for more information. If specified
+              along with --doc, the scripts will be merged with any specified
+              in the document.
+
+     [--certificate, -c certificate-name]
+              The name of a certificate with which to sign the flat package or
+              flat metapackage. The name should match that of a certificate in
+              your keychain that is valid for signing. Please note that if
+              packagemaker requires permission to use the certificate, using
+              this option will cause the standard GUI permission dialog to
+              appear.
+
+     [--filter, -x regular-expression]
+              Adds a file filter. Any files in the root matching the provided
+              regular expression will be not be included in the package. This
+              flag can be specified multiple times. If specified along with
+              --doc, the filters will be appended to any specified in the doc-
+              ument.
+
+     [--target, -g 10.5 | 10.4 | 10.3]
+              Specifies the minimum target operating system version. Defaults
+              to 10.3. For 10.5, flat packages and metapackages will be built;
+              for 10.4, bundle packages and distributions will be built; and
+              for 10.3, bundle packages and metapackages will be built.
+
+     [--domain, -h system | home | anywhere]
+              Adds an install domain. This flag can be specified multiple
+              times. Prior to Mac OS X v10.5, the Installer will default to
+              the 'anywhere' domain. You can use the --root-volume-only flag
+              to achieve the same effect as the system domain. If specified
+              along with --doc, will override to domain settings of the docu-
+              ment.
+
+     [--no-recommend, -m]
+              If specified, packagemaker will not apply recommended permis-
+              sions to package contents.
+
+     [--discard-forks, -k]
+              If specified, packagemaker will not preserve resource forks when
+              building packages.
+
+     [--root-volume-only, -b]
+              If specified, install will only be allowed on the root volume.
+
+     [--verbose, -v]
+              Provide detailed status information during construction.
+
+SIGNING PACKAGES USING --sign
+     Existing flat packages, flat metapackages or distributions (.dist) can be
+     signed using the --sign flag. Please note that if packagemaker requires
+     permission to use the certificate, the standard system permission GUI
+     dialog will appear.
+
+     Options:
+
+     --sign flat-pkg-or-distribution-path
+              The path to a flat package, flat metapackage or distribution
+              file (.dist).
+
+     --certificate, -c certificate-name
+              The name of a certificate with which to sign the flat package or
+              flat metapackage. The name should match that of a certificate in
+              your keychain that is valid for signing.
+
+     [--out, -o destination-path]
+              If specified, the signed version of the input will be output to
+              destination-path. If not specified, the signed version will
+              replace the input.
+
+SNAPSHOT PACKAGES USING THE --watch FLAG
+     If the --watch flag is specified, packagemaker will monitor filesystem
+     changes until it receives the SIGUSR1 signal. It will then construct a
+     package of all files that were created/modified while it was watching.
+     All of the flags described above for --root and --doc are applied to the
+     package, with the exception of --root and --doc themselves.
+
+BUILDING IN BACKWARDS-COMPATIBILITY MODE
+     In addition to the interface described above, packagemaker supports the
+     old CLI for backwards compatibility. It can be used to build packages or
+     metapackages using the following options:
+
+     -build   Create an installation package or metapackage. Must be specified
+              to trigger backwards-compatibility mode.
+
+     -proj    A path to a pmproj document.  packagemaker will import and build
+              the document. This will cause the -f, -i, -r, and -d flags to be
+              ignored.
+
+     -p       The path, including the package name and extension (.pkg or
+              .mpkg) where the package is created.
+
+     -f       Directory containing the contents of the package. Not applicable
+              when building a metapackage.
+
+     -b       Directory used to temporarily copy and modify the root if split-
+              ting resource forks (suggestion: /tmp). Not applicable when
+              building a metapackage.
+
+     -s       Split files with resource forks (Installer will reassemble
+              them).  Overrides default behavior that discards resource forks.
+              Not applicable when building a metapackage.
+
+     -ds      Filter .DS_Store files out of the creation process. Not applica-
+              ble when building a metapackage.
+
+     -v       Verbose output during archiving.
+
+     -u       Create uncompressed archive. Not applicable when building a
+              metapackage.
+
+     -r       Directory containing installation resources, such as scripts and
+              Read Me files.
+
+     -i       Path to property list file (.plist) that is copied to the pack-
+              age's Contents directory as Info.plist. It will be modified to
+              contain the package's installed size (IFPkgFlagInstalledSize)
+              and other package flags as necessary. This option must be speci-
+              fied and the Info.plist must contain a CFBundleIdentifier key.
+              This CFBundleIdentifier should uniquely identify your package.
+
+     -d       Path to property list file (.plist) that is copied to the pack-
+              age's Resources directory as Description.plist. If this option
+              is unspecified, a skeletal Description.plist is generated for
+              the package. You should add the title and description entries to
+              the Description.plist file after creating the package.
+
+     -mi      Path to directory of packages/metapackages to be included in the
+              metapackage. The packages will be stored within the created
+              metapackage.
+
+     -ms      Path to directory of packages/metapackages to be included in the
+              metapackage. The packages will not be stored within the created
+              metapackage, rather, they should be on the same level as the
+              .mpkg file.
+
+     -mc      Path to directory of packages/metapackages to be included in the
+              metapackage. The packages will not be stored within the created
+              metapackage, rather, they should remain at the location speci-
+              fied.
+
+THE PACKAGE FORMAT
+     An installation package contains everything the Installer application
+     needs to install a group of files (the package's payload), which can
+     include application bundles, documentation files, scripts, and so on. In
+     general, a package contains the following:
+
+     A bill of materials file:
+              A binary file that describes the contents of the package.
+
+     An information property list:
+              An XML file that contains the information about the package,
+              such as default location and version.
+
+     An archive file:
+              The set of files to be installed, also known as the payload.
+              With packagemaker, this archive is always compressed.
+
+     Resources directory:
+              This directory contains files Installer uses during an installa-
+              tion but doesn't install on the target computer. They include
+              Read Me files, license-agreement files, and scripts.
+
+     A metapackage is a file that includes a list of packages (and possibly
+     other metapackages) and any additional information needed to install
+     them. The actual packages can be stored in the metapackage, on the same
+     level as the metapackage, or at a custom location. In general, a meta-
+     package contains the following:
+
+     An information property list:
+              An XML file that contains the information about the metapackage,
+              such as version and package list.
+
+     Packages directory:
+              Contains any packages stored within the metapackage.
+
+     Resources directory:
+              This directory contains files Installer uses during an installa-
+              tion but doesn't install on the target computer. They include
+              Read Me files, license-agreement files, and scripts.
+
+     A distribution is similar to a metapackage, except that it contains a
+     distribution.dist file, which contains XML and JavaScript which specify
+     the UI for the Install. In general, a distribution contains the follow-
+     ing:
+
+     An distribution script:
+              An XML file specifying the UI for the install. May also contain
+              JavaScript.
+
+     Packages directory:
+              Contains any packages stored within the distribution.
+
+     Resources directory:
+              This directory contains files Installer uses during an installa-
+              tion but doesn't install on the target computer. They include
+              Read Me files, license-agreement files, and scripts.
+
+     See <http://developer.apple.com/documentation/DeveloperTools/Concep-
+     tual/SoftwareDistribution/> as well as the help integrated into Package-
+     Maker for information on the keys of the property-list files as well as a
+     detailed explanation of package creation, format, and use.
+
+     Scripts can be included in your packages/metapackages to test certain
+     conditions before installation or when you need to perform special tasks
+     as the installation takes place.
+
+     Scripts can be run before and after the package's payload is installed.
+     There are two types of scripts: environment-test scripts and installation
+     scripts.
+
+     These are the environment-test scripts you can define for an installa-
+     tion:
+
+     InstallationCheck
+              Installer runs this script to determine whether the installation
+              should proceed.
+
+     VolumeCheck
+              Installer runs this script to determine whether a particular
+              volume can receive the package's payload.
+
+     If the environment-test scripts allow the installation to proceed,
+     Installer performs the installation scripts and the installs the payload
+     in the following order:
+
+     preflight
+     preinstall    or preupgrade
+     Payload installation
+     postinstall   or postupgrade
+     postflight
+
+EXAMPLES
+     Building a root with an identifier:
+           packagemaker --root /tmp/MyGreatApp.dst --id com.example.MyGreatApp
+           --out /tmp/MyGreatApp.pkg
+     Building a flat package with an existing PackageInfo file:
+           packagemaker --root /tmp/MyGreatApp.dst --info /tmp/MyPackageInfo
+           --target 10.5 --out /tmp/MyGreatApp.pkg
+     Building a package from a pmdoc, overriding the version and title:
+           packagemaker --doc /tmp/MyGreatDoc.pmdoc --version 2.0 --title 'My
+           Great App v2'
+     Filtering files named "foo" from your package:
+           packagemaker --root /tmp/MyGreatApp.dst --id com.example.MyGreatApp
+           --filter '/foo$'
+     Creating Cool_App.pkg with existing Info.plist and Description.plist
+     files:
+           packagemaker -build -p /Volumes/Packages/Cool_App/Cool_App.pkg -f
+           /Volumes/Packages/Cool_App/Package_contents -i
+           /Volumes/Packages/Cool_App/Info.plist -d
+           /Volumes/Packages/Cool_App/Description.plist
+
+SEE ALSO
+     installer(8),
+     http://developer.apple.com/documentation/DeveloperTools/Conceptual/SoftwareDistribution/
+
+Mac OS X                       October 16, 2006                       Mac OS X



Mime
View raw message