Normally, xar does not come pre-installed in linux distributions. Now the only thing that needs to be done is to zip everything up into a xar archive. You will also need to create the License, Welcome, ReadMe and background files in the flat/Resources/en.lproj folder. Then also add the following to your Distribution file, right after the closing tag.
#Tmpdisk for mac license
Optional: If you would like to add a license text, a ReadMe file, a welcome text and an installer background image. Note also, that the pkg-ref id and the installKBytes must match the PackageInfo file which we generated above. We've included a system version check in the Distribution javascript. Most of the items should not need a lot of explaining. Place the following contents into the flat folder: SimCow 1.3 function pm_install_check() #base.pkg Great! We are done with the base.pkg, however there are still a few more files left in the flat package directory - all are very straight-forward.įirst, create the Distribution file. The -u and -g options allow us to conveniently
#Tmpdisk for mac mac os x
On Mac OS X the user and group id must be 0/80. In the above command, note that we are once again overriding the user and group identifiers. Create the Bom with the following command: ~ $ mkbom -u 0 -g 80 root flat/base.pkg/Bom
#Tmpdisk for mac install
For this you will need to install the bomutils. The last file needed in the base package is the Bom file. | cpio -o -format odc -owner 0:80 | gzip -c ) > flat/base.pkg/Scripts Mark the script as executable ~ $ chmod +x scripts/postinstallĪnd compress the scripts folder with the following command: ~ $ ( cd scripts & find. Osascript -e 'tell app "Finder" to display dialog "To get the most of SimCow please also install SimMilkMachine."' To add this to the installer, we first create a script directory ( mkdir scripts) in the build folder and then place a file named postinstall inside that folder with the following contents: has decided to deploy their installer with a postinstall script. If you do not wish to execute an installer script then you can omit the section of the above PackageInfo file. Where the latter is the payload size in kilobytes. Both can be obtained by executing the following in the build folder: Also, the PackageInfo contains the number of files and the installation size in kb. The version and bundle-ids must match the ist in your application bundle exactly, otherwise the installer will fail. First of all, notice how the PackageInfo file lists all bundles that are in your pay load. There are many important things you must watch out for in this file. This is an xml-file containing properties about the installer: Now let us create the PackageInfo file in the base.pkg directory. This is very important as your linux user and group ids will most certainly not match with the required user and group root/wheel (0/80) which Mac OS X requires. Notice that we told cpio to override the user and group id. | cpio -o -format odc -owner 0:80 | gzip -c ) > flat/base.pkg/Payload First we will compress the pay-load: ~ $ ( cd root & find. Now let's add some of the necessary files in the base package.
0 kommentar(er)
