On Sun, Feb 5, 2012 at 1:15 AM, Eric Wilhelm <enoba...@gmail.com> wrote: >>It doesn't help with optional, dynamic prereqs so those have to be >>specified manually, but that's unavoidable I think. > > I've experimented with detecting those using my Devel::TraceDeps on the > running test suite. It is possible to see the source and target of > every require(), including failed ones (so you have to be using > eval+require, but you already knew it was incorrect to go stat()ing > around in @INC looking for your optional deps.)
That's a different use case (though a neat trick). Seeing optional dependency load attempts is different than knowing which ones should be included in metadata (and whether they should be "recommends" or "suggests" or omitted) and what version of them are required. -- David
