while you're at it, you could check for this problem with the other environment variables sage uses; it seems like SAGE_PICKLE_JAR has similar behavior, for example:
http://www.sagemath.org/doc/reference/sage/structure/sage_object.html#sage.structure.sage_object.picklejar On Sep 21, 12:42 pm, John H Palmieri <[email protected]> wrote: > On Sep 21, 1:39 am, "Dr. David Kirkby" <[email protected]> > wrote: > > > > > On 09/21/10 05:48 AM, John H Palmieri wrote: > > > > On Sep 20, 5:39 pm, kcrisman<[email protected]> wrote: > > >> "SAGE_CHECK - if this is set to yes , then during the build process, > > >> run the test suite for each package which has one." > > > > I think this should actually say > > > > if this is set to any nonempty string, then ... > > > > The relevant code is in the sage-spkg script: > > > > if [ "$SAGE_CHECK" != "" -a -f spkg-check ]; then > > > echo "Running the test suite." > > > chmod +x spkg-check > > > ./spkg-check > > > That's a particularly bad bit of code. > > See > > <http://trac.sagemath.org/sage_trac/ticket/9960> > > You'll probably have critiques of the scripts, but anyway... > > -- > John -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
