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

Re: Distribution Project Catch-22
by Bill Coderre 31 Mar '06

31 Mar '06

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: Distribution Project Catch-22
by Christopher Ryan 31 Mar '06

31 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Please let me know if you need an example. Chris Hi, Any ideas on how I can tell the user in 10.3 that they can't install? Wayne _______________________________________________ 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 _______________________________________________ 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.… Distribution Project, as created by Package Maker creates a meta package (.mpkg) with a Distribution (.dist) inside. On 10.4 the entire user experience and decisions are made from the distribution script alone, and the .mpkg acts purely as a bundle to hold distribution script resources (ReadMe, License, Localizations). On 10.3, the Meta Package acts like any old meta package, VolumeCheck scripts should run as normal and allow you to block the package from installing on previous systems (in fact, the VolumeCheck in the metapackage can always fail, since on newer systems, the Distribution script takes precedence. InstallationCheck's do not work from MetaPackages in 10.3 and earlier. We have a Distribution Project to install an app, Kexts, and a slew o' stuff into the System, Since one of the things is a new file system, we need it to be limited to 10.4, obviously. The problem is this; when someone tries to launch the installer (ignoring the System Requirements and the ReadMe - how strange) in 10.3, Installer launches with no interface. Since 10.3 ignores the Distribution.dist - and any scripts inside, putting in a VolumeCheck is worthless. I do have an InstallerCheck package in the bundle, and it works fine by itself, but when rolled into the metapackage, doesn't seem to have any effect - most likely because the distribution project is 10.4- only. So, it won't launch in 10.3 to display a message that it can't run - catch 22! This email sent to ryanc(a)apple.com This email sent to site_archiver(a)lists.apple.com

1 0

Distribution Project Catch-22
by Wayne Linder 31 Mar '06

31 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcZVCSDMX3w2/cD8EdqENwANk8GE7A== Thread-topic: Distribution Project Catch-22 User-agent: Microsoft-Entourage/11.2.3.060209 Hi, We have a Distribution Project to install an app, Kexts, and a slew o' stuff into the System, Since one of the things is a new file system, we need it to be limited to 10.4, obviously. The problem is this; when someone tries to launch the installer (ignoring the System Requirements and the ReadMe - how strange) in 10.3, Installer launches with no interface. Since 10.3 ignores the Distribution.dist - and any scripts inside, putting in a VolumeCheck is worthless. I do have an InstallerCheck package in the bundle, and it works fine by itself, but when rolled into the metapackage, doesn't seem to have any effect - most likely because the distribution project is 10.4-only. So, it won't launch in 10.3 to display a message that it can't run - catch 22! Any ideas on how I can tell the user in 10.3 that they can't install? Wayne _______________________________________________ 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: Building Package from command line failes with relative root path
by Oliver Leu (pcsag) 31 Mar '06

31 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Stéphane, thank you for your answer. I already was looking in the list and found some unanswered like: http://lists.apple.com/archives/installer-dev/2005/Dec/msg00026.html Oliver [...] The package could not be created because of the following errors: No root specified for archive. Made Package: --->nedit.ppc<--- </log> _______________________________________________ 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 there a known bug? Look in the archive of the list. I think it was discussed some time ago. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Building Package from command line failes with relative root path
by Stéphane Sudre 30 Mar '06

30 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On jeudi, mars 30, 2006, at 05:15 PM, Oliver Leu (pcsag) wrote: [...] The package could not be created because of the following errors: No root specified for archive. Made Package: --->nedit.ppc<--- </log> Look in the archive of the list. I think it was discussed some time ago. _______________________________________________ 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 there a known bug? This email sent to site_archiver(a)lists.apple.com

1 0

Building Package from command line failes with relative root path
by Oliver Leu (pcsag) 30 Mar '06

