http://qs321.pair.com?node_id=11133273


in reply to Re: How to use the local Devel::Cover module?
in thread How to use the local Devel::Cover module?

Hi,
Thank you for the reply. I'm familiar with this special env. Did you mean the following? (added a newline):
PERL5LIB=<path-to-your-local-directory> perl -MDevel::Cover=-silent,1,-db,${cover_db}" <script>
Also, the Devel::Cover already installed in the lib of the "perl". I think it will still take the one already installed and not the one I cloned.

Replies are listed 'Best First'.
Re^3: How to use the local Devel::Cover module?
by Perlbotics (Bishop) on May 29, 2021 at 18:52 UTC

    No, I meant to have everything in one line. That way, setting of PERL5LIB is valid for this particular invocation of perl only and does not clobber the current value of PERL5LIB (if any) for the rest of your shell session (if exported).

    $: TEST=this #-- your shell might need to 'export' explicitly $: echo $TEST this $: TEST=that eval 'echo $TEST' that $: echo $TEST this

    Setting PERL5LIB the way you did, would keep the setting for the rest of your shell session. You might consider to set it in your shells configuration (.bashrc, .profile, etc.) if required.

    I am not sure, if I understood your last question.

    I think it will still take the one already installed and not the one I cloned.
    No, with path-to-your-local-directory, I meant the .../lib directory of your cloned installation. When in doubt try
    PERL5LIB=<as-needed> perl -MDevel::Cover=-coverage,none -e 'print "$D +evel::Cover::VERSION <--- HERE!\n"'
    and see if the VERSION is as expected (Devel::Cover might print that anyways in its header message).