• Packagemaker Mac Os X Download Iso
• Mac Os X Lion Download

Introduction:

Could someone try these steps on Mac OS X 10.5.4 and see if you have the same problem? Here are my exact steps to make the simplest installer possible. 1) Create a new Cocoa application called EmptyApp and make a release build. 2) Open PackageMaker and make a new package with 10.3 minimum target and com.MyCompany for organization. If you add any additional packages for installation as part of a Yosemite OS install/upgrade (like you would with NetInstall), they must all be distribution-style flat packages. Bundle-style packages (like those created by PackageMaker) will not work when added to a Yosemite OS install/upgrade and component-style flat packages also will not work. Prior to Mac OS X v10.5, the Installer will default to the 'any- where' 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 document. The version of Mac OS X that the resulting PackageMaker archive should be compatible with. Different versions of Mac OS X support different features. For example, CPack can only build component-based installers for Mac OS X 10.4 or newer, and can only build installers that download component son-the-fly for Mac OS X 10.5 or newer. Let’s download PackageMaker from the developer’s site. You will need to have an account, it’s free to create one. Once logged in, Go to the Dev Center and Click Mac. Click on Additional Downloads and search for PackageMaker. It will be under Auxiliary tools for XCode. Once you have it install, launch it. Create OS X Recovery on an external drive that has all of the same capabilities as the built-in unit. Generate new partitions not visible to standard system tools and personalize the output settings. Our software library provides a free download of OS X Recovery Disk Assistant 1.0 for Mac. This free Mac application is a product of Apple Inc.

In our blogpost today we will show you how you can create a simple installer application with the help of PackageMaker. The installer will install a kernel extension file to a Mac OS X with a version greater than or equal to 10.9.

What is PackageMaker?

PackageMaker is a tool used for creating installation packages, in other words software consisting of multiple components. Contrary to other installers, PackageMaker does not create a self-running installer but a package (with a .pkg extension) which contains files to install and information on where to install them. It can also include custom files and scripts to run before or after the installation.

The process to install a package is very simple; by double-clicking on the package the installer application will be launched and will guide you through the necessary steps of the installation.

Prerequisites:

In order to be able to build your package you will need two things:

