On Apr 24, 2021, at 10:49, Nathaniel W Griswold wrote:
> I guess my intent in asking this was to ask: does macports ever ad-hoc
> codesign packages? Is there ever a case that is necessary? Googling didn’t
> yield much discussion about it.
MacPorts does not contain any code to codesign anything
I guess my intent in asking this was to ask: does macports ever ad-hoc codesign
packages? Is there ever a case that is necessary? Googling didn’t yield much
discussion about it.
The reason i asked the question is because i couldn’t get the specific port i
was using to work as it did before i
I am running the latest Big Sur update. I was on Catalina last week and it had
the same behavior.
> On Apr 23, 2021, at 9:12 PM, Andrew Janke wrote:
>
> What version of macOS are you running? The SIP and sandboxing stuff
> changes from version to version...
>
>> On 4/23/21 8:12 PM, Nathaniel
Do apps like emacs need to be ad-hoc codesigned to access privileged folders
like Documents?
The first time i installed the emacs-app-devel subport, it prompted me the
first time i used it for accessibility control and access to folders like
~/Documents. Everything worked fine.
But then i
