September 2007 - Installer-dev

Re: Authentication resetting itself?
by Jack Repenning 26 Sep '07

26 Sep '07

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

Authentication resetting itself?
by Marco Salsiccia 25 Sep '07

25 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi everyone, Anyone else seeing this? Is there a fix in the works? Cheers, Marco Salsiccia _______________________________________________ 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 know if this has been covered previously, but I'm running into a bit of an annoying bug with the Authentication pop-up in the Configuration tab. I usually build my installers along the tabs...setting up the interface, then the contents, configuring it all, adding scripts, then setting the package version and building. If I set the Authentication to Administrator, then click to the Scripts or Package Version tabs, then click back on the Configuration tab, the Authentication pop-up is set back to none. In order for the Authentication to 'stick', I have to build the package with the Config tab open so I can physically see that the Authentication is being set. If I build it from any other tab after setting it, the Authentication is set back to none. This email sent to site_archiver(a)lists.apple.com

1 0

What's the identifier for my.target.receiptForIdentifier?
by John Cebasek 25 Sep '07

25 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acf/rnZztLlpJmuhEdybpAAX8gGyMA== Thread-topic: What's the identifier for my.target.receiptForIdentifier? User-agent: Microsoft-Entourage/11.3.6.070618 Hi All: What's the identifier to use in the API my.target.receiptForIdentifier? It's the CFBundleIdentifier from the info.plist in the receipt's package, correct? Thanks in advance for your time. John Cebasek _______________________________________________ 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-packaging Office 2004
by Shane Dixon 24 Sep '07

24 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acf+2qga5od7jGrNEdyuWwAX8tZq7A== Thread-topic: Re-packaging Office 2004 User-agent: Microsoft-Entourage/11.3.6.070618 _______________________________________________ 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

Obtaining XML tags
by John Cebasek 24 Sep '07

24 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: Acf+1cf7BmfMDWrJEdyu2gAX8gGyMA== Thread-topic: Obtaining XML tags User-agent: Microsoft-Entourage/11.3.6.070618 Hi All: Maybe I'm missing something, but I can't seem to find a way to get some of the definitions as described in the document: http://developer.apple.com/releasenotes/Developertools/Installer.html I want to get installKBytes from pkg-ref in a script. Can someone point me in the right direction? Thanks in advance for your time. John Cebasek _______________________________________________ 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: font colours of steps in package maker
by Peter Bierman 21 Sep '07

21 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Nope, you can't change these UI elements. -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 4:00 PM -0700 9/21/07, bert wrote: Since my background is mostly black, I would need this text to show up in red or white or some other colour, but not in black. Also to the right side of the screen there is a text box for displaying license text and so on, and I'd like to remove the 50% opacity white backgorund for this background since there are no graphics on the black background anyways. are these cosmetic changes possible? I searched for some options in Package Maker but couldn't find any. This email sent to site_archiver(a)lists.apple.com

1 0

font colours of steps in package maker
by bert 21 Sep '07

21 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=cwI6fJKFP3oWDf/5g/Xh+iPI6ixDUMof4RdL1L0FBfxVX/ws5Dk295jkoGiqDkm7VriUSJ4zu8D0ZgNvkRt6yUjq+z8K4S6wkThYrUDLweMrKo7NHtLhK0wfEtxFIkB8cWi0fLzege7EbEyArPEZAg4cqCgUHgQ3sVRNEJpeqcM=; _______________________________________________ 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: Check for file before installing
by Peter Bierman 21 Sep '07

