Re: Package Maker problem
Re: Package Maker problem
- Subject: Re: Package Maker problem
- From: Mario Emmenlauer <email@hidden>
- Date: Wed, 21 Jan 2009 12:30:58 +0100
Hi Bill,
I'm referencing an old message here, where you adress my exact
problem:
Bill Coderre wrote:
On Nov 22, 2008, at 10:23 AM, Adil Saleem wrote:
Previously i was using Package Maker on Mac OS 10.4 without any
problems. Now, for the first time, i have to use the Package Maker
(ver 3.0.3) on Mac OS 10.5. I created a package that installs the
application in /Applications/MyApp folder. On running the package, it
creates the folder MyApp in /Applications folder, but the folder is
empty. The application file does not get copied.
Any idea why this is happening ?
Very likely PackageMaker is turning on the relocation flag due to a
longstanding bug. Relocation means that the Installer tries to find an
existing copy of your app to update. Say, the one in the source folder
that your package is built out of.
About a month ago, I wrote a couple of emails explaining how to override
this flag -- ripping it out of the appropriate places in the finished
package.
I would very much like to get my hands on this specific email,
however I could not find it in the archives (maybe it was on a
different list? You post too frequent to be sure:-) ).
My problem is that I generate the PackageMaker configuration auto-
matically, and call PackageMaker with it. The relocatable flag is
then *always* turned on, no matter what I specify in the xml.
I tried PackageMaker versions 3.0.0 - 3.0.3 to no success.
Can you tell me how to rip out the relocatable flag from either the
xml before running PackageMaker, or from the final mpkg package?
Best,
Mario
_______________________________________________
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