• 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: Mountain Lion and Application Support permissions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Mountain Lion and Application Support permissions


  • Subject: Re: Mountain Lion and Application Support permissions
  • From: Howard Moon <email@hidden>
  • Date: Fri, 06 Sep 2013 09:39:24 -0700

Hmmm, might just be a problem with the tester and his machine.  All reports I find are from before I fixed the installer, and things don't look right on this guy's machine to me.  I have tested on multiple OS partitions, and can't see any problem.  I'll come back if I can identify an ACTUAL problem.

Thanks,
	Howard


On Sep 6, 2013, at 9:06 AM, email@hidden wrote:

> No, we're seeing this on a clean test machine, not just in the field.
>
> If the folder is already there with incorrect permissions, then that would mean that the user would already have had problems with whichever software of ours they have that writes to that folder, and they'd have called earlier, not just after installing a new product.
>
> And, obviously, if the folder exists with the correct permissions, then there would be no problem at all.
>
> The problem ONLY exists if the folder is NOT there already.
>
> -Howard
>
> On 06.09.2013 07:44, Conor Schutzman wrote:
>> I suspect the issue is that the folder is already present with
>> differing preferences.
>>
>> Best solution would be to script adjusting permissions in post-install.
>>
>> On Sep 6, 2013, at 7:22 AM, Howard Moon <email@hidden> wrote:
>>
>>> I had previously resolved a problem (on Lion) of our audio plug-ins not being able to create a folder inside /Library/Application Support, by having my installer create the folder (using Packages, and adding the folder to the Payload, with appropriate permissions).  However, this is NOT working in Mountain Lion, apparently.  I set permissions to Read&Write for everything, but when the folder is created on the user's hard drive, those permissions are NOT set, and our plug-ins can't write to our folder.
>>>
>>> How do I get our company's folder to install with the correct permissions inside /Library/Application Support on Mountain Lion?
>>>
>>> Thanks,
>>> 	Howard
>>>
>>>
>>> _______________________________________________
>>> 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


 _______________________________________________
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: 
 >Mountain Lion and Application Support permissions (From: Howard Moon <email@hidden>)
 >Re: Mountain Lion and Application Support permissions (From: Conor Schutzman <email@hidden>)
 >Re: Mountain Lion and Application Support permissions (From: email@hidden)

  • Prev by Date: Re: Mountain Lion and Application Support permissions
  • Next by Date: LZMA support in flat packages?
  • Previous by thread: Re: Mountain Lion and Application Support permissions
  • Next by thread: LZMA support in flat packages?
  • Index(es):
    • Date
    • Thread