June 2005 - Installer-dev - lists.apple.com

Re: localized packages
by Stéphane Sudre 30 Jun '05

30 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On jeudi, juin 30, 2005, at 03:34 PM, Wade Girard wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I have a meta package that I am using to install our product, and we have a set of apple scripts that are what the user uses to launch our application. We want to have the names of these apple scripts be localized. Is it possible to have individual packages for each language, and to determine what language the user is using, then either through a preflight script, or some other mechanism to install the correct package? Or is there a better/different way to handle > this. You can try it the Virus way (also known as the Mac OS X Install CD way). Instead of using directly the applescript scripts, embed them in a Cocoa application whose sole purpose in life is to run your applescript script. By using a Cocoa application, you can provide a localized name for the application for every language you wish to support. Have a look at the Mac OS X ReadMe on the Mac OS X Install CD, you will see how it's done. This email sent to site_archiver(a)lists.apple.com

1 0

Distribution lists
by Wade Girard 30 Jun '05

30 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com -Wade _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… Does anyone know of a way in a distribution list to determine what language the user is running their OS in (i.e. en, jp, etc...) This email sent to site_archiver(a)lists.apple.com

1 0

InfoPlist.strings
by Carl Smith 30 Jun '05

30 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcV9mJ4Ob1idiFl/Sc+7Yicaj8IyTg== Thread-topic: InfoPlist.strings _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

localized packages
by Wade Girard 30 Jun '05

30 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com -Wade _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I have a meta package that I am using to install our product, and we have a set of apple scripts that are what the user uses to launch our application. We want to have the names of these apple scripts be localized. Is it possible to have individual packages for each language, and to determine what language the user is using, then either through a preflight script, or some other mechanism to install the correct package? Or is there a better/different way to handle this. This email sent to site_archiver(a)lists.apple.com

1 0

Archiving my contents folder for clean installation
by Gert van de Beld 30 Jun '05

30 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Microsoft-Entourage/11.1.0.040913 _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Login Items...
by Stéphane Sudre 29 Jun '05

29 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On mercredi, juin 29, 2005, at 06:10 PM, Huyler, Christopher M wrote: I know this is not directly related to Package Maker but most people on this list would have experience with Mac installation tasks and hopefully one of you can answer my question. The latest version of our product is going to have what we call a "Realtime Monitor" Task Bar App. On Windows this would appear in the lower right corner of the task bar. On Mac, this will appear in the upper right hand corner of the Menu Bar next to the date. The App simply creates a status item with a drop down menu. I would like this App to launch when every user logs in (local or remote). Is it possible to configure this at install time on Mac OS X? We need to support 10.2.8, 10.3 and 10.4. You need to contact DTS to request this code. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… I don't have the "code" under my eyes right now, but DTS has some code that is adding Login Items. IIRC, there is an option to add it for the current user or all the users. This email sent to site_archiver(a)lists.apple.com

1 0

Login Items...
by Huyler, Christopher M 29 Jun '05

29 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcV8xQtqbX3+ecQbQ/W3PjeRQS7ZGg== Thread-topic: Login Items... I know this is not directly related to Package Maker but most people on this list would have experience with Mac installation tasks and hopefully one of you can answer my question. The latest version of our product is going to have what we call a "Realtime Monitor" Task Bar App. On Windows this would appear in the lower right corner of the task bar. On Mac, this will appear in the upper right hand corner of the Menu Bar next to the date. The App simply creates a status item with a drop down menu. I would like this App to launch when every user logs in (local or remote). Is it possible to configure this at install time on Mac OS X? We need to support 10.2.8, 10.3 and 10.4. Thanks, ~ Chris -- Christopher Huyler Computer Associates Intl. _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker 2.0 packages not working in Panther
by Christopher Ryan 28 Jun '05

28 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Andy, Chris Mac OS X Installation & Setup Thanks! -- Andy _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/ryanc%40apple.com This email sent to ryanc(a)apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… We want people to move to using the CFBundleShortVersionString for versioning, but since other versions where used in the past we continue to use them as the overall version. In Tiger the internal 5 tuple version used to represent the version is made like this: CFBundleShortVersionString | SourceVersion | IFMinorVersion 0.0.0 | IFMajorVersion | minor " | major | 0 " | 0 (major and minor come from the package_version file, which is no longer needed) In Panther, a much less deterministic method was used (which is why we switched to this method in Tiger). Tiger's package maker no longer writes out the IFMajorVersion and IFMinorVersion because we want you to use CFBundleShortVersionString (which is shown as "Version" in Package Maker on Tiger). However, after looking into this problem for you, it looks as if Panther would only use the CFBundleShortVersionString if IFMajorVersion and IFMinorVersion are defined! So, it sounds like Package Maker needs to continue to write out these keys so that the Panther (and possibly Jaguar) installer looks at the CFBundleShortVersionString as the significant "bits". I've been updating some of my packages to the new PackageMaker 2.0.1 under Tiger, but I'm finding that while these work fine in Tiger, if I try to install an update of an existing package that had been previously installed in Panther, the new package fails, saying that ".A newer version of the package is already installed." Looking at the receipt of the original install (done under Panther with a package created with PackageMaker 1.2), I discovered that its Info.plist contains the two keys IFMajorVersion and IFMinorVersion, both set to 0. The new plist from PackageMaker 2.0.1 doesn't create these two keys. I believe this is what's causing the problem because if I either remove these two keys from the receipt package or add them to the new package, the install works under Panther. It would seem that the Installer that runs under Panther looks at these values and if they're missing, gets confused. I'm wondering if anyone else has encountered this problem and what sort workaround there might be (other than manually adding these two keys each time I build the package under Tiger). Is the new PackageMaker supposed to create packages that are backwards compatible to the Installer that runs under Panther? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Binary Format plist
by Stéphane Sudre 28 Jun '05

28 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On mardi, juin 28, 2005, at 05:30 PM, Eric Zimmerman wrote: Stéphane Sudre wrote: _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… This is certainly possible with a postflight script. I would not go with a full shell or applescript solution but use an additional binary. As this would allow to use the Open Directory API to get the list of users and their Home folder location and to use CoreFoundation or Foundation API to work with the Property List files that are probably being used (and since Apple is moving to Binary plist, I have some doubt it's possible to edit them from a shell script). The part about plist moving to binary is really sad. I use ANT to build all of my plists manually to automate my build process. Changing over to a binary format will make it much more difficult for me to support the Mac platform. I hope they maintain backwards compatibility or change their minds. I can't say for all Property List files. But AFAIK, all the preferences are now in binary format (NSUserDefaults default mode probably). This email sent to site_archiver(a)lists.apple.com

1 0

Re: Binary Format plist
by Peter Bierman 28 Jun '05

28 Jun '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Stéphane Sudre wrote: % plutil -convert xml1 /path/to/plist -pmb _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev(a)lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.… At 8:30 AM -0700 6/28/05, Eric Zimmerman wrote: This is certainly possible with a postflight script. I would not go with a full shell or applescript solution but use an additional binary. As this would allow to use the Open Directory API to get the list of users and their Home folder location and to use CoreFoundation or Foundation API to work with the Property List files that are probably being used (and since Apple is moving to Binary plist, I have some doubt it's possible to edit them from a shell script). The part about plist moving to binary is really sad. I use ANT to build all of my plists manually to automate my build process. Changing over to a binary format will make it much more difficult for me to support the Mac platform. I hope they maintain backwards compatibility or change their minds. The text XML plist format is transparently supported, and you can switch between the two using the 'plutil' command. Modifying an existing plist has always been risky, since you're editing another program's data structures. It's much better to use (or request via a bug) an API. This email sent to site_archiver(a)lists.apple.com

1 0