November 2007 - Installer-dev

Re: Is there/will there be uninstall supported in PackageMaker v3.0?
by Don Montalvo 13 Nov '07

13 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Don _______________________________________________ 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.… "Perbix, Michael" <PERBIX(a)lmsd.org> wrote: FYI, InstallEase from LANRev has an option to create an Uninstall package when you use it to create the install package...all it does is create an empty installer with a shell script removing everything that was installed. -Mike Does it restore updated files that were overwritten? Does it set [back] permissions that were changed during the install? Just curious how effective a script that "removes everything that was installed" would be? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard installer too smart and overwrite existing app
by Nathan Duran 13 Nov '07

13 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Nov 12, 2007, at 3:09 PM, Martin Bestmann 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.… Does anyone know if there is a way to tell packagemaker via command line on Leopard to not be "smart" and NOT add the "IFPkgPathMappings" or is my only option to manually remove the "IFPkgPathMappings" key from the "info.plist" after the creation of the package? I too have had zero luck with Tiger compatible build options--the packages my original build scripts produced with them just gave some nonsensical -1 error when double clicked and that was pretty much it. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard installer too smart and overwrite existing app
by Martin Bestmann 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On 12.11.2007, at 23:31, Stéphane Sudre wrote: On lundi, novembre 12, 2007, at 10:03 PM, Martin Bestmann wrote: Hi, Well, it's not a bug, it's a feature! Hi Stéphane, -build -p -r -b -s -i -d -r Thanks, Martin _______________________________________________ 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'm facing a very odd issue with the Leopard installer. Here is what I have: I have a folder called /myApps in the root of my disk. Inside that folder is a bundled Cocoa app called myDemoApp. Now I want to install a copy of that app with the name "myDemoApp Copy". To do this I duplicate myDemoApp and create a new installer package using PackageMaker (destination "/myApps"). When installing this package, it will NOT create a new app "myDemoApp Copy" but rather update the existing app "myDemoApp" in "/myApps". [...] I've filed this as RADAR #5595385. In PackageMaker 3, by default, when you add an application, a relocator will be automatically created for it. Check the components panes of the package for your application bundle in PackageMaker 3. You will need to uncheck the Allow Relocation option. Be sure to have a different identifier for your package if you want to have both applications at the same time. you were pointing me to the right direction. The problem is not in the installer (because as you said the token search is really inside the package) but the problem is in the packagemaker command line tool. We are calling package maker from the command line with the following (Tiger compatible) command line options: We even provide the info.plist file. It seems to me that the packagemaker adds the "IFPkgPathMappings" automatically by default. Which I think is not the right thing to do. Does anyone know if there is a way to tell packagemaker via command line on Leopard to not be "smart" and NOT add the "IFPkgPathMappings" or is my only option to manually remove the "IFPkgPathMappings" key from the "info.plist" after the creation of the package? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard installer too smart and overwrite existing app
by Nathan Duran 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Nov 12, 2007, at 2:31 PM, 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.… In PackageMaker 3, by default, when you add an application, a relocator will be automatically created for it. Check the components panes of the package for your application bundle in PackageMaker 3. You will need to uncheck the Allow Relocation option. The problem that I have encountered in my own projects is that this option (which isn't very well named in my opinion) doesn't like to stay unchecked, and will frequently turn itself back on of its own accord once I hit "Save." So far I've only seen it in older projects I've updated for Leopard. The only way I've been able to get rid of the problem is by creating brand new projects. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Developer Tools
by Stéphane Sudre 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On lundi, novembre 12, 2007, at 09:50 PM, Jeff Vandehey 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.… Hello, I am re-working our imaging strategy for a mid-size office. I have a shell script that creates a sparse image, and applies the OS, and any custom packages to the sparse image. This is working great for fairly generic packages, but I'm having some problems with Developer Tools. I downloaded the xcode 3.0 DMG. It contains a main package installer, and a couple of sub-packages. I cannot get the developer tools to install, because the package requires that I be booted off an active 10.5 volume. This causes a failure when I am trying to set the 10.5 sparse image as the destination. As I'm not 100% sure to understand your install scenario, just in case you're trying to install the package when running on 10.4, the answer is you can't. The Xcode package is "distributed" using the new Flat package format. If you're running on 10.5, a possible exploration path is to open the package using the Flat Package Editor, drag the Distribution file to the Desktop, edit it with a text editor, slaughter the volumecheck() method so that it just returns true. And then move the text distribution file back to the package. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard installer too smart and overwrite existing app
by Martin Bestmann 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On 12.11.2007, at 22:51, Nathan Duran wrote: On Nov 12, 2007, at 1:30 PM, Martin Bestmann wrote: http://www.khiltd.com/images/iWorkInstaller.jpg Martin _______________________________________________ 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.… But if you e.g. install two different versions (myDemo App 1.0 and myDemo App 2.0) of the same app (still having the same bundle identifier) then you do NOT want this behavior. Take iWorks e.g. you have version 06 and version 08 and both of the Keynote apps have the same bundle identifier. So this "smart" behaviour of the installer is not good, at least not as the default mode. OK, so if we keep using iWork as an example, notice that it creates separate folders for each full release in order to avoid this confusion: You're trying to force them into the same place, which I, as a user, would consider more unusual than what Installer.app is doing. How are you specifying the destination in your project/build script? As I wrote in my post the destination location doesn't matter. If you remove the original app from the location you want to install the app to and the app is located somewhere else it'll install it in that location where ti finds the app. The only time it really installs the app as intended is when the original app doesn't exist at all. To be honest I've not tried to install iWorks 08 over and existing iWorks 06 installation on Leopard. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard installer too smart and overwrite existing app
by Stéphane Sudre 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On lundi, novembre 12, 2007, at 10:03 PM, Martin Bestmann wrote: Hi, Well, it's not a bug, it's a feature! _______________________________________________ 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'm facing a very odd issue with the Leopard installer. Here is what I have: I have a folder called /myApps in the root of my disk. Inside that folder is a bundled Cocoa app called myDemoApp. Now I want to install a copy of that app with the name "myDemoApp Copy". To do this I duplicate myDemoApp and create a new installer package using PackageMaker (destination "/myApps"). When installing this package, it will NOT create a new app "myDemoApp Copy" but rather update the existing app "myDemoApp" in "/myApps". [...] I've filed this as RADAR #5595385. In PackageMaker 3, by default, when you add an application, a relocator will be automatically created for it. Check the components panes of the package for your application bundle in PackageMaker 3. You will need to uncheck the Allow Relocation option. Be sure to have a different identifier for your package if you want to have both applications at the same time. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard installer too smart and overwrite existing app
by Nathan Duran 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Nov 12, 2007, at 1:30 PM, Martin Bestmann wrote: http://www.khiltd.com/images/iWorkInstaller.jpg _______________________________________________ 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.… But if you e.g. install two different versions (myDemo App 1.0 and myDemo App 2.0) of the same app (still having the same bundle identifier) then you do NOT want this behavior. Take iWorks e.g. you have version 06 and version 08 and both of the Keynote apps have the same bundle identifier. So this "smart" behaviour of the installer is not good, at least not as the default mode. OK, so if we keep using iWork as an example, notice that it creates separate folders for each full release in order to avoid this confusion: You're trying to force them into the same place, which I, as a user, would consider more unusual than what Installer.app is doing. How are you specifying the destination in your project/build script? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard installer too smart and overwrite existing app
by Martin Bestmann 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On 12.11.2007, at 22:21, Nathan Duran wrote: On Nov 12, 2007, at 1:03 PM, Martin Bestmann wrote: Martin _______________________________________________ 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.… Is this an intended behaviour? Bundles are more accurately identified via (gasp!) bundle identifiers, not names, which are easily changed/mangled by the user. I've honestly never tried installing two copies of the same application in the same folder before, but I can't think of a good reason why I'd need to, either, so I think it's understandable if the Installer is getting confused by what you're asking it to do. But if you e.g. install two different versions (myDemo App 1.0 and myDemo App 2.0) of the same app (still having the same bundle identifier) then you do NOT want this behavior. Take iWorks e.g. you have version 06 and version 08 and both of the Keynote apps have the same bundle identifier. So this "smart" behaviour of the installer is not good, at least not as the default mode. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Leopard installer too smart and overwrite existing app
by Nathan Duran 12 Nov '07

12 Nov '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Nov 12, 2007, at 1:03 PM, Martin Bestmann wrote: Is this an intended behaviour? Bundles are more accurately identified via (gasp!) bundle identifiers, not names, which are easily changed/mangled by the user. I've honestly never tried installing two copies of the same application in the same folder before, but I can't think of a good reason why I'd need to, either, so I think it's understandable if the Installer is getting confused by what you're asking it to do. _______________________________________________ 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