#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):

 Replying to [comment:35 jhpalmieri]:
 > Replying to [comment:31 leif]:
 > > >  - If you run "`sage -info zlib sqlite`", it says "Listing SPKG.txt
 of zlib sqlite", which looks a little funny to me.  This is not a big
 deal, but if you could fix it, that would be nice.
 > >
 > > Hmmm, that's intentional. Do you want the spkg names to be separated
 by commas?
 >
 > If possible, commas would be nice.  It looks fine with a single
 argument, but with multiple args, I think some punctuation would help.

 Well, `sage -i pkg1 pkg2 ...` behaves the same ("`Installing pkg1 pkg2
 ...`", and did before), but I can add commas to both -- easily, until we
 support (or use) spaces in spkg filenames...

 [[BR]]

 > > We (currently) don't support long options consistently, but I can also
 add that (i.e., support `--info`, too).
 >
 > We say that we do: at the end of "sage -advanced", it says
 {{{
 You can also use -- before a long option, e.g., 'sage --optional'.
 }}}
 > I see that a few options are missing, like `--merge``, but most of them
 are there.

 `sage -t --verbose ...` doesn't work either; only `sage-sage` seems to
 support (some) long options with double dashs.

 > The script sage-sage is a mess anyway, but cleaning it up belongs on
 another ticket^TM^.

 Agreed. I'd also ''remove'' long options with a ''single'' dash (i.e.,
 only allow `--` there), but others disagreed a while ago.

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