Re: Listing dependencies for Perl modules--should even the common ones get listed?

Definitely specify the minimum required version of Perl and your use of any modules such as Exporter. Just because they are in core today doesn't mean that they always will be.

You can include the pragmata or not as you wish. I doubt anyone is going to have a strong opinion on those either way.

🦛

Comment on Re: Listing dependencies for Perl modules--should even the common ones get listed?

Replies are listed 'Best First'.
Re^2: Listing dependencies for Perl modules--should even the common ones get listed? by cavac (Prior) on Nov 27, 2023 at 17:03 UTC
That also goes for any sub-dependencies that YOUR dependencies consider optional. One of the classics is (or rather: "was", thankfully) IO::Socket::INET6 when you are using IO::Socket::IP to connect over the network. When your software requires IPv6 support, you will have to make sure that the required modules actually get installed. Believe me, more than once my servers were IPv6-blind because i forgot... PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP	[reply]

Replies are listed 'Best First'.

Re^2: Listing dependencies for Perl modules--should even the common ones get listed?
by cavac (Prior) on Nov 27, 2023 at 17:03 UTC

That also goes for any sub-dependencies that YOUR dependencies consider optional. One of the classics is (or rather: "was", thankfully) IO::Socket::INET6 when you are using IO::Socket::IP to connect over the network. When your software requires IPv6 support, you will have to make sure that the required modules actually get installed. Believe me, more than once my servers were IPv6-blind because i forgot...

PerlMonks XP is useless? Not anymore: XPD - Do more with your PerlMonks XP

[reply]