On Sat, Aug 29, 2009 at 12:25 PM, Jason Grout <jason-s...@creativetrax.com>wrote:
> > William Stein wrote: > > > Now for a development question: should I include automatic svn/hg/git > > checkout and compilation of the above packages (those that aren't > > already in Sage) in Clawpack's spkg-install script? Is that the > > standard procedure for optional spkgs? I can of course include a > "This > > will download and install x, y, and z: [Y/n]" check during the > install > > process. Since it would all occur within the Sage shell then I don't > > think it would be a bad idea. (That is, if wouldn't modify the user's > > system, just the Sage system.) Thoughts? Suggestions? > > > > > > Yes, that's a good idea. > > > In the nauty spkg, we had (have?) a point at which the user has to agree > to the license agreement. A while back, there was a big fuss about this > and having interactive spkg installs, and it seemed like the consensus > was that it was a bad idea. Good point. It's a very bad idea if it can't be easily disabled with a command line option or environment flag. This is because I often do "install all optional packages" for testing purposes, and when installing, e.g., sagenb.org's copy of Sage. William > > > > > > > Alternatively, spend some time and > > design/write a little "optional spkg dependency system" for Sage! We've > > been needing something like that for ages. > > > Definitely +1. > > Jason > > > -- > Jason Grout > > > > > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org --~--~---------~--~----~------------~-------~--~----~ To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
