December 2005 - Installer-dev

Re: Prevent user from accessing Archive.pax.gz?
by Stéphane Sudre 30 Dec '05

30 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On vendredi, décembre 30, 2005, at 07:19 PM, Patrick Litterst 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'm trying to create an updater that will install an application only if a previous version of the application exists on the user's machine. However, it seems that if a previous version does not exist (and so the install fails as a result), the user can still go into the contents of the .pkg and unarchive the Archive.pax.gz, and get the application even if they do not have a previous version of the application on their computer. Is there a way to prevent this? They could also used Pacifist to extract the package wherever they want to. The only solution AFAIK would be not to have the real application in the archive and do something like: 1) In the preflight script, compute a md5 checksum of the previous installed version. 2) Install an encrypted version of the application (encryption would have been made using the md5 key) 3) In the postflight script, decrypt the encrypted binary using the md5 checksum. This email sent to site_archiver(a)lists.apple.com

1 0

Prevent user from accessing Archive.pax.gz?
by Patrick Litterst 30 Dec '05

30 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com -Patrick _______________________________________________ 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 trying to create an updater that will install an application only if a previous version of the application exists on the user's machine. However, it seems that if a previous version does not exist (and so the install fails as a result), the user can still go into the contents of the .pkg and unarchive the Archive.pax.gz, and get the application even if they do not have a previous version of the application on their computer. Is there a way to prevent this? This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker broke when I installed Xcode 2.2?
by Karl Schramm 29 Dec '05

29 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On Dec 29, 2005, at 1:10 PM, Steve Johnson wrote: Greetings, Can anyone offer any info on what's going on here? TIA. Steve _______________________________________________ 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.… Have you tried using the verbose flag (-v) when building? That should give you more information on the error. e.g. PackageMaker -build -proj project-path -p destination-path [-v] I just installed Xcode 2.2, and now my installer builds (via make and PackageMaker) fail. I don't know of anything else that has changed in my environment, so I'm figuring that the Xcode 2.2. install caused this problem. PackageMaker is providing no diagnostic information...it writes nothing to either stdout or stderr. It simply returns a result of 1 rather than 0, causing the make to fail, and fails to write a package file. I've played with it some, and noticed one weird thing. If I add the '-v' flag to my builds, then PackageMaker doesn't return an error code (it seems to succeed), but the package file still isn't written. The logging output doesn't specify that anything has gone wrong. _______________________________________________ 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/karlfschramm% 40mac.com This email sent to karlfschramm(a)mac.com This email sent to site_archiver(a)lists.apple.com

1 0

Re: PackageMaker broke when I installed Xcode 2.2?
by Steve Johnson 29 Dec '05

29 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcYMx0kJh64VPHi6EdqdxQARJDiIkA== Thread-topic: PackageMaker broke when I installed Xcode 2.2? User-agent: Microsoft-Entourage/11.2.1.051004 SUCCESS!! I just reverted to the version of PackageMaker that came with Xcode 2.1 by pulling it out of the 2.1 DeveloperTools.pkg file, and now my installer builds work again. So there's definitely something fishy with the Xcode 2.2 PackageMaker. NOTE: Beware of a point of possible confusion. The PackageMaker that ships with Xcode 2.1 is version 2.0.1. The version that ships with Xcode 2.2 is 2.1. S _______________________________________________ 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

PackageMaker broke when I installed Xcode 2.2?
by Steve Johnson 29 Dec '05

29 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Thread-index: AcYMvFU7k7ec/HivEdqdxQARJDiIkA== Thread-topic: PackageMaker broke when I installed Xcode 2.2? User-agent: Microsoft-Entourage/11.2.1.051004 Greetings, I just installed Xcode 2.2, and now my installer builds (via make and PackageMaker) fail. I don't know of anything else that has changed in my environment, so I'm figuring that the Xcode 2.2. install caused this problem. PackageMaker is providing no diagnostic information...it writes nothing to either stdout or stderr. It simply returns a result of 1 rather than 0, causing the make to fail, and fails to write a package file. I've played with it some, and noticed one weird thing. If I add the '-v' flag to my builds, then PackageMaker doesn't return an error code (it seems to succeed), but the package file still isn't written. The logging output doesn't specify that anything has gone wrong. Can anyone offer any info on what's going on here? TIA. Steve _______________________________________________ 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

PackageMaker command line feature request
by Karl Schramm 29 Dec '05

29 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com Hi all, Thanks! Karl Schramm P.S. I'm using 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 trying to automate the build of a rather complicated installer I built using PackageMaker and its command line interface. The big problem I keep running into is that PackageMaker's command line interface does not follow relative paths when building a package from a PackageMaker GUI project. Can we please have this feature in the next rev of PackageMaker? This email sent to site_archiver(a)lists.apple.com

1 0

Re: Install into User's Home directory
by Abraham Nelson 28 Dec '05

