On 06/26/10 08:33 AM, William Stein wrote:
On Sat, Jun 26, 2010 at 12:04 AM, Dr. David Kirkby
<david.kir...@onetel.net> wrote:
Currently if a package fails to build in Sage, one gets a message like:
============================
sage: An error occurred while installing pynac-0.2.0.p3
Please email sage-devel http://groups.google.com/group/sage-devel
explaining the problem and send the relevant part of
of /export/home/drkirkby/sage-4.5.alpha0/install.log. Describe your
computer, operating system, etc.
==========================
It would be quite easy to make that a bit more informatative, and dump at
least some basic information, like the output of 'uname -a' and /etc/release
(Solaris), /etc/issue (Linux).
That way, if someone posts their failed build, we already have some
information.
Then we change the above wording to
It might be better to store all that in a *file*, e.g.,
SAGE_ROOT/tmp/buildinfo.txt and suggest in the short message that the
person reporting the issue also include that file.
William
Why do you think it might be better to put it in a file and suggest they include
the file?
* It creates more work for the person (they need to look for the file and
attach it).
* It's more error prone, if they have multiple builds in different
directories. They could then attach the wrong file.
I don't have anything against putting the information in a file, but I think
printing it out directly has some advantages. So do both - disk space is pretty
cheap!
Dave
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
