Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re^4: Should I list core modules as dependencies?

by vsespb (Chaplain)
on Jun 02, 2013 at 11:16 UTC ( #1036577=note: print w/replies, xml ) Need Help??


in reply to Re^3: Should I list core modules as dependencies?
in thread Should I list core modules as dependencies?

I usually avoid listing non-dual-lived modules because they will cause CPAN to try to install perl again, which isn't what you or the user really want. For example, if you try to install bytes---CPAN will install bytes but also all of the core all over again.
So, Git::Raw and HTML::Builder (see links in original post) are trying to install new Perl ? I doubt.

Why it should? For example 'strict' module version specified as 0, that means it's installed, and should not be updated...
  • Comment on Re^4: Should I list core modules as dependencies?

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1036577]
help
Chatterbox?
[1nickt]: choroba no kidding! The muscle memory alone makes it insignificant. I suppose the addition of param checking is nice. But if you are using MOo anyway you are using Type::Tiny, and you can easily use T::T for params in regular methods.

How do I use this? | Other CB clients
Other Users?
Others meditating upon the Monastery: (5)
As of 2017-11-24 13:59 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    In order to be able to say "I know Perl", you must have:













    Results (349 votes). Check out past polls.

    Notices?