28 Dec '05

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=Message-ID:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Oam3j7t5fjMThJLny8F2t2GepZ/eT0BXix9wUeeeCG/IKPZcYrQ0wS1zC6aU73o1iVsjfF4p+EyJmEHi/8jtwkINEfhDJng/FoySvs/pnRx5qtNGlCRazsKWhc93fL6njLLoklh4dcvoJn4BxK39AQwY1wosEbu6i30QibQV7EM= ; --- Stéphane Sudre <ssudre2(a)wanadoo.fr> wrote: > > Juts found a solution to install files/folders in > $HOME with a .pkg if: > I'm curious: would doing it this way allow Installer to compare the version information included with the pagacked software (the version.plist info discussed in the Software Distribution docs)? __________________________________ Yahoo! for Good - Make a difference this year. http://brand.yahoo.com/cybergivingweek2005/ _______________________________________________ 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: Install into User's Home directory
by Stéphane Sudre 27 Dec '05

27 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On mardi, décembre 27, 2005, at 07:19 PM, Patrick Litterst wrote: Almost. From the list archive: Juts found a solution to install files/folders in $HOME with a .pkg if: - you only install files/folder in $HOME and you don't want: I thought it might be interesting to share this solution. --------8<-----------8<----------- Launch PackageMaker or any other tool that can create .pkg: 1) Create a package with the following flags set: o Root Volume Only o Follow Flags o Overwrite directory permissions (Off or On) (I tried it with On). 2) Create your file hierarchy on disk or in the other tool like this: Then create the Library, Pictures, Movies, etc... folder as you wish. 3) Create the following pretty complex preflight script: #!/bin/sh ln -s $HOME /private/tmp/A_SUPER_UNIQUE_NAME_YOU_SELECTED exit 0 5) Run (and test?) #!/bin/sh mv /InstalledFiles ${HOME}/directory exit 0 It may depend on what $HOME is pointing to. _______________________________________________ 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 need to install a folder of files into the user's Home directory. There doesn't seem to be a way to do this without writing a script. Am I correct about this? - any user interaction (as in: the user has to select his/her home folder) The folder /private/tmp/A_SUPER_UNIQUE_NAME_YOU_SELECTED/ will be the default location for the installation I set the file owner and group to root:admin for the files/folder within A_SUPER_UNIQUE_NAME_YOU_SELECTED. The final files are current_user_id:20 after installation on my 10.2.8 machine. 4) Build your package with either Command + K or Command +B depending on the tool. I am currently attempting to achieve this with a script. I have made an installer that installs the folder of files on the user's hard drive and then uses the following simple postflight script to move the files to the proper directory inside user's Home directory. The > script: When I build and run the installer, the installer says it cannot run this script. However, if I run the script from the Terminal, the script executes properly. Is there something wrong with the Script? Should I install into the user's Home directory via some other way? This email sent to site_archiver(a)lists.apple.com

1 0

Install into User's Home directory
by Patrick Litterst 27 Dec '05

27 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com #!/bin/sh mv /InstalledFiles ${HOME}/directory exit 0 _______________________________________________ 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 need to install a folder of files into the user's Home directory. There doesn't seem to be a way to do this without writing a script. Am I correct about this? I am currently attempting to achieve this with a script. I have made an installer that installs the folder of files on the user's hard drive and then uses the following simple postflight script to move the files to the proper directory inside user's Home directory. The script: When I build and run the installer, the installer says it cannot run this script. However, if I run the script from the Terminal, the script executes properly. Is there something wrong with the Script? Should I install into the user's Home directory via some other way? This email sent to site_archiver(a)lists.apple.com

1 0

Re: how to avoid overwriting files during installation
by Stéphane Sudre 22 Dec '05

22 Dec '05

site_archiver(a)lists.apple.com Delivered-To: installer-dev(a)lists.apple.com On jeudi, décembre 22, 2005, at 08:55 PM, Patrick Litterst wrote: A quick look at the archive show a post from C. Ryan which may help: I assume you could have a hint that says: <array> <string>/*</string> <string>dontobsolete</string> </array> _______________________________________________ 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've created a .mpkg installer using PackageMaker that contains two packages: one package contains an application that gets installed in the Applications folder, and the other package contains files that get installed elsewhere on the computer. If the user reinstalls the application using the .mpkg installer, the files (which the user may have modified prior to reinstallation) will be overridden. How can I prevent these files from getting overridden during reinstallation of the software? [...] Yes, although I could find no public documentation. Do a search for "Hints.plist" in your receipt directory (find . -name "Hints.plist" -print). You will see a number of Apple packages which use the hints mechanism to prevent obsoletion in some cases. Basically saying don't obsolete anything (although you will have to try that out and see if it works). The problem is, that in the future when you do want upgrade behavior (to remove old files) it will see your "update package" which only contains a few files and you will have a hard time removing all the pieces of the original install on upgrade (if they are truely not part of your product anymore) without writing a script to do it by hand, since the last receipt for a given package is all that sticks around. [...] This email sent to site_archiver(a)lists.apple.com

1 0