scottclowe/matlab-continuous-integration

A method of doing Continuous integration on a CI server when developing in MATLAB

matlab-continuous-integration's Issues

Automatic download of FEX and other requirements

The Octave Forge requirements.txt installation function should be generalised so it can handle the installation of packages from MATLAB FileExchange, and curl tarball and zip files from the web.

The new specification for requirements.txt will be like so

• Blank lines will be ignored
• Lines starting with a # are comment lines and will be ignored
• Content on a line after # is ignored. (NB: Not after # alone, must have a space beforehand. This is in case URLs contain anchors.)
• Lines which begin with fex:// are explicitly declared to be FEX IDs.
• Lines which are completely numeric, or are numeric and then a hyphen and some text, are assumed to be FEX IDs.
• Lines which begin forge:// are explicitly declared to be Octave Forge packages
• Lines which do not contain :// and start with [a-zA-Z] text are assumed to be Forge packages.
• Octave Forge requirements can not be downloaded if octave is not installed. If an octave binary can not be found, these will print a warning message, but not return an error.
• Any lines which contain :// other than fex:// and forge:// are curled (optionally being cached in a cache folder) and unzipped/untarred

One can include multiple requirements.txt files intended for different environments.

Example

requirements.txt

fex://32025  # Tiff stack
31069  # RequireFEX
31069-require-fex-package
https://sites.google.com/site/nmftool/home/source-code/nmfv1_4.zip

requirements-octave.txt

forge://image
http://research.ics.aalto.fi/ica/fastica/code/FastICA_2.1.octave.tar.gz

requirments-matlab.txt

http://research.ics.aalto.fi/ica/fastica/code/FastICA_2.5.tar.gz