we can infer from the context in this thread that it's referring to t/026FileApp.t in the Log::Log4perl distro.

Thx, haukex, I had to read all of that very carefully and serially in order to follow along. [I hadn't patched anything before.] A little more context with the new t/026FileApp.t here:

#########################################################
# Print a header into a newly opened file
#########################################################
$data = qq(
log4perl.category         = DEBUG, Logfile
log4perl.appender.Logfile          = Log::Log4perl::Appender::File
log4perl.appender.Logfile.filename = ${testfile}_5
log4perl.appender.Logfile.header_text = This is a nice header.
log4perl.appender.Logfile.layout   = Log::Log4perl::Layout::SimpleLayo
+ut
);

Log::Log4perl->init(\$data);
open FILE, "<${testfile}_5" or die "Cannot open ${testfile}_5";
$content = join '', <FILE>;
close FILE;

is($content, "This is a nice header.\n", "header_text");


# same with syswrite
unlink "${testfile}_5";
$data = qq(
log4perl.category         = DEBUG, Logfile
log4perl.appender.Logfile          = Log::Log4perl::Appender::File
log4perl.appender.Logfile.filename = ${testfile}_5
 log4perl.appender.Logfile.header_text = This is a nice header.
 log4perl.appender.Logfile.syswrite = 1
 log4perl.appender.Logfile.layout = Log::Log4perl::Layout::SimpleLayou
+t
 log4perl.appender.Logfile.mode = clobber
 );

Log::Log4perl->init(\$data);
[download]

I made mistakes on the way to get this, in particular changing the critical line

 log4perl.appender.Logfile.mode = clobber

in Log4perl.pm . I've always wondered how to make changes in the .pm's that are installed on my machine. It seemed like the wrong way to have to change permissions on the file, but I did it, because, hey, we're using force here, right? I added the line and summarily got an error when opening a cpan client window.

After patching the right file and executing:

C:\Users\tblaz\Documents\evelyn\my_repos\Log-Log4perl-1.49>cpanm .
--> Working on .
Configuring Log-Log4perl-1.49 ... OK
Building and testing Log-Log4perl-1.49 ... OK
Successfully installed Log-Log4perl-1.49
1 distribution installed

C:\Users\tblaz\Documents\evelyn\my_repos\Log-Log4perl-1.49>
[download]

, Log4perl.pm was restored to what it was before I started messing with it. I still get a complaint about the Terminal Size, but there is no mention of Log4perl being uninstalled:

Unable to get Terminal Size. The Win32 GetConsoleScreenBufferInfo call
+ didn't work. The COLUMNS and LINES environment variables didn't work
+. at C:\Strawberry\perl\vendor\lib/Term/ReadLine/readline.pm line 410
+.

cpan shell -- CPAN exploration and modules installation (v2.26)
Enter 'h' for help.

cpan>
[download]

Thanks all for comments,

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.