site_archiver@lists.apple.com Delivered-To: installer-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:subject :mime-version:date:references:x-mailer; bh=bIK8KKQ4jP4H/d7jscE1mPXBaW/x2LOgJE6WpwNBvOg=; b=wRqxFkQJcHXChAdmnk1ijuzplqGppzHDKbc4gUbCvA+DeIE34523jBDX/CgtdADDnA QAGiJczsGQQUEQYzN6rlnoz7wgg1ev0yKSA2gzIZ3IbGe0G7LJ/rnxUuDVmGZKOf3rut Ka9lTG/T5uEvhyw+IlhP4XHkRZKbbjbubls2o= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:subject:mime-version:date:references :x-mailer; b=np/JQOGKSCHFVCxsTP1mJ9qB60+xx0KygWOkmOXxOR+MK4i3dLlNoIzxsOrgN2NQb+ 5H7c0VI3XpRSFxOd+BTZYQk+vucjtTGWPinICbRM1ynIBWUt3o8MPNrMHTU3yCi2vjEp 4KTRB7JYmQDZEd7EuM6pxi12O6pDZqO01WzaM= On May 10, 2009, at 3:41 PM, Andrew Merenbach wrote: Hi, all, Have you tried building from the command line using: Eli _______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (Installer-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/installer-dev/site_archiver%40lists.a... Has anyone had any luck using custom--or even just non-root-- permissions in PackageMaker 3 (I'm using 3.0.3)? I'm installing part of my installation to /Users/Shared, so I don't want "root:wheel" permissions, lest a user be unable to delete what gets installed. Every time that I build my installer--which can be either a 10.4-compatible or 10.5-compatible installer, any default or custom permissions get written over. I posted to this mailing list awhile back about this, but I believe that I may have been a little less clear and a little less general than I'm being now. Is this a known bug in PM3? Is there a workaround? It seems to me that there's absolutely no way to install to /Users/Shared using PackageMaker 3 unless I want to set permissions manually with a script afterwards, which seems somewhat backwards when PackageMaker should be setting permissions for me. Any ideas, anyone? /Developer/Applications/Utilities/PackageMaker.app/Contents/MacOS/ PackageMaker --no-recommend While I haven't built an installer that puts things in /Users/Shared/, this has fixed the problem I had with PackageMaker using incorrect permissions for files in /Library/LaunchAgents. This email sent to site_archiver@lists.apple.com