On May 6, 9:06 pm, "John Cremona" <[EMAIL PROTECTED]> wrote:
> Michael,
John,
> I hope you realised that I was only criticising my own lamentable lack
> of understanding and not your explanations. I think that the number
> of drinks I'll be buying you next time we meet must be into double
> figures by now.
:)
> For most of us, even though we build all or most of the alphas and rcs
> and releases, we pay no attention whatsoever to what happens between
> typing "make" and coming back a couple of hours later to see the
> wonderful words "Sage build successful" or whatever. Well, that is
> true for me anyway. So I'm not so aware of the build doing lots of
> things one after the other, one of which is "building the sage
> library" since as far as I am concerned the entire 2 hours is spent
> "building the sage library". I hope that wasn't too much of a shock
> to hear.... [I hope I am unshockable -- I spent several hours over the
> last few days helping my 87-year-old mother switch her email from
> hotmail to gmail, all over the telephone, so I know the meaning of
> patience!]
Yes. I had some email exchange with some people yesterday [a survey
like thing] and one of them mentioned that the user documentation
*must* become better. I has been clear to Gary, many other people in
IRC and me what pbuild does and that the Sage library is different
than "the whole of Sage". But that is a problem since the lingo of
#sage-devel needs to be understandable by other developers not hanging
out there. I certainly don't blame you for asking since I am convinced
that many people just stay quiet and that is bad since anybody with a
question should just ask. It is partially *my* fault that it is
unclear to many people what pbuild does. And we need to figure out how
to improve the documentation and then actually make it better.
Somebody with time on their hands just ought to read the manuals and
start complaining and opening ticket about out of date/wrong info in
the manual. Sage needs to be polished and that includes the
documentation. Who knows how many people walked away from Sage because
they hit some little snafu and couldn't find ot found *wrong*
documentation in the first place.
> I didn't really mean that I had given up on any testing, just that the
> version of Sage I am currently using is 3.0.1 without PBUILD since I
> only like using a version which has passed --testall.
Sure. I hope you will try out pbuild in 3.0.2.alpha0. I thought of
slapping Gary on the back of the head at Dev1 for each bug I find in
pbuild until then ;)
> Back to work fixing #3111!
That one actually exposed a bug in pari on OSX IMHO, too, i.e. when
Sage or pari fails to allocate any more memory it just fails. I think
the likely culprit is pari in this instance, but we will see.
> best,
>
> John
Cheers,
Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
