Packagemaker 3.0.3 Help

Hello,
Im trying to compile a filmmaker stand alone app in packagemaker to use as an installer. I'm currently getting an error message while archiving these files. The message I get is "could not create contents directory for StoryO.pkg" and the error message "could not create archive.bom." What's interesting is that the StoryO file has no contents folder. Please see the picture below. I'm isntalling from my local machine and having pagemaker create file path applications/StoryO.
I'm out of ideas.
Thanks for any input
http://i69.photobucket.com/albums/i77/spitstix/Picture1.png

I created a new "Standard" account on my machine and was able to run cmu with no problems when I connected via ssh from my login.
I changed the script to the following and rebuilt and re-installed:
#!/bin/bash
/usr/bin/env > "/Applications/Logs/env.txt"
/usr/bin/cmu > "/Applications/Logs/cmu.txt"
exit 0
The env.txt file was populated with the Installers env variables (see below); the cmu text file was created but was empty.
Installer env (I've replaced the name of my app):
INSTALLER_TEMP=/private/tmp/PKInstallSandbox.frwZLG/tmp
DSTVOLUME=/
TMPDIR=/private/tmp/PKInstallSandbox.frwZLG/tmp
DSTROOT=/Applications/xyz License Container
DYLDNO_FIXPREBINDING=YES
USER=MarkC
COMMAND_MODE=unix2003
SCRIPT_NAME=postinstall
_PARENT_INSTALLSANDBOX=/var/folders/zz/zzzivhrRnAmviuee+++++++++/Cleanup At Startup/PKInstallSandbox-tmp
SHAREDINSTALLERTEMP=/var/folders/zz/zzzivhrRnAmviuee+++++++++/Cleanup At Startup/PKInstallSandbox-shared-tmp
INSTALLERSECURETEMP=/var/folders/zz/zzzivhrRnAmviuee+++++++++/Cleanup At Startup/PKInstallSandbox-tmp/Secure_Temp.639592538
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/libexec
PWD=/private/tmp/PKInstallSandbox.frwZLG/Scripts/com.xyz.xyz.xyz.pkg.bczx0r
INSTALLPKG_SESSIONID=com.xyz.xyz.xyz.pkg
PACKAGE_PATH=/Users/MarkC/xyz/Installer/Installer/xyz.pkg
SHLVL=1
HOME=/Users/MarkC
_=/usr/bin/env
Thanks,
Mark.

Similar Messages

Help with PackageMaker

I need to install three plugins into the users home directory but can't seem to get this accomplished.
I want the plugins to land here: Users/UserName/Library/Application Support/FileMaker/Extensions/
where UserName is discovered on the users machine.
I selected 'User home directory' in PackageMaker and deselected Volume by user and System volume but the files keep landing here:
MacintoshHD/Library/Application Support/FileMaker/Extensions/
In the configuration I am entering the Destination as:
/Library/Application Support/FileMaker/Extensions/
I thought that selecting the 'User home directory' would concatenate their home directory path to the beginning of the destination path I entered. No go.
If you could please help this rookie out.
Thanks
Doug

Package Maker is a frustrating program! I recall spending many hours juggling with all the options to a package working just so.
I'm not sure I can provide you with a direct answer to your particular problem, but when all else fails you can write a post flight script to copy the files you want to install from the folder that package maker dumps them, to the folder you want them to be in.
Your post flight script file would look something like this:
#!/bin/bash
\# Running apps postflight script
\# Remove any previously installed files from destination folder
cd ~/Library/Application Support/FileMaker/Extensions/
touch firstfilename
rm firstfilename
....etc for other two files....
\# Move files into correct destination folder
cd /Library/Application Support/FileMaker/Extensions/
mv firstfilename ~/Library/Application Support/FileMaker/Extensions/firstfilename
....etc for other two files....
exit
When you've got it just right, then take my advice and write yourself a memo giving yourself detailed, step by step instructions in how to set it all up again.
Bob
Message was edited by: Bob Lang1

Trying to create install script in PackageMaker...help for newbie

Hello,
I am trying to deploy a solution as an install package. Currently, there are 3 items inside the folder that needs to be installed in the /Applications folder. This in itself is easy. However, when I create upgrades to the solution, I want to carry over one file from the previous installation to the new one. Is there a way to have this upgraded version install and instead of removing all of the earlier files, can it install the new files (which are 3) and carry over 1 of the other files.
I hope this makes sense. Thanks for any input or sample scripts that I may be able to modify to accomplish this.
Thanks,
Stephen

Thanks for your time!
Perhaps it would help if I explain a little further my situation and what I am trying to accomplish.
I have a database runtime solution that I want to distribute. I have all of the necessary files in a single folder, let's say, named "Progam 1.2". Since whenever I upgrade this version, I need to have the old data file from the previous version on hand to import into the new file, I create a new folder called "Program 1.3" So after the installation, I would have both folders. The user then opens the new version and the program then will import the previous versions data. At that point the user may delete the previous version folder entirely.
My question is how can accomplish an install so that the new version will not overwrite the previous folder "Program 1.2" when installing the upgrade to "Program 1.3" since I need the data file for updating the data. Ideally, I would love to have the new folder installed and the single data file in the previous version folder be copied to the new versions folder and be renamed to "Previous Data" so that the new version can update the data.
Again, I am a complete newbie in this arena and have simply been doing DMG files where the user copies the new version to the applications folder. But if there was a way to automate this installation more, I would like to do that.
Thanks again for your help!
Stephen

Can Packagemaker create installer with content files outside the bundle?

I'm trying to create an installer with Packagemaker, but the content files need to be outside the final bundle because they're shared with a Windows installer.
I thought I could create a symbolic link to the external folder, but instead of linking from the installer, it copied the files into the bundle. Any idea how to do this, or if it's even possible? I need to be able to do this on 10.3+, if that's relevant.
(I can give a more specific scenario if this isn't clear enough)
Thanks!

zekel wrote:
The main issue I'd be worried about is that the external files (which are quite large) won't have the appropriate progress bar. The external files are around 1GB, while the internal files are in the 30MB range.
How about installing a secondary installer with progress bar that copies these files from the correct location. Your postflight script can just kick off the newly installed file copier.
How's this sound for a hack...
Have a launcher script copy the installer to /tmp, then modify the package to point my files. (I'm installing from read-only media.) It would then open the modified installer which would pull my files from the DVD. This would probably work better (read: at all) if the files aren't compressed inside the package. Do you know if that's an option?
No, sorry. The internals of a package are quite specific. You need PackageMaker itself to build them.
Things like the receipts are non-essential at this point, only because if I can't get this to work then we will continue to use our terrible installer which leaves none of those things. Those shouldn't be too much trouble if I can get the rest to work.
There are some 3rd party installers like Installer VISE. The sad part is that they tend to make the MacOS X Installer look good.
If the guy responsible for that is interested I'll show him Inno Setup, but we have a working Windows installer, so he probably won't want to mess with it.
I agree, but tell him about it anyway. The next time you have to build a Windows installer, he could use Inno Setup and get it done in a couple of hours and then have time to help with the mess that is software deployment on MacOS X.

PackageMaker and selection options

I was wondering if I could get some help on this subject.
I want to create an installer that will install plugins for a game. Im using PackageMaker as it comes with my mac, but Im happy to change if there are any easier ones.
What the installer needs to be able to do is install multiple files into a plugins folder. However, there are conflicting files within these multiple files and they will cause the game to crash if they are installed together.
How do I make it so that if one file is selected, the other/s can't be?
Thanks for the help, really appreciate it.

Ham in a can wrote:
I want to create an installer that will install plugins for a game. Im using PackageMaker as it comes with my mac, but Im happy to change if there are any easier ones.
There is the Iceberg program. I have never tried it so I don't know what its capabilities are.
What the installer needs to be able to do is install multiple files into a plugins folder. However, there are conflicting files within these multiple files and they will cause the game to crash if they are installed together.
How do I make it so that if one file is selected, the other/s can't be?
What you need to do is add each file into your project as a separate item so that they can be individually selected. It would be a very good idea to take this in distinct steps. First build a project with all the files, then refine it.
In the Contents pane, there will be two items for each file, a choice, and the file itself. For you, the interesting part will be the choice. The first thing you will want to do is go through the Configuration tab for each choice and set the identifiers to be meaningful names. Remember, PackageMaker is a buggy, finicky beast. Don't get too fancy with the names. Keep them short, sweet, and without spaces.
You may want to select some choices as initially selected and/or enabled. Things get more interesting with the Requirements pane for each choice. There, you will find additional settings for selected and enabled. Confused yet? Don't worry, I'm sure PackageMaker is too. Always strive to do as little as possible. Don't make too many changes at once. Keep backups. This won't be a quick task.
The main part of the Requirements tab is a test to be performed on each choice. If the test fails, then you can set the selection on/off setting, enabled setting, and/or hidden setting of the choice. The test can be virtually anything. The trick is that for each choice, you have to decide what other conditions merit changing its properties. The test is a negative test. If it fails, you can take action.
It is a going to be a trial and error process, I'm afraid.

PackageMaker Metapackages Command Line

Hi everyone,
I'm trying to create a .pkg via PackageMaker command-line. I'm using 3.0.4 PackageMaker on SnowLeopard. My goal is to create a sort of an "online installer" via command line (since it will be an automatically generated installer).
I have "OnlineInstaller.pmdoc" created prevously with the PM's GUI which works fine. It includes 2 files (both ponting to a remote URL for the "Package Location" config option), some pre-install & post-install scripts, postinstall Actions and some validations such as OSX, java version, memory on System, etc.
So PackageMaker creates correctly the 3 files with the GUI:
1.- OnlineInstaller.pkg (the one that starts the intallation process)
2.- Content.pkg
3.- ThirdPartyComponents.pkg.
They work fine when I created them by clicking "Build" on the GUI.
The problem is when I try to create the packages by command line, PackageMaker generates some /tmp/pkmXXXX folder with the correct packages but deletes it immediatly, the command I'm running is:
/Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/PackageMaker --doc OnlineInstaller.pmdoc --verbose
I've also tried using "-build" parameter but always prompts "ERROR: No packages to build." Some other combination of parameters prompted nothing or created nothing.
Please!!! any help or doc link will be appreciated.
Regards !!
Ismael
Message was edited by: ismamon

Unfortunately, with PackageMaker, there often isn't a good answer. In many cases, you just have to keep trying different methods until you find something that works. Plus, PackageMaker likes to stop working if you upgrade the OS or Xcode. The "--doc" parameter is very handy, but it just may not work. Try specifying all the parts on the command line. I think it is 6 or 7 parameters. I can't tell you exactly what they are because the last time I did that was some time ago and the interface has changed.
I have found it easier to write bootstrapping applications than to use PackageMaker.

Packagemaker 3.0.3. get user's installation preferences

Hi all,
i have a small problem that seems to be caused by my lack of knowledge on the issue. Basically, what I am trying to do is to create an installer for my application with the PackageMaker.app. I am stuck on one place though, how can I 'get' a user's input during the installation and feed it to a script which is getting started after the install.
Example: I give the user 4 language choices during the installation - german, japanese, french and english. The user chooses one of those and according to this choice my post-install script has to do different things.
Does anybody know how can I achieve such behaivior?
Thanks in advance.
Regards
artOf...

I am still struggling with the postinstall script... The problem is the PackageMaker does not give ANY language information to my script i tried many different things for example:
#!/bin/sh
/usr/bin/env
echo "arg0: '"$0"'"
echo "arg1: '"$1"'"
echo "arg2: '"$2"'"
echo "arg3: '"$3"'"
echo "arg4: '"$4"'"
echo "arg5: '"$5"'"
echo "arg6: '"$6"'"
echo "arg7: '"$7"'"
echo "arg8: '"$8"'"
echo "pkgpath: $PACKAGE_PATH"
echo "language: $LANG"
echo "messageLanguage: $LC_MESSAGE"
echo "environment: $ENV"
The output is:
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg0: '/private/tmp/scripts.eDmN/./postinstall'
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg1: '/Developer/Projects/TS-S2/code/trunk/Mac/TS-S2/Setup/BETA/MyApplication - Installer.pkg'
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg2: '/Applications'
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg3: '/'
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg4: 'upgrade'
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg5: ''
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg6: ''
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg7: ''
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: arg8: ''
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: pkgpath:
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: language:
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: messageLanguage:
...imac /private/tmp/scripts.eDmN/./postinstall[1503]: environment:
Where you can see that more then half of the variables are empty. Also the '/usr/bin/env' outputs nothing related to language or localization... I think, I set the localization properly in the packageMaker interface so the problem should be somewhere in the script. I am not experienced at all with writing scripts so I am guessing that is the problem. Any help will be appreciated. Thanks!
-artOf...

PackageMaker & ScreenSaver Setup

Hello,
I'm trying to create an installer for my ScreenSaver using PackageMaker. everything works fine, excepts that I cannot select the screensaver I just installed as the current one.
I have written the following PostFlight script :
#!/bin/sh
/usr/bin/defaults -currentHost write com.apple.screensaver moduleName ToDoScreenSaver
/usr/bin/defaults -currentHost write com.apple.screensaver modulePath "/Library/Screen Savers/ToDoScreenSaver.saver"
I'm sure this script is properly executed because it is launched if I add another command to the script.
But the value in the preferences are not changed. There's no error message, everything seems to be okay, but the script simply does nothing.
Is there anybody someone that could help me ?
David

First follow the instructions in this support article.
If an iPhoto or Aperture library is the source of your desktop pictures, it may need to be rebuilt, or you may need to update the application to the latest version.
Otherwise, continue as below.
Back up all data.
In the Finder, hold down the option key and select
Go ▹ Library
from the menu bar. From the Library folder, delete the following item, if it exists:
Caches/com.apple.systempreferences
and move the following items to the Desktop, if they exist:
Application Support/Dock/desktoppicture.db
Preferences/com.apple.desktop.plist
Launch System Preferences and test. If you still have the issue, put the items you moved to the Desktop back where they came from and post again. Otherwise, delete the items.

Packagemaker 3 and en.lproj

Hi all,
I've searched on this and only come up with one Twit through Google. I had a PackageMaker 3 installer project that worked fine until today. I wanted to move some folders around, so I did and adjusted the relative links to the files in the project. But now I get this odd message:
Could not copy resources to "en.lproj".
Not sure what it needs here, and there's no help in the manual or online. Anyone else run into this?

Just want you to know that you aren't alone on this one. I got bit by it also (twice). If you rename or move your background image, it will give you a somewhat cryptic error. I thought it was a major bug until I removed all my contents and it still wouldn't build the main package until I realized it couldn't build it's OWN en.lproj folder.

PackageMaker Issues

I am having an issue with launching a PackageMaker file (Installer File built with PackageMaker).
When I launch it, other PackageMaker installers also appear that I did not double-click.
This has happened before, and I rebuilt the PackageMaker file. This time, I can't seem to get around it.
I even opened up an Installer created with PackageMaker days ago, and it is opening all my installers, as if I am going to run multiple installs.
Any help would be appreciated.
Aaton

Thanks for that. That does make sense, and I am sure it is because of that Mountain Lion restoring open documents, but they are all closed and PackageMaker (the app) is not running. I don't think this is going to affect my customer's however, since chances are they are only going to launch one installer at a time. It's just disheartening to know that Mountain Lion is trying so hard to make it "easy" but it is only making it confusing. Below is a screenshot of what "sometimes" happens when I launch one installer. It launches both:
Aaton

Productsign help

Hello all!
I am having difficulty understanding the signing of Packages, which I use for Distribution outside of the App Store. I have a valid Apple Developer Installer certificate I use with the `productsign --sign` command which I will demonstrate below. All machines involved were running OS X 10.10.2. The package in question is a ~500Mb flat package generated using PackageMaker.app available via Xcode Tools. The pkg itself was generated via the following command (posting this, just in case that matters):
[/tmp]> /Applications/PackageMaker.app/Contents/MacOS/PackageMaker --doc /tmp/UNSIGNED.pmdoc
[/tmp]> file unsigned.pkg
unsigned.pkg: xar archive - version 1
First, some verification steps:
[/tmp]> pkgutil --check-signature unsigned.pkg
Package "unsigned.pkg":
   Status: no signature
I now sign the package:
[/tmp]> productsign --sign "3rd Party Mac Developer Installer: some company (ABC123)" unsigned.pkg signed.pkg
productsign: signing product with identity "3rd Party Mac Developer Installer: some company (ABC123)" from keychain /Users/needshelp/Library/Keychains/login.keychain
productsign: adding certificate "Apple Worldwide Developer Relations Certification Authority"
productsign: adding certificate "Apple Root CA"
productsign: Wrote signed product archive to signed.pkg
And, some verification for good measure:
[/tmp]> pkgutil --check-signature signed.pkg
Package "signed.pkg":
   Status: signed by a developer certificate issued by Apple
   Certificate Chain:
    1. 3rd Party Mac Developer Installer: some company (ABC123)
       SHA1 fingerprint: A0 2B 94 FD 70 8A D4 A8 4F A7 CE 13 DB E3 A2 13 D1 CC 92 09
    2. Apple Worldwide Developer Relations Certification Authority
       SHA1 fingerprint: 09 50 B6 CD 3D 2F 37 EA 24 6A 1A AA 20 DF AA DB D6 FE 1F 75
    3. Apple Root CA
       SHA1 fingerprint: 61 1E 5B 66 2C 59 3A 08 FF 58 D1 4A E2 24 52 D1 98 DF 6C
Looks good, how about the GateKeeper test:
[/tmp]> spctl -a -vvv --type install signed.pkg
signed.pkg: rejected
origin=3rd Party Mac Developer Installer: some company (ABC123)
Failed...? Lets try to use it anyway. `scp signed.pkg someuser@someothermachine:~/` and attempt to install the package while GateKeeper is enabled on a newly imaged machine... Success. Shows a 'valid' certificate by clicking the little lock icon at the top right and everything. However... when a person uses Safari, Chrome or FireFox to download this package, it fails. Using `curl` works. Basically, the package _is_ signed. But for some reason when you download this package, metadata is created, and that is somehow upsetting GateKeeper. When you clear this metadata:
xattr -c signed.pkg
open signed.pkg
GateKeeper is happy once again. I have tried downloading the package securely using a valid Startcom SSL Certificate (HTTPS Download), and in the clear (HTTP). It does not seem to matter.
Furthermore, and this is the part I really do not understand, I have found that I can scp or curl the unsigned.pkg to a newly imaged machine, with GateKeeper enabled and that works as well. There is no lock at the top right, and we are allowed to install an unsigned untrusted package. Does this mean a package is only checked for validity when downloaded from the internet using a popular web browser? Does GateKeeper not care about signed applications, but only this 'metadata' stuff?
My hope, is that I am missing something simple. But clearly, GateKeeper is not doing what I thought it should be doing.
Thank you all for any help and or thoughts you have the matter!
Jason

After re-reviewing the instructions for distributing applications outside of the App Store, it appears applications are only put in quarantine if downloaded by supported applications. Like Safari, Chrome, Mail etc... So having an untrusted package installed, even when GateKeeper is enabled, is acceptable behavior when obtaining packages beyond the scope of GateKeeper. Okay. I'll accept that
However, I am still not receiving the OK from the GateKeeper user experience verification process, and I would like to know why. My packages are still being blocked. Screen shot attached.
[~/Downloads]> xattr signed.pkg
com.apple.metadata:kMDItemWhereFroms
com.apple.quarantine
The only way I can get any joy:
[~/Downloads]> xattr -d com.apple.quarantine signed.pkg
[~/Downloads]> open signed.pkg
As you can see, the package is signed. Its valid.

Why did PackageMaker Turned my Application into a folder?

I used PackageMaker to create a package to install Font Reserve. After the package was made and installed I noticed that all went into the correct places but my font reserve application is now a folder. Any help would be appreciated.
Thank-you.
Multiple Mac OS X (10.4.9)

Yea the Dev. Tools are on the MAC OS X CD.....or you can download it from the Apple Developer Website to get the latest. Can try it and see what happens like I said it fixed my issues, but to my knowledge from what I read around the net you shouldn't need to install Developer Tools to use Package Maker, but again thats what fixed my issue.
One thing I never tried though was using the PackageMaker off the ARD CD. I have always downloaded the latest Dev. Tools and used the Package Maker that came with it, but it sounds as if that the version you are using is the version off the ARD CD. Thats my best guess.....install the Dev. Tools and try that out.
Thanks,
Dan

PackageMaker (Simple problem I'm sure)

Hi everyone -
Getting my feet wet playing around with PackageMaker, and there's one thing that doesn't make sense to me. How do you install to the "Users" directory without knowing the user's name? I can select a content piece in the left column, and in the right I can choose between an absolute or relative path to the destination (which is a folder inside /Users/[username]/), but it's using my username. How can this be dynamically written?
Message was edited by: domineydesign
Message was edited by: domineydesign

The PackageMaker UI is a complete mystery to me. Somehow, with version 3.0.1, they have managed to take a difficult to use product and make it even worse. So, I can't really help with the User Interface.
If you use the command line version, it goes from incomprehensible to only virtually unusable. On the command line, specify "--domain user". The man page says to use "--domain home" but that is wrong. On the command line, you can specifiy the root and the user domain and the software should be installed in the user's home directory. If you successfully get it to use the user domain, it shouldn't ask for an admin password. It will require the user to logout when the installer finishes. There is no way around that.
You can specificy "--domain user --domain system" and you can choose to "Install for all users of this machine" or "Install just for me". Regardless of the option you choose, you will have to enter an admin password. There is no way around that. At least you won't have to log out.
Unfortunately, it is not a simple answer. Feel free to read the installer-dev Apple mailing list. Those people know far more about PackageMaker than I do and they have no idea how to use it.
I'm now writing my own installer application. Good luck!

Scripts in PackageMaker

Hello,
I'm having a hard time figuring out how to work with scripts (postinstall and choice requirements) in PackageMaker and can't find the answer, so I'll just shoot:
1. Should I place the script manually inside the installer, if so, where? or PackageMaker will do it automagically for me?
2. How should I write the path to the scripts in PackageMaker? Absolute paths using the variables, like $1 (if they can be used there) or is there a way to use relative paths? if so, relative to where?
Thanks in advance for any help!
Israel

Hello,
I also get headaches, figuring out how PackageMaker works. I use Version 3.03. In the scripts pane you can simply add the absolute path to your script for postinstall. PackageMaker will automagically include the script in you package and rename it properly. If your postinstall script need to call additional scripts or other ressources, put them all in one folder and add this folder to "Scripts directory". All files in this folder will be available at install time.
Be aware that the Postinstall script is only called once. (Only, when you run the installer the first time, even if you change the script later). For test purposes, it may be better to use Postflight.
Until now, I don't use the "requirements tests".

Getting the current Home directory in PackageMaker

Hi all,
My package works fine to install a folder in /Library and then set two keys in Loginwindow's defaults file. Even internet-enabled disk image works great.
My problem is, and I've tried now for 2 days to read everything on this, is that I want my install to place an "uninstaller" script on the user's Desktop so the user can easily reverse what the installer did (remove 2 keys and remove the folder in /Library). No problem, this script works fine when run by itself.
But I can't figure out for the life of me how to specify to PackageMaker "home directory of the current user/Desktop" as the install location of this "uninstaller" file. I tried "~/Desktop" and "$HOME/Desktop" in the PackageMaker "destination" field, and also tried making a hierarchy of "~" and "Desktop" folders, and also tried setting the destination to "." and blank. All of these resulted in the Installer making a new directory called "~" at the root of the volume, or one named "$HOME", or just placing the script on the root of the volume. I want it on the user's Desktop, so they will see it. (NOTE: when trying these Unix terms, I was making a separate .pkg for the uninstaller; I know you can't have 2 different install locations in the same package.)
Is this (getting the path to the user's Desktop) possible with PackageMaker, or do I have to have my "postinstall" script for the main install literally create the uninstall script at the user's Desktop (because the "~" notation should be recognized in a shell script)?
I can't figure out why PackageMaker does not recognize the "~" as being the user's home directory - it uses "/" and ".." as defaults sometimes, so it is using the Unix notation.
Also, since the uninstall script is a shell script, if the user double-clicks it, it opens Terminal, which is un-elegant to say the least. Is there a flag that can be set in a shell script which tells it NOT to open Terminal, just to run? I know this is what happens if I wrap it in AppleScript, but I hate using kludges like that.
Thanks in advance to anyone who can help! Happy Holidays
Johnny
Dual 2.0 rev A G5 Mac OS X (10.4.3)

I have a tech support incident ongoing with ADC about this. People are away for the holidays, but so far I have been able to confirm that PackageMaker itself can't do this, as the name of the current user isn't available, nor do paths to the current Home directory work.
The only way is to have PackageMaker launch a preinstall shell or Applescript that does the "mv <item1> <item2>" or similar (the argument $1 that gets passed to these preinstall scripts IS the name of the user doing the install, so you can get the path to his home directory).
The problem THEN becomes, PackageMaker will not build a package that contains only scripts - it HAS to have some "payload" or you will get a build error. So the ultimate kludge would be to have it run the preinstall script, give it a bogus payload (empty file, etc) to install in e.g., /Library or /Applications, then have the postinstall script delete that bogus payload. I have not tried this so I do not know if it would work.
I am thinking now, with the extremely confusing and apparently contradictory rules that PackageMaker has, that the best way to install software is just to wrap a shell script in an Applescript Application Bundle wrapper (because you can't double-click a shell script without launching Terminal, so to have the user run a shell script you need to wrap it in Automator or AppleScript or a Cocoa app wrapper) and have the shell script do the copying of the files that you need. This still might result in the shell script trying to get some sort of permission (either sudo or that "Override user/group for xxx?" message).
I have read the rules on permissions for Packages about 1,017 times and they still make absolutely no sense to me, and I understand Unix permissions completely. All they would have to do is give some examples, but they don't.

Packagemaker 3.0.3 Help

Similar Messages

Maybe you are looking for