• Have PackageMaker installed to your computer. You can download PackageMaker directly by logging into developer.apple.com (https://developer.apple.com/downloads) and downloading ‘Auxiliary Tools for Xcode – Late July 2012’.
• Have access to an administrator account on your computer.

Package your kext file:

Here are the major steps you will follow in order to package your kext file:

• Set permissions and owner for your kext
• Create additional installer information
• Create a package with PackageMaker
• Build the package and test the installation

Set permissions and owner for your kext:

The first and the most important thing to do before starting to build your package is to make sure that the kext file has the proper permissions and owner. Don’t forget to check that your kext is located in a directory with root permissions when it is packaged.

In other words the kext should have the following attributes:

For example:
Your kext file is located on your Desktop ( e.g. codebender.kext).
Create a directory on your tmp folder, (e.g. codebender):

and copy your kext inside:
sudo cp -R ~/Desktop/codebender.kext ~/tmp/codebender

Check that the owners and the permissions are correct:

If everything is fine, the ouput will be:
drwxr-xr-x 3 root wheel 102 Feb 10 11:37 codebender.kext

Create additional installer information:

You can create a Welcome file, a Read Me file and a Software Licence Agreement file which will be used later for your installer.

• Welcome file:
  The Welcome file is the first impression that a user receives when opening the kext’s package. Most of the time, it’s a summary of what the software will install to a user’s computer. The Welcome file file should be in rtf format. If Welcome.rtf file is added during the creation of a package, the installer will display the contents of the file. It is not obligatory to have a Welcome.rtf file to your installer.
• Read Me file:
  The Read Me file describes the contents of your package, version information, or any additional information that you want to show to the user. The Read Me file file should be in rtf format. If ReadMe.rtf file is added during the creation of a package, the installer will automatically add a ‘ReadMe’ bullet to the list and will display the contents of the file. It is not obligatory to have a ReadMe.rtf file to your installer.
• Software Licence Agreement:
  The Software Licence Agreement describes the terms of use for your package, legal disclaimers, and any prerelease software warnings. The Software Licencefile Agreement file should be in rtf format. If Licence.rtf file is added during the creation of a package, the installer will automatically add a ‘License’ bullet to the list and will display the contents of the file. It is not obligatory to have a Licence.rtf file to your installer.

Create a package with PackageMaker

First, you have to open PackageMaker application. Navigate to the folder where ‘Auxiliary Tools for Xcode – Late July 2012’ has been downloaded and double click to the dmg file. Then you will have to find PackageMaker application and double click to open it. The main PackageMaker window will appear. Complete the Install Properties and click OK.
Fill in the fields of the Configuration tab of the main window as show below:

Then,you have to add your kext file. Open a terminal and type:

Drag and drop the codebender.kext file under Contents of the main window. The main view changes and shows information about the codebender package:

Click on the Configuration tab and fill the Destination field. For Mac OS X 10.9 and earlier the Destination of the kext files is /System/Library/Extensions (the one that PackageMaker shows by default) while for versions greater or equal to 10.9 Destination should be changed to /Library/Extensions. In our example we will create an installer that will be suitable only for Mac OS X greater or equal to 10.9:

The component package Contents pane is where you specify the ownership and access permissions of each of the files that are included in the component (you can see the files by clicking on the arrow next to codebender.kext):

By clicking on codebender Distribution Requirements pane you can add tests that the installer application performs before starting the installation. In our example we want to check whether or not the target operation system version is greater than or equal to 10.9:

Now you are ready to add custom actions. You may want to tell the installer application to perform a particular action before or after the product package is installed. For example, in our case, in order to avoid asking the user for a system restart we will add a custom action that will load the kext file once the installation is over. You will have to select codebender Distribution and then click the Actions tab. Go to Postinstall Actions and click Edit…. A menu containing some customs actions that can take place will appear. Select Load Kernel Extension:

Afterwards select the component that you want to be loaded and click OK:

Click codebender.kext and then Choose:

The custom action will now appear under Postinstall Actions section:

Once you have completed this step, the package has everything it needs for the installer to install your kext. Now it is time to customize the installer interface using the files previously created. Click the Edit Interface button in the upper-right corner of the window and view the Interface Editor window that opens. The first page of the Interface Editor, Background bullet, allows you to provide a custom background image for your installer that will be shown instead of the default installer image. Under Background section on the right, select File and browse to the directory where you custom image is located. Click on Continue:

In the same way you can add the Welcome.rtf and ReadMe.rtf files previously created by clicking on the corresponding bullets and selecting the file under File option that will appear on the right.

Build the package and test the installation

You are ready to build and test your package. To build the package go to the PackageMaker menu bar and select Build. If you haven’t saved your progress now it is the time to do it. Specify a location of your choice and enter codebender.pkg as the filename:

If you have correctly followed the process your build will succeed and the codebender.pkg installer will appear on the selected directory. Double-click your package to run the Installer application. The first screen that will appear will display your Welcome.rtf file message:

By clicking on Continue button, you will be prompted to the next screen that will display the ReadMe.rtf file previously created:

Following the simple installer steps you will reach the Summary section where you can see whether or not the installation was successful:

Last thing to do is check that the package was properly installed. Open a terminal and type:

The output will be:

That’s all for now! Thanks for stopping by and reading.

Today I will be talking about PackageMaker

It’s a very neat tool for systems administrators to use and create packages for OS X.

You can download PackageMaker from Apple Developer’s site (A google Search will also find you PackageMaker via Softopia)
PackageMaker let’s you create simple and easy to use application or script packages to be deployed on clients machines.

Personally, I use PackageMaker constantly to create deployment software for batch installs or even pass on customized softwares to my end users as a simple to use install.

Further down, you can also use the packages you create with Deploystudio or Munki

Chess programs for mac os x. Let’s download PackageMaker from the developer’s site

You will need to have an account, it’s free to create one.

Once logged in, Go to the Dev Center and Click Mac

Click on Additional Downloads and search for PackageMaker

It will be under Auxiliary tools for XCode

Once you have it install, launch it

In the Organization Field, you need a unique Organization concept such as com.apple, com.google (Clearly you don’t want to use those but pick something according)

Click OK

At this stage, you will need to give the package a title

Select the Install Destination (User selected, System Drive i.e Macintosh HD or the user home folder)

You can add a certificate (I will not get into that, because apps tied to certs are actual in house apps and chances are you rather the software checked in rather than having the cert with it)

Description will just give a written explanation to the user

Drag and Drop the app or Files you want to include in your package over to the content section (Firefox in this case)

You will see the permissions options allowing you to set permissions for the files.

Unless you know what you are doing, just apply the recommendations.

Packagemaker Mac Os X Download Iso

The configuration tab will allow you to say where exactly the app should be stored, give it an identifier and a version to your package, you can also set if it needs admin authentication or a restart action

The Blue Interface Logo above the packageMaker window will allow you to customize the interface for a better User Experience.

How to set background color in dev c%2b%2b. This would be where you would put the User Agreement, etc.

Once all is done.

Click the Build and you will be prompted for a Saved Location and File Name

That’s it, you have created your package and it’s ready to use.

Mac Os X Lion Download

I would also recommend you save the PackageMaker build File so if you needed to make a new version it would be easy.