<p>Does anyone have any suggestions for a good approach to finding all the CPAN dependencies that might have arisen in a bespoke development project. As tends to be the case your local development environment rarely matches your live one and as you build more and more projects you tend to build up a local library of installed modules. These then lead to you not necessarily noticing that your latest project has a requirement on a non-core module. As there is generally a requirement to package the entire project up for deployment to another group (in our case our operations team), it is important to know what modules should be included in the package.  </p>

<p>Does anyone have any insights into the problem.</p>

<p>Thanks</p>

<p>Peter</p>

In the past I have used
Devel::Modlist
which is reasonably good allowing you to go
```
```
perl -d:Modlist script.pl
```
```
To get a list of the required modules.