#8306: Parallel inter/intra-spkg builds
----------------------------+-----------------------------------------------
   Reporter:  mpatel        |       Owner:  GeorgSWeber 
       Type:  enhancement   |      Status:  needs_review
   Priority:  major         |   Milestone:  sage-4.3.4  
  Component:  build         |    Keywords:              
     Author:  Mitesh Patel  |    Upstream:  N/A         
   Reviewer:  David Kirkby  |      Merged:              
Work_issues:                |  
----------------------------+-----------------------------------------------

Comment(by mvngu):

 The patch [http://trac.sagemath.org/sage_trac/attachment/ticket/8306
 /trac_8306_scripts-spkg_log_files.patch trac_8306_scripts-
 spkg_log_files.patch] introduces the environment variable
 {{{
 SAGE_LOGS="$SAGE_ROOT/spkg/logs"
 }}}
 for storing build logs of spkg's. A closely related idea, but for MD5
 integrity check files, can be found at #7617. What could be implemented is
 an environment variable like
 {{{
 SAGE_SPKG_MD5="$SAGE_ROOT/spkg/md5"
 }}}
 As of Sage 4.3.3, the SageTeX package is the only standard package that
 has an MD5 file bundled together with the package itself to result in an
 spkg. Whenever the SageTeX spkg is built, its MD5 file is extracted and
 lingers under
 {{{
 SAGE_ROOT/spkg/build
 }}}
 Perhaps a more appropriate place is to deposit MD5 files of spkg's under
 {{{
 SAGE_ROOT/spkg/md5
 }}}
 This would nicely solve ticket #329 after more than 3 years.

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/8306#comment:35>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
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-trac?hl=en.

Reply via email to