30 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Dear friends I've setup my package configuration using PackageMaker with GUI. The package could not be created because of the following errors: No root specified for archive. Made Package: --->nedit.ppc<--- </log> Is there a known bug? If yes, is there already a workaround? Thank you very much for your help! Greetings, Oliver *** Systemconfiguration: - PowerBook G4 - OS Tiger 10.4.5 - PackageMaker Version 2.1 (122) _______________________________________________ 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 having the following problem using PackageMaker to build packages from the commandline. When I choose "Contents" I specifiy the Rootpath absolute and building from command line works well: (Root: /Users/oli/PCSAG/Deployment/PACKAGES/PMCS/Release7/MacOSX/ Darwin-ppc-8.3.0/7_0_1/Packages/nedit.PPC) <log> Making Package: --->nedit.ppc<--- /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker -build -proj /Users/oli/PCSAG/Deployment/PACKAGES/PMCS/ Release7/MacOSX/Darwin-ppc-8.3.0/7_0_1/Package-Projects/ nedit.ppc.pmproj -p /Users/oli/PCSAG/Deployment/PACKAGES/PMCS/ Release7/MacOSX/Darwin-ppc-8.3.0/7_0_1/Build-MetaPackages/Packages/ nedit.ppc.pkg -v Creating Package Shell Scanning Package Root Copying Root to Temporary Build Directory Scanning Package Root Preserving File Resources Calculating Installed Size Creating BOM file Creating Archive Archiving... "./usr/local/bin/nedit" Removing Temporary Build Directory Creating Configuration Files Copying Interface Resources Made Package: --->nedit.ppc<--- </log> But when I set the root path with relative path and then try to build from the command line I get the following error: (Root: ../Packages/nedit.PPC) <-- Automatic generated by switching from "absolute" to "relative" <log> Making Package: --->nedit.ppc<--- /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker -build -proj /Users/oli/PCSAG/Deployment/PACKAGES/PMCS/ Release7/MacOSX/Darwin-ppc-8.3.0/7_0_1/Package-Projects/ nedit.ppc.pmproj -p /Users/oli/PCSAG/Deployment/PACKAGES/PMCS/ Release7/MacOSX/Darwin-ppc-8.3.0/7_0_1/Build-MetaPackages/Packages/ nedit.ppc.pkg -v This email sent to site_archiver(a)lists.apple.com

1 0

Authorization problems with Applescript as postflight script
by Michael Kiaer 30 Mar '06

30 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com I am having problems with using an Applescript as postflight script. Can anyone enlighten me? Thanks, Michael _______________________________________________ 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.… The package is created in Iceberg. The script writes some data to the netOctopus preference pane. The package requires root authentication. It works fine if logged as administrator but fails is logged in as user. It appears that the root privileges are not passed to the postflight script. I've never had this problem with shell scripts as postflight script but have run into this several times with Applescripts. I've tried saving the Applescript as application, application bundle, run only, but I've not been able to get around this issue. This email sent to site_archiver(a)lists.apple.com

1 0

PackageMaker 2.1 Issues
by Joannou Ng 21 Mar '06

21 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi folks, Just wondering if others are experiencing the same issues: Cheers, Joannou. _______________________________________________ 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.… First issue: When configuring a package using PackageMaker, the Authentication option in the Configuration tab gets reset to None occasionally after setting it to Root. Second issue: When editing package requirements in the Configuration tab, wouldn't it be great to have "Info from Property List" as a rule option? As a workaround, I currently specify "Info from Bundle", build the package, then edit "bundle" to "plist" in the built package's Info.plist. This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to make Installer Plugin work?
by Mike Fischer 19 Mar '06

19 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Paul, Am 19.03.2006 um 21:02 schrieb Paul Miller <paul(a)fxtech.com>: Indeed :-) Do you know if it is possible to create installer plugins using C++/Carbon instead of Objective C++/Cocoa? Actually it's Objective C not Objective C++. Mike -- Mike Fischer Softwareentwicklung, EDV-Beratung Schulung, Vertrieb Web: <http://homepage.mac.com/mike_fischer/index.html> Note: I read this list in digest mode! Send me a private copy for faster responses. _______________________________________________ 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.… Mike - good news. I'm pretty sure you could make most of your plugin use C/C++/Carbon if you wanted to. There is nothing preventing you from mixing ObjC/ Cocoa code with C/C++/Carbon. I'd say that you probably need to keep the basic ObjC structure as an interface to the InstallerPlugins.framework. Or at least you'd make your life way too difficult trying to get around that. It would probably be possible though since ObjC is based on C and anything you can do in ObjC you can also do with plain C - albeit less elegantly. The ObjC syntax is not hard to learn though if that's your concern. Given that there is no documentation other than the ObjC framework headers at the moment, you already have enough problems to deal with, I'd say. Me, I don't care. I'll use ObjC/Cocoa and if I need something from Carbon I'll just call a Carbon API. The Integration of Interface Builder is way better for Cocoa than it is for Carbon so for the UI part Cocoa is actually a solid advantage, maybe even a requirement. Also mixing a Carbon UI with Cocoa UI tends to be difficult and the Apple Installer seems to be based on Cocoa. So, as the saying goes: when in Rome... This email sent to site_archiver(a)lists.apple.com

1 0

Re: How to make Installer Plugin work?
by Paul Miller 19 Mar '06

19 Mar '06

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com User-agent: Thunderbird 1.5 (Windows/20051201) Answering my own post... Mike - good news. -- Paul Miller | paul(a)fxtech.com | www.fxtech.com | Got Tivo? _______________________________________________ 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.… Mike Fischer wrote: Nevermind, I figured it out. The InstallerSections.plist must be in Contents/Plugins/ of the .pkg not in Contents/. My Installer Plugin now loads and its UI displays just fine. The NSLogs I put into my code indicate that the overridden methods of the pane class are called just fine. Do you know if it is possible to create installer plugins using C++/Carbon instead of Objective C++/Cocoa? This email sent to site_archiver(a)lists.apple.com

1 0