Difference between revisions of "Downloads"
m (Moved core packages to own page) |
(Moved user packages to own page) |
||
Line 52: | Line 52: | ||
=== [[MainVisTrailsPackages | Packages distributed with VisTrails]] === | === [[MainVisTrailsPackages | Packages distributed with VisTrails]] === | ||
=== [[UserContributedPackages | Packages developed by users]] === | === [[UserContributedPackages | Packages developed by users]] === | ||
Revision as of 17:45, 13 March 2007
Latest Release
Revision 502 (2007-03-09 16:00) View Notes | Size | Architecture | Type |
62571080 | i586 | .zip (32-bit Windows) | |
941311 | all | Source .tar.gz |
- Instructions on how to build from source
- If you have problems downloading from our repository, we keep mirror copies at sourceforge VisTrails@SourceForge.
Mailing Lists
Information on joining mailing lists is available here.
Experimental Ubuntu Packages
Carlos Scheidegger is experimenting with Ubuntu (debian) packages and is currently making them available at http://www.sci.utah.edu/~cscheid/software. They can be installed in Ubuntu with
sudo dpkg -i vistrails-<version>.deb
These will install VisTrails on /usr/local. They currently perform no dependency checking, though this will be done in the future, together with a VisTrails apt repository. Please check back often or email him at cscheid@sci.utah.edu
VisTrails Module Packages
VisTrails makes use of packages of Modules to define and form valid workflows. Some packages are maintained and distributed with the VisTrails itself and are considered part of the core functionality. However, work has also been done on developing user-made and maintained Module Packages. Below are a current list of packages maintained by VisTrails and user packages maintained outside the core source repository. The Package Name field describes the name required by the addPackage() directive in the .vistrails/startup.py file required to load the package.