On Mon, 16 Dec 2019, 15:10 Emmanuel Charpentier, < emanuel.charpent...@gmail.com> wrote:
> > > Le lundi 16 décembre 2019 15:28:16 UTC+1, Dima Pasechnik a écrit : >> >> On Mon, Dec 16, 2019 at 11:06 AM E. Madison Bray <erik...@gmail.com> >> wrote: >> > >> > On Fri, Dec 13, 2019 at 5:16 PM Emmanuel Charpentier >> > <emanuel.c...@gmail.com> wrote: >> > > >> > > Le vendredi 13 décembre 2019 14:12:01 UTC+1, E. Madison Bray a écrit >> : >> > >> >> > >> On Fri, Dec 13, 2019 at 2:05 PM Emmanuel Charpentier >> > >> <emanuel.c...@gmail.com> wrote: >> > >> > >> > >> > While we are already late in the Sage 9 release cycle, Trac#28877, >> which is a (routine) upgrade of R to the current release, may be of >> benefit. >> > >> > For non-R-users : using the latest released R is almost a sine qua >> non to get help from the R-help mailing list... >> > >> >> > >> I will have a look at it. FWIW while I still think it's good and >> > >> right to distribute R with Sage, I think serious users of R are not >> > >> installing Sage to get R so I don't think we should be in the >> business >> > >> of worrying about what is sine qua non in the R community to get >> help >> > >> from the rest of their community. >> > > >> > > >> > > I initially thought that getting people to "just install Sage" to get >> a consistent and interoperable set of modeling-related software was a clean >> way to get rid of the complexity of available software set maintainance. >> > > >> > > But the current state of Sage distribution makes this a bit of a >> dream. Currently, the best way to install Sage is to compile it from source >> : definitely not an "end-user" task... It's even worse on Windows, where >> Sage isn't even a "first class citizen", notwithstanding the Herculean >> efforts of one E. Madison Bray (more on this in a little while on This >> issue). >> > >> > I don't think that's true. On the vast majority of systems I've >> > tried, the best way to install Sage is to install the pre-compiled >> > binaries. I've almost never HAD to compile Sage from source just to >> > have a working Sage on some system. It's also been packaged for most >> > major Linux distributions, including the latest Debian (of course in >> > that case you're not always going to get the most recent version, >> > depending on the distro). I don't know what you mean by "first class >> > citizen" w.r.t. Windows. The only extent to which it isn't is that >> > there still is not a stable buildbot for Windows, despite my efforts, >> > as it tends to need more maintenance than a Linux server would... very >> > annoying. Other than that I don't know what you mean. So I don't >> > think you should be giving anyone the wrong impressions here. >> > >> > > Do you think that it is possible to keep the R *interface* standard >> while R being *optional*, in a way similar to Mathematica, Magma and Maple >> ? It might require a bit more work, R being updated at least twice >> annually, while Mathematica's release are at multi-years intervals... >> > >> > I think the only reason it isn't currently is that R is free and >> > open-source, so can be distributed as part of Sage anyways, whereas >> > the other M's aren't. I think R is popular enough that there is value >> > in having an interface to it, but I tend to agree that distributing R >> > with Sage by default is not so useful; it should instead be easier to >> > configure Sage to interface to an existing system R if there is one. >> >> and it is now fixed by https://trac.sagemath.org/ticket/28884 >> >> Please have a look. It tests OK on various Debian/Ubuntu, on >> (obsolete) Fedora 26 I had to supply openplas.pc, as it does >> not install it, > > > According to this bug report > <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946698>, this should > be fixed in Debian Real Soon Now(TM), but it seems that this fix has > triggered another bug > <https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946828>. Mektoub... > > >> and even on MacOS 10.13 with R and openblas from >> Homebrew it tests just fine. >> It should be possible to use the "native" R installation, if they >> supplied libR.pc (which they don't, but >> it should be easy to produce one). >> > > Upstream creates libR.pc ; it is also present in Debian packages. Do you > mean it is a Mac OS-specific problem ? > > it is specific to MacOS "binary* distributed by R project. It includes libR and headers, but no libR.pc if providing the latter works, we should report it to them. > -- > You received this message because you are subscribed to the Google Groups > "sage-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-devel+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/sage-devel/64b4d468-77d4-4898-b768-69195cc5083d%40googlegroups.com > <https://groups.google.com/d/msgid/sage-devel/64b4d468-77d4-4898-b768-69195cc5083d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-devel/CAAWYfq3M8e50NvqSVGFMon6mp2i3OyM%3D250p35xTV3bnopdOhg%40mail.gmail.com.
