kcrisman wrote:
> 
>     I think maybe even a better distinction than "sage-the-distro" is to
>     call it "SageMath, the Application".  As far as users of the
>     application are concerned I agree the it should have the goal of being
>     a general purpose stack of mathematics software.  For short I'll call
>     the application/distribution SageMath in (camel-case) and the Python
>     package "sage" since that's what the actual package is called.
> 
>     But treating that larger software stack, and the `sage` Python package
>     as one in the same makes development on the latter more difficult, and
>     probably ultimately the former as well.  For example--continuing with
>     R as the test particle--say I'm a SageMath user who makes heavy use of
>     R for my statistics, and like being able to use R with sage.  What
>     happens when a critical bug is fixed in R, and a new patch release
>     comes out (something Sage, by the way, doesn't even have but should).
>     How do I get that patch release?  Well I have to wait for a new
>     version of sage (the package, and everything else that comes with it).
>     That might include a bunch of other new dependencies that I didn't
>     really think I needed.  Possibly even API breakage elsewhere (though
>     fortunately sage itself is normally pretty good about that).
> 
> 
> Yes, I agree that is a very significant issue and of course has been for
> some time (with respect to many, many packages, I couldn't even list
> them all for you).

... which was less of a problem with our "legacy" spkgs, as you in many
cases could simply install an older or a more recent version when
available /somewhere/, or even easily create your own, just replacing
the upstream version in the src/ folder.

More or less just out of curiosity, did we ever upgrade R because of
bugs in R (besides build/installation issues) R-thru-Sage users
complained about?

Closer on topic, is there urgent need to upgrade our current version of
R?  (The 'configure' bug I reported upstream May last year is by the way
still in 3.3.1, although the patch I submitted is pretty trivial.)


-leif


-- 
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.

Reply via email to