Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re: Should I list core modules as dependencies?

by DrHyde (Prior)
on Jun 03, 2013 at 10:51 UTC ( #1036714=note: print w/replies, xml ) Need Help??

in reply to Should I list core modules as dependencies?

Yes, you should. What's in core varies from one version of perl to another. Normally it's just things being added so modern perls have more in core than older ones, but occasionally things get removed., for example, may be removed soon.

What's more, you should list every module your code relies on. If your code uses Foo::Bar and Baz::Barf, but Foo::Bar depends on Baz::Barf, you should declare a dependency on both of them, because at some point in the future Foo::Bar might stop depending on Baz::Barf and use something else instead.

In general, if your code mentions a module, you should list it as a pre-requisite.

  • Comment on Re: Should I list core modules as dependencies?

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1036714]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (3)
As of 2018-04-21 02:24 GMT
Find Nodes?
    Voting Booth?