On Thu, Dec 3, 2020 at 5:39 PM Mathieu Dutour <mathieu.dut...@gmail.com> wrote:
>
> Thank you for providing this. Keep that in mind for future.
>
> As it turns out, the solution to installing was incredibly simple:
> "brew install sage"
>

dima@oucl13243 sage % brew install sage
==> Searching for similarly named formulae...
This similarly named formula was found:
imessage-ruby
To install it, run:
  brew install imessage-ruby
Error: No available formula or cask with the name "sage".
==> Searching for a previously deleted formula (in the last month)...
Error: No previously deleted formula found.
==> Searching taps on GitHub...
Error: No formulae found in taps.

dima@oucl13243 sage % brew install --cask sage
Error: Cask 'sage' is unavailable: No Cask with this name exists.


> I think this should be mentioned on the "Sage Installation Guide"
> as this is a very convenient and standard procedure on Macintosh.
>
doesn't even install for me, see above.


> Your mention of "sudo xattr ..." should be mentioned as well
> I think.
>
>   Mathieu
> On Thursday, 3 December 2020 at 18:10:12 UTC+1 john_perry_usm wrote:
>>
>> Have you tried this?
>>
>>    sudo xattr -r -d com.apple.quarantine <path/to/Sage>
>>
>> It removes the "quarantine" signal on files. I used it to get Sage running 
>> on Catalina. I've had to use this with some other things, too. I learned of 
>> it through one of the StackOverflow sites, and it may also be in Sage's 
>> documentation somewhere.
>>
>> john perry
>>
>> On Wednesday, December 2, 2020 at 12:54:29 PM UTC-6 Mathieu Dutour wrote:
>>>
>>> I would like to install SAGE on a macOS MacBook Pro16 computer.
>>>
>>> The problem I have is that Sage is killed when trying to install it
>>> by the system. The reasons is laudable: Do not run untrusted binaries
>>> on a macintosh.
>>>
>>> But in that case, it makes installation kind of impossible. The reason
>>> is that the first binary to be allowed on "Security & Privacy" is Python3.8
>>> If the story stopped here, then that would be perfectly fine. However, after
>>> I allow the Python3.8 I have further libraries to allow and it does not 
>>> appear
>>> to converge as I keep allowing the same libraries over and over.
>>>
>>> I tried two ways of installing:
>>> 1) Downloading the .tar.bz2 and installing it in my $HOME/opt directory
>>> just as I do on Linux.
>>> 2) Downloading the .dmg archive and installing sage in /Application 
>>> directory.
>>> I would have expected that it worked since /Application is a root directory
>>> and not user one. Also the .dmg is a package format so should allow
>>> simple authorization scheme.
>>>
>>> I followed the "Sage Installation Guide. Release 9.2" and unfortunately
>>> that problem does not appear to be addressed there.
>>>
>>>   Mathieu
>
> --
> You received this message because you are subscribed to the Google Groups 
> "sage-support" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to sage-support+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/sage-support/e6cb3fd4-f338-4fd6-bd48-f4d6ad7c7345n%40googlegroups.com.

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/sage-support/CAAWYfq2Vc%2BR-Gy1QR4c%3D0VuqF_xeoppnV-WUuWP4LdVjaCNi7w%40mail.gmail.com.

Reply via email to