MATLAB: Best way to handle code dependencies for file exchange submissions

Question

I'm planning on submitting a decent size chunk of code to the Matlab file exchange. One of the things I like least about the process is handling code dependencies that are outside the core set of files being submitted. Normally I will run a dependency check and simply include the dependent files in a separate directory with the submission. Is there a better way of doing this?

It might also be important to note that some of these dependent files are also file exchange submissions. In that case I would almost rather point them to the other FEX file than also include it in my "dependents" folder.

Thoughts and suggestions?

Answer 1

We need the MATLAB equivalent of CPAN (Comprehensive Perl Archive Network), together with the perl dependency analysis and auto-fetch routines...