On Friday, March 18, 2016 at 3:06:04 PM UTC, William wrote:
>
> On Fri, Mar 18, 2016 at 7:59 AM, Volker Braun <vbrau...@gmail.com 
> <javascript:>> wrote: 
> > I've had people at workshops trying to compile Sage (never mind using 
> > binaries) and they were SOL because their system bash was linked against 
> the 
> > wrong version of some library. If you can't compile it you surely can't 
> use 
> > it 6 times. 
>
> David Roe had no trouble compiling Sage.  It's wasteful to have to do 
> it many times repeatedly. 
>

yet, David does not want to spend a bit of his time helping general Sage 
development.
(we talk about perhaps 10 lines of code to change timestamps
in the right place, where the most time would go to navigating to the right 
place...)

This is fine. But then he has 0 right to request enhancements from 
volunteers, and you should not
have any pity on him for him having to read some new docs and spend extra 
CPU cycles because
of a very, very rare in practice case of use for Sage.
(actually, as Volker points out, a case that might not work in practice, as 
the server he's using is not powerful
enough for 6 teams of people hacking on Sage at the same time...)


> > Also, your use case is a bit weird; Parallel installations on the same 
> > server? 
>
> It's David's use case for Sage Days 71.  It seems to me like a 
> reasonable use case for development. 
>
> >  Still, not a problem with rpaths. 
>
> Cool, in theory. 
>
> > 
> > Finally, if you don't have enough memory to build the docs once then 
> you'll 
> > have a bad time running the tests when developing (you do run the tests, 
> > right?). 
>
> Sage is getting more and more unwieldy.   I fear for its survival.  

 
if the best Sage devs like you don't want to make their hands dirty and 
work on the core Sage, including
build system, packages, etc, it might start to collapse indeed.
 

>
>  - William 
>

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