On Wednesday, December 23, 2020 at 5:55:38 AM UTC-8 u...@ll.mit.edu wrote:
>
>>> the MacPorts-specific part would be to create a list of packages to
>> install, and put it into build/pkgs/*/distros/macports
>> and a similar global location.
>>
>
> I'm not sure I understand what that means.
>
On Wed, 23 Dec 2020, 14:11 Mouse Mousevich, wrote:
> I looked into build/pgks/* (1.5 GB) and it appears that Sage is trying to
> be a package manager, in addition to what people probably want it for.
>
> I guess at version 9.2 it's rather late to ask why it isn't good enough to
> just list in
The short answer is that Sage is designed for (among others) research
mathematicians, who may not have the interest or inclination to learn how
to install lots of system packages. So from the beginning it included as
many components as possible. Years ago the presence of MacPorts and other
Le mer. 23 déc. 2020 à 14:55, Mouse Mousevich:
>>
>> the MacPorts-specific part would be to create a list of packages to install,
>> and put it into build/pkgs/*/distros/macports
>> and a similar global location.
>
> I'm not sure I understand what that means. If a package is already installed
>
I looked into build/pgks/* (1.5 GB) and it appears that Sage is trying to
be a package manager, in addition to what people probably want it for.
I guess at version 9.2 it's rather late to ask why it isn't good enough to
just list in the README a set of packages that Sage requires to run, and
>
>
>> We don't have a single MacPort user among a handful of SageMath
>>> developers. Please feel free to provide patches. (Yes, it means supporting
>>> yet another nonstandard location, more or less, I suppose)
>>>
>>
>> The fun part is that to support Macports, you need to look in
>>
On Wed, 23 Dec 2020, 11:01 Mouse Mousevich, wrote:
> Please see below.
>
> TL;DR.
>> patches are most welcome :-)
>>
>
> Understood.
>
>
>> Sage-9.2 has several idiosyncrasies that for me are hard to explain. One
>>> - it deliberately refuses to work with Macports-installed packages, even
>>>
Please see below.
TL;DR.
> patches are most welcome :-)
>
Understood.
> Sage-9.2 has several idiosyncrasies that for me are hard to explain. One -
>> it deliberately refuses to work with Macports-installed packages, even
>> though their main difference from similar ones installed via Brew
TL;DR.
patches are most welcome :-)
Details below.
On Wed, 23 Dec 2020, 02:40 Mouse Mousevich, wrote:
> A lot of people have a lot of problems with Sage-9.2 on MacOS, installing
> pre-compiled or building from the source.
>
> Sage-9.2 has several idiosyncrasies that for me are hard to explain.
After changing the env compiler flags to stop pplpy-0.8.4 from confusing
itself, and re-starting the build, it fails in scipy-1.5.2:
[scipy-1.5.2] clang -bundle -undefined dynamic_lookup
-L/Applications/SageMath/local/lib
-Wl,-rpath,/Applications/SageMath/local/lib -L.
A lot of people have a lot of problems with Sage-9.2 on MacOS, installing
pre-compiled or building from the source.
Sage-9.2 has several idiosyncrasies that for me are hard to explain. One -
it deliberately refuses to work with Macports-installed packages, even
though their main difference
On Fri, Dec 4, 2020 at 3:26 PM Mathieu Dutour wrote:
>
> On Thursday, 3 December 2020 at 19:13:28 UTC+1 dim...@gmail.com wrote:
>>
>> On Thu, Dec 3, 2020 at 5:39 PM Mathieu Dutour wrote:
>>>
>>> Thank you for providing this. Keep that in mind for future.
>>>
>>> As it turns out, the solution to
On Thursday, 3 December 2020 at 19:13:28 UTC+1 dim...@gmail.com wrote:
> On Thu, Dec 3, 2020 at 5:39 PM Mathieu Dutour
> 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"
>>
>
>
Hi Dima.
As you said, "brew install sage" does nothing more than downloading a
sage-*.app.dmg and copying it to /Applications, at least on an older OS.
Details follow for macOS High Sierra (10.13.6). Yes, I know it is an
"obsolete" version.
$ brew info sage
sage: 9.1,10.11.6
On Thu, Dec 3, 2020 at 5:39 PM Mathieu Dutour 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
A ticket to track providing an app for macOS again:
- Provide macOS app again
https://trac.sagemath.org/ticket/31000
--
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
On Thu, Dec 3, 2020 at 5:39 PM Mathieu Dutour
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"
>
on macOS 10.15.7 this appears to install the version 9.2 of x86_64.app.dmg
by
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"
I think this should be mentioned on the "Sage Installation Guide"
as this is a very convenient and standard procedure on Macintosh.
Your mention of
Have you tried this?
sudo xattr -r -d com.apple.quarantine
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
19 matches
Mail list logo
