in reply to How to CPAN dry run ?

How do I perform a dry run of a module installation ?

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?

Your question is very vague. It almost seems as though you have a complaint against an unimplemented flag, yet you haven't provided any tests or anything.

You don't 'execute' downloads. If a distribution has direction, it is often make test. Done. All tests performed, including dependency checks, and nothing installed.

Replies are listed 'Best First'.
Re^2: How to CPAN dry run ?
by choroba (Cardinal) on Aug 30, 2024 at 08:46 UTC
    > it is often make test. Done. All tests performed, including dependency checks, and nothing installed.

    It already installs all the dependencies.

    map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]
[reply]
[d/l]
[select]

      I stand corrected.

[reply]
Re^2: How to CPAN dry run ?
by marto (Cardinal) on Aug 30, 2024 at 08:27 UTC

    "Your question is very vague. It almost seems as though you have a complaint against an unimplemented flag, yet you haven't provided any tests or anything."

    It's not a complaint, it's an observation based on what the documentation tells people:

    "Do a dry run, but don't actually install anything. (unimplemented)"

    I'd argue the question isn't vague, since they ask how to do a specific thing.

[reply]
Re^2: How to CPAN dry run ?
by mvanle (Acolyte) on Aug 31, 2024 at 11:04 UTC
    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.

[reply]
[d/l]
[select]
      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]

In Section Seekers of Perl Wisdom