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...