Best way to handle code dependencies for file exchange submissions

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

[Walter Roberson]

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

[Jim Hokanson]

I was also thinking of things like Boost (C++), Apache Commons (Java), rubygems (Ruby), EasyInstall (Python), CRAN (R), etc. I think the File Exchange is frustratingly underdeveloped and locked down. Perhaps an enterprising third party could develop something better instead of waiting for the Mathworks to act. It is perhaps especially frustrating given the use of Matlab in research computing where one would hope more focus could be spend on research instead of reinventing the wheel.