site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-YMail-OSG:X-Yahoo-Newman-Property:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=YoW4pUjvx7WQHrw8LFkFIsH17v5yHh3Ecl/kIMpYPGJDVg+8Pw6e5VHSBJIKix0WXhYd/6UllFuSHTWBocJ+anRsKxTh/eAtrHtwOTtQJVOiH1Hf114L2aIpTm0REgY+FaWwBYH9a09el4uYPpAf+CcZVYsaCf5yf1RNORUMX+0= ; User-agent: Thunderbird 2.0.0.16 (Windows/20080708) Hello, Mr. Claeson. Thank you for your reply. Thank you for your guidance. JongAm Park On 17 Sep 2008, at 19:38, JongAm Park wrote: Try unchecking the relocatable checkbox. /Robert _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... I tried building two installers, one is with "Allow Relocation" turned on, and the other is with the option turned off. I doesn't seem to make difference though. The option is originally for allowing users move the installed files after installation. Probably it is because I successfully install the interested file previously. The document says : When the user installs a relocatable component a second time on the same computer, the installer application searches for the component's existing files in additional locations in the file system, not just the location at which the component was installed, according to the installer package database. So, it may help on a troubled machine we tried install it, but on my local MacBook Pro, I installed it to the /Applications folder a few times successfully, so the one with the "relocation" option should be able to install the files to the /Applications folder consistently, but it didn't. So,.. what I guess now is that.. probably turning on the "Allow relocation" can be a temporary solution to my installation problem. Anyway, I think Apple should be more clear on this policy also. It seems to me that it recognized the interested files in a previous version of the installer package, and it "touched" the one in the installer package. So, according to the document, it searched the existing file, but it was too much! (The default one was "Combination Search" with its default path is set to /Applications/***.app and its identifier as com.<companyname>.<productname>. Because its default path is set to /Applications/***.app, it should check the location and if no such one exists, it should install files there, not searching the same one in Xcode project's build directory or another installer package's content. ) Robert Claeson wrote: 2. It sometimes picks some other destination path than the one which was designated using the PackageMaker. This email sent to site_archiver@lists.apple.com