21 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 21, 2007, at 11:46 AM, Peter Bierman wrote: -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 12:32 PM -0700 9/21/07, Jack Repenning wrote: While I agree that this situation makes life hard for the installer, the Mac OS X Installer handles this as well as can be expected. The OS itself installs many many files that overlap between packages. The consequences are that when multiple packages own the same file, upgrading any one of those packages has the potential to replace or remove that file, leaving the other packages in an inconsistent state. When you know the circumstances of upgrading, you can work around this issue. For example, with Annette's issue, if she replaces a font that should exist anyway, then system upgrades will update or replace that font as necessary. Sure, I didn't mean to dis the Apple installer. But we're still -- inescapably, so far as I can see -- left with those potential inconsistent states. If for example, Annette cares about this font because she wants to use it (seems a safe guess!), and she wants to use this particular font because its metrics make some tricky form layout work better than any other font (wouldn't surprise me, given her return address and implied product), then a change to the font that altered the layout metrix (a thing outside her control, since she doesn't actually own this font) would be a big deal for her: when half her customers start complaining that the form lays out wrong, she'll have a very hard time figuring out why it fails at all ("works for me"), let alone why it only fails for half her customers. Absolutely. Those are all big warning flags for anyone going into this situation. The most obvious solution would be for Annette to ship her own copy of the font in a location private to her software. But she's chosen to use a system font. Her software is making an API contract with the OS over that font. She's trusting that Apple will only alter that font in compatible ways (which may or may not be true over a long timeframe.) Presumably the risk of using the system font is outweighed by other factors such as its availability. (Although if she has permission to ship it to repair a broken system, she probably has permission to install it somewhere private.) The biggest risk here is probably to the OS itself. Annette's product will continue to install that font even after the OS removes it. If the OS does remove it, it'll probably be for a good reason. That illustrates the common problem with multiple packages owning the same file... any of the several owners could choose to remove the file. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Check for file before installing
by Stéphane Sudre 21 Sep '07

21 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On vendredi, septembre 21, 2007, at 09:32 PM, Jack Repenning wrote: On Sep 21, 2007, at 11:46 AM, Peter Bierman wrote: My $0.02 _______________________________________________ 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.… While I agree that this situation makes life hard for the installer, the Mac OS X Installer handles this as well as can be expected. The OS itself installs many many files that overlap between packages. The consequences are that when multiple packages own the same file, upgrading any one of those packages has the potential to replace or remove that file, leaving the other packages in an inconsistent >> state. When you know the circumstances of upgrading, you can work around this issue. For example, with Annette's issue, if she replaces a font that should exist anyway, then system upgrades will update or replace that font as necessary. Sure, I didn't mean to dis the Apple installer. But we're still -- inescapably, so far as I can see -- left with those potential inconsistent states. If for example, Annette cares about this font because she wants to use it (seems a safe guess!), and she wants to use this particular font because its metrics make some tricky form layout work better than any other font (wouldn't surprise me, given her return address and implied product), then a change to the font that altered the layout metrix (a thing outside her control, since she doesn't actually own this font) would be a big deal for her: when half her customers start complaining that the form lays out wrong, she'll have a very hard time figuring out why it fails at all ("works for me"), let alone why it only fails for half her customers. Hmm, I think there's one point that has not been taken into consideration. It's not because a file is not where it has been installed that it's not there. Let's have a look at the case of a Font file. Some utilities lets you disable Fonts by moving them to the Fonts (Disabled). I wrote a tool that does this and other Font tools available for Mac OS X do this too. Maybe Font Book.app does this differently to disable a font. I haven't checked it. Anyway, the fact is that if you assume a Font is not on the System because it's not in /System/Library/Fonts or /Library/Fonts or ~/Library/Fonts, and if this leads you to install it in the Fonts folder in the appropriate domain, then you will be faced with a funny case, where the Font is both enabled and disabled. This may confuse some of the previous mentioned tools and the user (if he/she selected to disable this font in the first place). So if you need to check for the existence of a Font on Mac OS X, don't limit yourself to /Library/Font and don't assume it has not just been moved to a Fonts (Disabled) folder. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Check for file before installing
by Jack Repenning 21 Sep '07

21 Sep '07

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Sep 21, 2007, at 11:46 AM, Peter Bierman wrote: -==- Jack Repenning jackrepenning(a)tigris.org Project Owner SCPlugin http://scplugin.tigris.org "Subversion for the rest of OS X" _______________________________________________ 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.… While I agree that this situation makes life hard for the installer, the Mac OS X Installer handles this as well as can be expected. The OS itself installs many many files that overlap between packages. The consequences are that when multiple packages own the same file, upgrading any one of those packages has the potential to replace or remove that file, leaving the other packages in an inconsistent state. When you know the circumstances of upgrading, you can work around this issue. For example, with Annette's issue, if she replaces a font that should exist anyway, then system upgrades will update or replace that font as necessary. Sure, I didn't mean to dis the Apple installer. But we're still -- inescapably, so far as I can see -- left with those potential inconsistent states. If for example, Annette cares about this font because she wants to use it (seems a safe guess!), and she wants to use this particular font because its metrics make some tricky form layout work better than any other font (wouldn't surprise me, given her return address and implied product), then a change to the font that altered the layout metrix (a thing outside her control, since she doesn't actually own this font) would be a big deal for her: when half her customers start complaining that the form lays out wrong, she'll have a very hard time figuring out why it fails at all ("works for me"), let alone why it only fails for half her customers. This email sent to site_archiver(a)lists.apple.com

1 0