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

Re^5: getting Log::Log4perl to install on windows strawberry perl (updated)

by haukex (Bishop)
on Jan 02, 2020 at 08:57 UTC ( #11110866=note: print w/replies, xml ) Need Help??


in reply to Re^4: getting Log::Log4perl to install on windows strawberry perl
in thread getting Log::Log4perl to install on windows strawberry perl

I've always wondered how to make changes in the .pm's that are installed on my machine.

Well, it's possible to patch them directly where they are installed in the @INC paths, but as you've discovered those changes are easily clobbered by a reinstall. So when patching something it's usually better to do so in the distributions before installation. But even in that case there are some chances for conflicts, for example, if you don't change the version number, there is a potential for confusion about whether the patched version is installed or not; and if you simply increment the version number, there is a chance for conflict when the module gets an update by the author. There are several different approaches, listing them all is probably too much, best to cross that bridge if and when you get to it and ask about it then :-) In regards to the question in this thread, note it's about modifying one of the test scripts that don't actually get installed, they only get run before installation to verify that the module was compiled ok on your machine.

Update:

Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call didn't work. The COLUMNS and LINES environment variables didn't work.

See Re: Unable to debug due to terminal problem (read) and Re: Problems starting the debugger

Replies are listed 'Best First'.
Re^6: getting Log::Log4perl to install on windows strawberry perl (updated)
by Aldebaran (Deacon) on Jan 04, 2020 at 05:30 UTC

    I finally have a script that deals with the terminal and cpan opening up with the need to overwrite a lockfile. This is a grandchild of portableshell.bat that is recommended for beginning strawberry perl on windows. I have alternated between using set TERM=dumb and commenting it out. Also, I don't want the script erasing the value of PERL5LIB, so I comment that out as well.

    @echo off rem set env variables rem set TERM=dumb set LINES=40 set COLUMNS=80 set PERL_JSON_BACKEND=JSON::XS set PERL_YAML_BACKEND=YAML rem avoid collisions with other perl stuff on your system rem set PERL5LIB= set PERL5OPT= set PERL_MM_OPT= set PERL_MB_OPT= perl -e "printf("""Perl executable: %%s\nPerl version : %%vd\n""", $ +^X, $^V)" 2>nul if ERRORLEVEL==1 echo.&echo FATAL ERROR: 'perl' does not work; check i +f your strawberry pack is complete! echo. chcp 65001 cd C:\Users\tblaz\Documents\evelyn\ dir cpan | echo y

    Thanks all for comments.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://11110866]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others having an uproarious good time at the Monastery: (10)
As of 2020-11-24 10:38 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?