Re^2: How to CPAN dry run ?

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.

Comment on Re^2: How to CPAN dry run ? Select or Download Code

Replies are listed 'Best First'.
Re^3: How to CPAN dry run ? by afoken (Chancellor) on Aug 31, 2024 at 11:33 UTC
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 -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]

Replies are listed 'Best First'.

Re^3: How to CPAN dry run ?
by afoken (Chancellor) on Aug 31, 2024 at 11:33 UTC

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

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

[reply]