Packaging Addendum. Information technology resources and support for LSA faculty, staff, and department system administrators.

accessible view | jump to content | search | jump to site-wide navigation

Packaging Addendum

This article contains information not found in the main packaging document that will be rolled into the next version of the document:

Bundle Indentifier:

Should never contain spaces
Should uniquely identify that package. For example, if you're creating separate packages for Intel and PPC versions of an app, be sure to include "Intel" or "PPC" in the BundleID. Do not include the version number in the bundleID unless the vendor does
If there is a vendor supplied bundle identifier, use it as described in the packaging tutorial. Otherwise, format the bundle ID as follows: edu.umich.lsa.dept.application (where dept is omitted if it's a college-wide package)
Examples: com.adobe.Photoshop, edu.umich.lsa.bookmarks, edu.umich.lsa.math.maple11.intel

Package Filename:

Should never contain spaces
Should include the platform (PPC/Intel) if there are separate packages for each
Should include the version number - if the package has two different means of describing the version, including both is useful.
Examples: Matlab-2007a-7.4.pkg, Maple-11-Intel.pkg
It's generally best to remain consistent with previous package names unless that previous name doesn't conform to the above standards

lsa-swl2/testing share:
Feel free to use lsa-swl2/testing as a temporary repository for your packaging work. However, if you're doing so and a package isn't suitable for public use, please put things in a sub-folder called "uniqname-testing".

Package deployment:
When you're done with the package, these steps should be followed:

package author puts the pkg on swl2/testing and announces it to lsa-dev-osx or lsa-mac-admins
people do testing. time passes...
package author is happy with the testing
package author tells Dave that foo.pkg on swl2/testing should be put into SNI
Dave puts it on the staging server
people do SNI testing. time passes....
Dave pushes stuff on staging server to production server
Dave waits a day to make sure things aren't broken
Dave moves the changed packages from swl2/testing to swl2/swdist