On Jan 17, 1:15 pm, John H Palmieri <jhpalmier...@gmail.com> wrote: > On Tuesday, January 17, 2012 10:06:18 AM UTC-8, kcrisman wrote: > > > Here is a probably dumb question. > > > Currently (as far as I am aware), most spkgs should pass with > > SAGE_CHECK set, though it does depend on the platform and specific > > machine. Python is somewhat notorious for not doing so. I'd like to > > be able to start using SAGE_CHECK while building, but currently this > > is annoying because it means I have to wait until it fails with > > Python, then unset it for Python, reset it on the next spkg... not > > very automated. > > Slightly more automated, but still some work, is to create a new Python > spkg file: just deleting the spkg-check file should be good enough. So > unpack python-....spkg, delete spkg-check, run sage --pkg python-... (you > don't even need to commit the changes), and then do 'make'.
Hmm, that could be useful, even if not as automated, since it would mean only typing "make" once, which is the real goal. It wouldn't lead to an error if I only delete that file (i.e. spkg-install doesn't have lines about spkg-check in it that would stop the build)? - kcrisman -- 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
