Re^2: How to CPAN dry run ?

[mvanle]

What do you want to dry run against? Your current situated environment? A Windows, Linux or MacOS installation nearby? Do you want to ensure compilation of low-level code that isn't pure perl?

I want to review whatever cpan is doing (or going to do), and pre-determine the success of an operation before it actually modifies or installs anything, especially on a production server.

I could tolerate it downloading and installing things into 1 single known temporary directory that I can rm -rf afterwards as long as I can isolate all of its changes (and [preferably] easily rollback).

I'm also surprised the -n option still isn't implemented after +10 years.

[afoken]

I want to review whatever cpan is doing (or going to do), and pre-determine the success of an operation before it actually modifies or installs anything, especially on a production server.

That's why you should have a test/staging server configured in the same way as the production server.

Alexander