• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Permissions Broken in PackageMaker 3
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Permissions Broken in PackageMaker 3


  • Subject: Re: Permissions Broken in PackageMaker 3
  • From: Andrew Merenbach <email@hidden>
  • Date: Sun, 10 May 2009 17:53:00 -0700

Greetings, Eli,

Well, I'll be! Working with PM from the command line appears to open up a whole new world of options, both productivity-oriented and convenience-oriented. I very much appreciate your pointing out that parameter; it appears to solve the issue that I am experiencing. I suppose I should file a bug.

Thank you very much for your time, Eli!

Cheers,
	Andrew

On May 10, 2009, at 3:52 PM, Eli Bach wrote:


On May 10, 2009, at 3:41 PM, Andrew Merenbach wrote:

Hi, all,

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?

Have you tried building from the command line using:

/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.


Eli

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Installer-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Installer-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Permissions Broken in PackageMaker 3 (From: Andrew Merenbach <email@hidden>)
 >Re: Permissions Broken in PackageMaker 3 (From: Eli Bach <email@hidden>)

  • Prev by Date: Re: Permissions Broken in PackageMaker 3
  • Next by Date: Just updated vanilla.catalog, and an update
  • Previous by thread: Re: Permissions Broken in PackageMaker 3
  • Next by thread: Just updated vanilla.catalog, and an update
  • Index(es):
    • Date
    • Thread