On Saturday, August 20, 2016 at 7:05:27 PM UTC+2, leif wrote: > > Emmanuel Charpentier wrote: > > While trying my hand <https://trac.sagemath.org/ticket/20523> at > porting > > R 3.3.1 to Sage (needs_review, by the way), I found this in the > > current R Installation and Administration manual > > <https://cran.r-project.org/doc/manuals/r-release/R-admin.html#Cygwin> > : > > > >> C.8 Cygwin > >> > >> The 32-bit version has never worked well enough to pass R’s make > > check, and residual support from > >> earlier experiments was removed in R 3.3.0. > I wonder what the residual support was...
> >> > >> The 64-bit version is completely unsupported. > I concur, but that was for bad reasons, or let's be fair, one could say the lack of manpower maybe? > > > > Maybe we should consider to have an interface to system's R rather than > > our own version (and therefore make it an optional package) > > +1 for making it an optional package. (It's by the way not what I'd > call a small package, and also takes some time to build.) > > > The Cygwin developers certainly have to say something regarding support > as a standard package. (I don't think it would make sense to upgrade > Sage's R version *and* keep it a standard package if it does no longer > build on Cygwin. We could presumably still keep Rpy and let it use the > system version of R, also on Windoze, if present and suited.) g > > It's not my impression that The R folk really supported any version of Cygwin recently. I even got bashed out when proposing a simple and non-intrusive patch for Cygwin64. The point is that it seems hopeless to push patches upstream which is a very bad point. gwthat hard at all, one just needs a setup and a very little bit of good will: ftp://cygwin.com/pub/cygwin/x86_64/release/R/ So yes R still builds on Cygwin32/64. The other solution on Windows is to try to use the R provided binaries, but that surely means no real library interface. Concerning the status of Sage on Cygwin, it's always the same deal: we need buildbots, I thought it was one of the ODK goals. I don't have the time anymore to play with my VM's and torture Cygwin and Sage. I could still do it next week at SD75. > > -leif > > > > It would be more difficult (but not impossible) to offer the same kind > > of access to an external R as to a tightly-knit R. I'm thinking > > graphics, notebook(s) integration, etc... > > > > OTOH, the existence of a good R interface (Rpy2) could make things > > easier. The largest problem that one can forecast is, of course, > > backwards compatibility in existing programs. > Would this be possible on Cygwin, mixing a Cygwin compiled rpy2 and a Windows compiled R? -- 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 post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
