Re: Not just SnowLeopard-- Re: SL checking bundle versions incorrectly?
Re: Not just SnowLeopard-- Re: SL checking bundle versions incorrectly?
- Subject: Re: Not just SnowLeopard-- Re: SL checking bundle versions incorrectly?
- From: Carl Harris <email@hidden>
- Date: Tue, 08 Sep 2009 12:34:52 -0400
Nathan Kinsinger <email@hidden> wrote:
Basically PackageMaker is storing the original version in it's xml
file and then keeps using that old version for it's upgrade check.
Delete all occurrences of version="1.0" from the xml file and it will
use the apps Info.plist version instead.
This approach worked well for me with Xcode tools 3.1, but not for
Xcode tools 3.2. Under 3.2, it seems that removing the "version"
attribute from the <component> elements in .pmdoc's internal XML files
did not fix the problem. Instead, I found that I had to basically
update the version attribute values to match the CFBundleVersion
values in Info.plist. I added this to my build workflow using an XSLT
transform.
I'd be curious to know if removing the version attribute works for
others using Xcode tools 3.2.
_______________________________________________
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