sage-devel and Randy, (cc. Kyle Mandli)
> Chris is working on a Sage spkg interface so that it can be easily
> installed as an optional package.
This raises another licensing-related issue: Clawpack requires the
following libraries and Python packages (these requirements are,
unfortunately, not well documented yet):
gfortran
numpy
matplotlib
farbtastic (listed as GPL, possibly GPLv3)
hdf5 ("BSD-style")
h5py (BSD)
I'm not sure how farbtastic fits into Clawpack. The "v3" part may be
an issue... Also, since we've been using gfortran for most of our
compilation, I'm not sure yet how Sage's g95-based Fortran compiler
will fare...
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?
Like Randy said, Clawpack 5.0 is undergoing major changes so that a
Sage spkg can be considered possible. This includes major changes in
the documentation and website!!! :) If you have any questions then
feel free to email me. (Or someone who knows more about Clawpack.)
--
Chris Swierczewski
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
