#4949: Optionally build spkgs in $SAGE_BUILD_TMPDIR
-------------------------------------------------------------+--------------
   Reporter:  mabshoff                                       |          Owner:  
mabshoff     
       Type:  enhancement                                    |         Status:  
needs_review 
   Priority:  minor                                          |      Milestone:  
sage-5.0     
  Component:  build                                          |       Keywords:  
sd32         
Work_issues:                                                 |       Upstream:  
N/A          
   Reviewer:  Mariah Lenox, Leif Leonhardy, Maarten Derickx  |         Author:  
John Palmieri
     Merged:                                                 |   Dependencies:  
             
-------------------------------------------------------------+--------------
Changes (by jhpalmieri):

  * status:  needs_work => needs_review


Old description:

> `$HOME` can be slow in case it is NFS-mounted for example. So using local
> scratch space or even better a RAM disk should speed up the build by a
> nice factor. To do so, use `$SAGE_BUILD_TMPDIR/build/` in case it exists
> instead of `$SAGE_ROOT/spkg/build/`.
>
> ----
>
> Apply [attachment:trac_4949-root.patch] to the Sage '''root
> repository'''.
>
> Apply [attachment:trac_4949-installation.patch] to the '''Sage
> library'''.

New description:

 `$HOME` can be slow in case it is NFS-mounted for example. So using local
 scratch space or even better a RAM disk should speed up the build by a
 nice factor. To do so, use `$SAGE_BUILD_TMPDIR/build/` in case it exists
 instead of `$SAGE_ROOT/spkg/build/`.

 ----

 Apply [attachment:trac_4949-root.v2.patch] to the Sage '''root
 repository'''.

 Apply [attachment:trac_4949-installation.patch] to the '''Sage library'''.

--

Comment:

 If you run "sage -i blah"  and "blah" is an optional spkg which needs to
 be downloaded, would it make more sense to save the spkg in
 $SAGE_ROOT/spkg/optional/ or in $SAGE_BUILD_TMPDIR/optional? The previous
 versions of the patch do the second of these, but I think it makes more
 sense to do the first: downloading spkg files for optional packages is not
 the same as building, so setting SAGE_BUILD_TMPDIR shouldn't cause the
 spkg files to end up somewhere nonstandard.  Another way to say it: I
 don't view downloaded spkg files for optional spkgs as temporary, the way
 build directories are.

 Here's a new patch.  I've removed the variables "BUILD" and "BUILD_DIR",
 and I've appended "build" to the setting of "$SAGE_BUILD_TMPDIR".  I still
 check whether `$SAGE_BUILD_TMPDIR` exists, as a safeguard against typos,
 for example.  Optional spkgs are kept in `$SAGE_PACKAGES/optional`
 regardless of the setting of `$SAGE_BUILD_TMPDIR.`

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/4949#comment:37>
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