#11021: Fix "sage -info" and a bug when sourcing sage-env more than once
--------------------------------------------------------+-------------------
   Reporter:  jhpalmieri                                |          Owner:  leif 
                                                     
       Type:  defect                                    |         Status:  
needs_review                                              
   Priority:  major                                     |      Milestone:  
sage-4.7.1                                                
  Component:  packages                                  |       Keywords:  
SPKG.txt SAGE.txt -info BUILD sage-env sage-sage sage-spkg
Work_issues:                                            |       Upstream:  N/A  
                                                     
   Reviewer:  Kelvin Li, Leif Leonhardy, John Palmieri  |         Author:  Leif 
Leonhardy, Kelvin Li                                 
     Merged:                                            |   Dependencies:       
                                                     
--------------------------------------------------------+-------------------

Comment(by leif):

 I wonder if there's a better (and more efficient) way to test if an spkg
 is (bzip2-) compressed, preferably in a shell function.

 I suspect something like
 {{{
 #!sh
 if file "$spkg" | grep "bzip2" >/dev/null; then
     # it is compressed
     ...
 }}}
 wouldn't be very portable, since `file` might not recognize bzip2 files on
 some systems.

 We could also directly check the magic header instead, with e.g. `head`
 and `cut` or `dd`.

 Any further suggestions?

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