Re: Ugh, PackageMaker woes.
Re: Ugh, PackageMaker woes.
- Subject: Re: Ugh, PackageMaker woes.
- From: G S <email@hidden>
- Date: Thu, 10 Jun 2010 17:30:19 -0700
Thanks for your reply, Stephane.
As it turns out, some of the updates are being missed by the GUI (and possibly Spotlight). I installed fseventer (after seeing it mentioned in another thread on here) to monitor file-system activity while the installer was running, and found that in fact files are being updated even though Finder reports old dates. One item wasn't being updated, and I found that the source file path in PackageMaker was set to "absolute" instead of "relative to project"; I don't know why that caused the failure, because the file did exist at the absolute path. However, changing it to "relative" apparently fixed the problem.
Interestingly, fseventer also seems to miss a bunch of file additions that take place a couple directory-levels below /Library. Might be unrelated.
My remaining problem is the bizarre behavior of that scripts path for the included package, where PackageMaker forces a path into the "scripts directory" field and then complains it can't copy scripts.
I'm on OS 10.6.3, PackageMaker 3.0.4.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden