March 2008 - Installer-dev - lists.apple.com

Re: Question about plugins and shouldExitPane
by Dan Spirlock 28 Mar '08

28 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Stéphane, Thanks again for your reply. -Dan On Mar 27, 2008, at 6:00 PM, Stéphane Sudre wrote: On Mar 27, 2008, at 11:23 PM, Dan Spirlock wrote: Hi All, - (void) willExitPane:(InstasllerSectionDirection)dir { if(dir == InstallerDirectionBackward) { // Do some stuff } } It works fine on my Mac OS X 10.4 system: - (void) willExitPane:(InstallerSectionDirection) inDirection { NSLog(@"%d",inDirection); } _______________________________________________ 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.… Thank you for the reply. You are correct. The plugin demo project catches the back button in the shouldExitPane method, but my modified project does not. I'll have to take a closer look and see, as you said, if there are any missing connections. In any case, the documentation for the direction parameter in InstallerPane.h file are incorrect for shouldExitPane. I have been playing with the installer plugin sample project and have gotten things mostly working. One thing I did notice is that if I override shouldExitPane, it only gets called if the user clicks the "Continue" button. It doesn't get called if the user clicks the "Go back" button. What method needs to be overridden to catch this? I tried willExitPane and checking like this: but it doesn't enter this function. The header file documentation for shouldExitPane says the "dir" parameter is the direction in which the pane was entered, which seems strange because for all of the other ExitPane methods the "dir" parameter is the direction you are exiting the pane. If anyone has any info on this, it would be appreciated. Could it be a missing connection or an incorrect class name set in the nib file? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Question about plugins and shouldExitPane
by Stéphane Sudre 28 Mar '08

28 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 27, 2008, at 11:23 PM, Dan Spirlock wrote: Hi All, - (void) willExitPane:(InstasllerSectionDirection)dir { if(dir == InstallerDirectionBackward) { // Do some stuff } } It works fine on my Mac OS X 10.4 system: - (void) willExitPane:(InstallerSectionDirection) inDirection { NSLog(@"%d",inDirection); } _______________________________________________ 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 been playing with the installer plugin sample project and have gotten things mostly working. One thing I did notice is that if I override shouldExitPane, it only gets called if the user clicks the "Continue" button. It doesn't get called if the user clicks the "Go back" button. What method needs to be overridden to catch this? I tried willExitPane and checking like this: but it doesn't enter this function. The header file documentation for shouldExitPane says the "dir" parameter is the direction in which the pane was entered, which seems strange because for all of the other ExitPane methods the "dir" parameter is the direction you are exiting the pane. If anyone has any info on this, it would be appreciated. Could it be a missing connection or an incorrect class name set in the nib file? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Question about plugins and shouldExitPane
by Mike 27 Mar '08

27 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Thunderbird 2.0.0.12 (Macintosh/20080213) typedef enum{ InstallerDirectionForward = 0, InstallerDirectionBackward, InstallerDirectionUndefined } InstallerSectionDirection; -willEnterPane:(InstallerSectionDirection)dir Mike Dan Spirlock wrote: Hi All, - (void) willExitPane:(InstasllerSectionDirection)dir { if(dir == InstallerDirectionBackward) { // Do some stuff } } If anyone has any info on this, it would be appreciated. Thanks, Dan ------------------------------------------------------------------------ _______________________________________________ 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/lists%40michael-amoros… _______________________________________________ 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.… Try -willEnterPane but check the direction. See InstallerPane.h in the framework for a description of how it works: /*! @enum InstallerSectionDirection @discussion Describes the direction in which a pane is entered or exited. @constant InstallerDirectionForward Specifies that the pane was entered/exited while moving in the forward direction. @constant InstallerDirectionBackward Specifies that the pane was entered/exited while moving backwards. @constant InstallerDirectionUndefined Specifies that the pane was entered/exited using the gotoPane: method. Since the pane is "jumped" to rather than moved to going forward or back, InstallerDirectionUndefined is used. */ Many of the methods in the framework pass a direction parameter that you can check to determine the direction: I have been playing with the installer plugin sample project and have gotten things mostly working. One thing I did notice is that if I override shouldExitPane, it only gets called if the user clicks the "Continue" button. It doesn't get called if the user clicks the "Go back" button. What method needs to be overridden to catch this? I tried willExitPane and checking like this: but it doesn't enter this function. The header file documentation for shouldExitPane says the "dir" parameter is the direction in which the pane was entered, which seems strange because for all of the other ExitPane methods the "dir" parameter is the direction you are exiting the pane. This email sent to lists(a)michael-amorose.com This email sent to site_archiver(a)lists.apple.com

1 0

Question about plugins and shouldExitPane
by Dan Spirlock 27 Mar '08

27 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.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.… This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker & Custom Folder Icons
by Paul Cook 27 Mar '08

27 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Best Wishes, Paul Best of luck, Andrew Stéphane Sudre, Thanks very much for the needed refresher course & your help. Best Wishes, Paul On which OS are you observing this issue? o First, a refresher on custom folder icons: * Icon\r file * Folder: A which only contains the data fork part of A ._A which contains the finder Info and the resource fork of A My $0.02 -- Stephane Any ideas? Best Wishes, Paul _______________________________________________ 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.… Thank you very much. Some of this is new, so it may take me a while to figure it out. But, I do expect that I and others will find it useful. On Mar 27, 2008, at 12:07 PM, Andrew wrote: Paul, I'd prefer not to spread my contact information, but feel free to share the information part of this email with the list if you find it useful. Our installers do three things to get custom folder icons to appear properly in a variety of OS versions: 1. Install an Icon^M file (same as Icon\r as Stephen indicates). In bash, you can form this file name using Icon$'\r' or "$ {SOME_PARENT}"/Icon$'\r' 2. Set the custom icon bit on the enclosing folder. We do this by "find"ing Icon^M files in our installation and then running a custom tool on the parent directory paths. Depending on your scripting ability and environment, it may be simpler to just use a fixed path. You could test this step using the developer tool SetFile, however, I would be surprised if you could ship with that. 3. Refresh the Finder's view of the folder. Historically we have done this via an AppleScript that tells the Finder to iterate all its windows and update the items of each one. More recently we have had success asking the Finder to update all the parent directory paths up to and including the one getting the custom icon. There are other gyrations such as deleting or replacing .DS_Store files and restarting the Finder that can be done, however, the above approaches work pretty reliably and have the benefit of not losing data such as window layouts. On Mar 27, 2008, at 7:21 AM, Paul Cook wrote: In answer to your question, we were observing this issue on Leopard 10.5.2. Leopard 10.5.2 was used to create the packages and it was also the target. I'll try to see if the "kHasCustomIcon" is being set on the folder. That sounds like a good lead. Custom Folder icons has a troubled history with Installer.app and Mac OS X. To have a custom folder icon you need to have both an invisible Icon \r file inside the folder and some flags set on the folder itself. It is a Resource fork file. The different icon representations are stored in 'icns' resource -16455. The file type is 'icon', the creator is 'MACS'. The FileInfo finderFlags for this file has the kIsInvisible flag set The FolderInfo finderFlags for the folder has the kHasCustomIcon flag set. o This means that in order to have a custom folder icon, a package needs to both retain the resource fork of the Icon\r file and the Finder flags. This is done through the split forks operation that creates the Apple Double format file. A file A may end up through this process as 2 files: I filed a bug report (Problem ID: 3635123 04/27/2004 which is said to be a duplicate of 3551477). At the time, the issue was that the kHasCustomIcon was not set back on the folder upon installation. I can't say whether the bug was fixed or not on the OS I was observing it because the report was marked as duplicate. On Mar 26, 2008, at 3:38 PM, Paul Cook wrote: Does anyone know how to get Apple's PackageMaker to handle custom folder icons? I'm not really a developer. But in order to install software via Apple Remote Desktop or as part of OS-X Servers NetInstall, it has to be in an Apple style package. So we are repackaging some software with PackageMaker. And this seems to be the most appropriate list for PackageMaker questions. Generally, things are working well, except that, when we run the installers, folders have lost their custom icons. Otherwise, if there are other problems, we haven't yet noticed them. One example is, we were trying to repackage Office 2004 into a package so that it could be installed by Leopard Server's NetInstall feature. Other than being big, there doesn't appear to be anything too complicated here. The created install works fine, except the Office 2004 folder icon is missing. Although, if I do an ls -Gal of the folder created with the installer, there is a .Icon file there. Since Office is so huge, to make testing quicker, we created a new, folder with just a simple text file in it and using finder's Get Info, we copied the icon from the original Office 2004 folder and pasted it into the test folder. It seems to recreate the problem fine. The package creates a the folder, as it should, except no custom icon displays. I'm using the Leopard Developer Utilities on a Mac running the current version of Leopard. Based on some google hits for the problem, I've played with trying to not filter out the .DS_Store files. We've tried playing with what is the root for the package. And we put the source for Package Maker onto a UFS disk image to force any resources into Apple Double format. (One hit suggested that PackageMaker didn't properly handle resource forks. Is true?) We have also looked at what Apple documentation we could find on how to use PackageMaker. We didn't want to let a little think like an Icon be a blemish on the quality of the effort, but after about 5 hours on this little icon problem, we decided to take a break. _______________________________________________ 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/cook.p.d% 40comcast.net This email sent to cook.p.d(a)comcast.net _______________________________________________ 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/matheson% 40adobe.com This email sent to matheson(a)adobe.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: Metapackage that can install depending on architecture
by Nigel Kersten 27 Mar '08

27 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.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.… On Mar 26, 2008, at 6:47 AM, Ted Brown wrote: Some people re-package other companies installers so that they can easily deploy them. Making a universal binary isn't an option. One would think Adobe would be able to figure out how to make a universal binary. But there are still separate installers for the Flash Player (even though one is called "UB".) It is odd how Adobe are doing this, but we've tested the UB version on PPC quite a lot, and have had no problems with it. This also gets around the horrible Adobe installer that asks for elevated privileges and then decides not to use them when it scans / Applications for app bundles that it thinks need updating. This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker & Custom Folder Icons
by Paul Cook 27 Mar '08

27 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Stéphane Sudre, Thanks very much for the needed refresher course & your help. Best Wishes, Paul On which OS are you observing this issue? o First, a refresher on custom folder icons: * Icon\r file * Folder: A which only contains the data fork part of A ._A which contains the finder Info and the resource fork of A My $0.02 -- Stephane Any ideas? Best Wishes, Paul _______________________________________________ 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.… In answer to your question, we were observing this issue on Leopard 10.5.2. Leopard 10.5.2 was used to create the packages and it was also the target. I'll try to see if the "kHasCustomIcon" is being set on the folder. That sounds like a good lead. Custom Folder icons has a troubled history with Installer.app and Mac OS X. To have a custom folder icon you need to have both an invisible Icon \r file inside the folder and some flags set on the folder itself. It is a Resource fork file. The different icon representations are stored in 'icns' resource -16455. The file type is 'icon', the creator is 'MACS'. The FileInfo finderFlags for this file has the kIsInvisible flag set The FolderInfo finderFlags for the folder has the kHasCustomIcon flag set. o This means that in order to have a custom folder icon, a package needs to both retain the resource fork of the Icon\r file and the Finder flags. This is done through the split forks operation that creates the Apple Double format file. A file A may end up through this process as 2 files: I filed a bug report (Problem ID: 3635123 04/27/2004 which is said to be a duplicate of 3551477). At the time, the issue was that the kHasCustomIcon was not set back on the folder upon installation. I can't say whether the bug was fixed or not on the OS I was observing it because the report was marked as duplicate. On Mar 26, 2008, at 3:38 PM, Paul Cook wrote: Does anyone know how to get Apple's PackageMaker to handle custom folder icons? I'm not really a developer. But in order to install software via Apple Remote Desktop or as part of OS-X Servers NetInstall, it has to be in an Apple style package. So we are repackaging some software with PackageMaker. And this seems to be the most appropriate list for PackageMaker questions. Generally, things are working well, except that, when we run the installers, folders have lost their custom icons. Otherwise, if there are other problems, we haven't yet noticed them. One example is, we were trying to repackage Office 2004 into a package so that it could be installed by Leopard Server's NetInstall feature. Other than being big, there doesn't appear to be anything too complicated here. The created install works fine, except the Office 2004 folder icon is missing. Although, if I do an ls -Gal of the folder created with the installer, there is a .Icon file there. Since Office is so huge, to make testing quicker, we created a new, folder with just a simple text file in it and using finder's Get Info, we copied the icon from the original Office 2004 folder and pasted it into the test folder. It seems to recreate the problem fine. The package creates a the folder, as it should, except no custom icon displays. I'm using the Leopard Developer Utilities on a Mac running the current version of Leopard. Based on some google hits for the problem, I've played with trying to not filter out the .DS_Store files. We've tried playing with what is the root for the package. And we put the source for Package Maker onto a UFS disk image to force any resources into Apple Double format. (One hit suggested that PackageMaker didn't properly handle resource forks. Is true?) We have also looked at what Apple documentation we could find on how to use PackageMaker. We didn't want to let a little think like an Icon be a blemish on the quality of the effort, but after about 5 hours on this little icon problem, we decided to take a break. _______________________________________________ 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/cook.p.d% 40comcast.net This email sent to cook.p.d(a)comcast.net This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker & Custom Folder Icons
by Stéphane Sudre 26 Mar '08

26 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 26, 2008, at 9:38 PM, Paul Cook wrote: On which OS are you observing this issue? o First, a refresher on custom folder icons: * Icon\r file * Folder: A which only contains the data fork part of A ._A which contains the finder Info and the resource fork of A My $0.02 -- Stephane _______________________________________________ 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 how to get Apple's PackageMaker to handle custom folder icons? I'm not really a developer. But in order to install software via Apple Remote Desktop or as part of OS-X Servers NetInstall, it has to be in an Apple style package. So we are repackaging some software with PackageMaker. And this seems to be the most appropriate list for PackageMaker questions. Generally, things are working well, except that, when we run the installers, folders have lost their custom icons. Otherwise, if there are other problems, we haven't yet noticed them. One example is, we were trying to repackage Office 2004 into a package so that it could be installed by Leopard Server's NetInstall feature. Other than being big, there doesn't appear to be anything too complicated here. The created install works fine, except the Office 2004 folder icon is missing. Although, if I do an ls -Gal of the folder created with the installer, there is a .Icon file there. Since Office is so huge, to make testing quicker, we created a new, folder with just a simple text file in it and using finder's Get Info, we copied the icon from the original Office 2004 folder and pasted it into the test folder. It seems to recreate the problem fine. The package creates a the folder, as it should, except no custom icon displays. I'm using the Leopard Developer Utilities on a Mac running the current version of Leopard. Based on some google hits for the problem, I've played with trying to not filter out the .DS_Store files. We've tried playing with what is the root for the package. And we put the source for Package Maker onto a UFS disk image to force any resources into Apple Double format. (One hit suggested that PackageMaker didn't properly handle resource forks. Is true?) We have also looked at what Apple documentation we could find on how to use PackageMaker. We didn't want to let a little think like an Icon be a blemish on the quality of the effort, but after about 5 hours on this little icon problem, we decided to take a break. Any ideas? Custom Folder icons has a troubled history with Installer.app and Mac OS X. To have a custom folder icon you need to have both an invisible Icon \r file inside the folder and some flags set on the folder itself. It is a Resource fork file. The different icon representations are stored in 'icns' resource -16455. The file type is 'icon', the creator is 'MACS'. The FileInfo finderFlags for this file has the kIsInvisible flag set The FolderInfo finderFlags for the folder has the kHasCustomIcon flag set. o This means that in order to have a custom folder icon, a package needs to both retain the resource fork of the Icon\r file and the Finder flags. This is done through the split forks operation that creates the Apple Double format file. A file A may end up through this process as 2 files: I filed a bug report (Problem ID: 3635123 04/27/2004 which is said to be a duplicate of 3551477). At the time, the issue was that the kHasCustomIcon was not set back on the folder upon installation. I can't say whether the bug was fixed or not on the OS I was observing it because the report was marked as duplicate. This email sent to site_archiver(a)lists.apple.com

1 0

PackageMaker & Custom Folder Icons
by Paul Cook 26 Mar '08

26 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Any ideas? Best Wishes, Paul _______________________________________________ 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 how to get Apple's PackageMaker to handle custom folder icons? I'm not really a developer. But in order to install software via Apple Remote Desktop or as part of OS-X Servers NetInstall, it has to be in an Apple style package. So we are repackaging some software with PackageMaker. And this seems to be the most appropriate list for PackageMaker questions. Generally, things are working well, except that, when we run the installers, folders have lost their custom icons. Otherwise, if there are other problems, we haven't yet noticed them. One example is, we were trying to repackage Office 2004 into a package so that it could be installed by Leopard Server's NetInstall feature. Other than being big, there doesn't appear to be anything too complicated here. The created install works fine, except the Office 2004 folder icon is missing. Although, if I do an ls -Gal of the folder created with the installer, there is a .Icon file there. Since Office is so huge, to make testing quicker, we created a new, folder with just a simple text file in it and using finder's Get Info, we copied the icon from the original Office 2004 folder and pasted it into the test folder. It seems to recreate the problem fine. The package creates a the folder, as it should, except no custom icon displays. I'm using the Leopard Developer Utilities on a Mac running the current version of Leopard. Based on some google hits for the problem, I've played with trying to not filter out the .DS_Store files. We've tried playing with what is the root for the package. And we put the source for Package Maker onto a UFS disk image to force any resources into Apple Double format. (One hit suggested that PackageMaker didn't properly handle resource forks. Is true?) We have also looked at what Apple documentation we could find on how to use PackageMaker. We didn't want to let a little think like an Icon be a blemish on the quality of the effort, but after about 5 hours on this little icon problem, we decided to take a break. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Metapackage that can install depending on architecture
by Ted Brown 26 Mar '08

26 Mar '08

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Mar 25, 2008, at 8:19 PM, Andy Mroczkowski wrote: To restrict the package to Intel only do the following: - Select the Choice you want to set an architecture requirement for - Click the 'Requirements' Tab - Add a new Requirement with the '+' button - Set the following values: If: Result of Gestalt value: sysa is: == 10 Selected: NO Enabled: NO Then do the same for the PPC choice, replacing the 10 with 2. --- Andy Mroczkowski Mac Developer, NeatReceipts Hi there: Any pointers are appreciated. Cheers I really like how the values differ from the Gestalt call. _______________________________________________ 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.… If you are using the PackageMaker 3 GUI, this is fairly easy. You can add Requirements for package choices (subpackages of a metapackage). Requirements can check results of Gestalt directly, which can be used to detect the current architecture. The applicable Gestalt key is 'sysa' and the result codes for Intel and PPC are 10 and 2 respectively. There are probably other solutions, but this works for me. I would suggest just using a Universal binary if it makes sense though. On Mar 25, 2008, at 5:11 PM, Roy Marquez wrote: I'm fairly new to using PackageMaker as I have used it to package smaller applications and such, but haven't used it extensively. I have a project and would appreciate any guidance that the more experienced folks (you) can provide. I have application "A". This application comes in two version: PPC and Intel. I have built 2 separate packages. What I would ideally like to build is a metapackage installer that can detect the machine architecture type and install the correct package for the architecture. But I have no clue as to where to start as to how to get that working. From my reading, it looks like I will be needing a script that would do this. But other than this, I have no clue where to start looking for literature that documents this. This would be the only need I have as far as this is concerned. Roy Some people re-package other companies installers so that they can easily deploy them. Making a universal binary isn't an option. One would think Adobe would be able to figure out how to make a universal binary. But there are still separate installers for the Flash Player (even though one is called "UB".) I'm using sysctl 'hw.cputype'. Intel = '7' and PPC = '18'. I think I settled on using sysctl as I'm a unix geek, and it's something that I can implement from the command line using tools that I'd already used (sysctl). Follow the above step, only use "Result of Sysctl". Use "hw.cputye" as the value. I call PackageMaker from the command line, and I generate my own distribution.dist file. Having done that, It's much easier to do this from the GUI. If someone cares, I can post an example distribution.dist CPU detection example, but it's easy to have Packagemaker make you one and read what it generates. This email sent to site_archiver(a)lists.apple.com

1 0