On Tuesday, August 18, 2015 at 6:49:47 AM UTC-7, Volker Braun wrote: > > Whats the use case of attempting to install a package without > dependencies? I can't think of any. >
I'm not sure I can come up with very compelling examples, but if I've modified some package on which gcc depends, but I really want to know whether that modification affects some other package, I may just want to run "sage -i <other package>", not wait for gcc to recompile. But your point is pretty convincing to me. > Whether you are developer or user, you always want to have your > dependencies in place before compiling something. The fact that "sage -i" > does not is 100% historical limitation. Now we can build packages with > dependencies, so we should consider the old behavior as the bug that is has > always been. > -- John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
