<URL: https://rt.cpan.org/Ticket/Display.html?id=84544 >
Log-Dispatch-File-Stamped-0.10_002 has been uploaded to PAUSE as an unauthorized release, as my $company is using it in its production code now, but I'd really like this to get your blessing :) (cc modules@perl.org - this is the third attempt to contact you over a span of a few months -- earlier attempts are when I filed this ticket, and when I inquired about a public repository and/or process for patching, via https://rt.cpan.org/Ticket/Display.html?id=84228) On Tue Apr 09 16:22:17 2013, ETHER wrote: > > Log::Dispatch::File optionally does a number of nice things, like bypassing > block buffering, closing the filehandle after every write, etc that this > module does not handle. (From t/other_options.t in the below-mentioned > repository, the options that are currently not respected are: autoflush, > close_after_write, mode, and syswrite.) > > As I really would like to use timestamped files, but keep using the > existing settings that I need in production, I've fixed this module as well > as made some modifications to Log::Dispatch::File itself to make > subclassing a little easier. > > Dave Rolsky has my fixes for Log::Dispatch::File at > https://github.com/karenetheridge/Log-Dispatch/tree/topic/fix_subclassing. > > I've rewritten ::File::Stamped to do the right thing in all cases, as well > as writing tests to confirm this, at > https://github.com/karenetheridge/Log-Dispatch-File-Stamped (using the 0.10 > release as a starting point). > > I'm happy to do anything extra that is needed to help get this into a > releasable state, up to and including taking on comaint of this module in > case you are busy/no longer interested in Perl development and/or > maintaining this module -- but no pressure, it's totally fine if you don't > want to take that route, too! > > cc: modules@perl.org > > thanks, > > Karen Etheridge > et...@cpan.org
