Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re: Best way to deal with a bug in a CORE Module (release patched version)

by Anonymous Monk
on Dec 03, 2013 at 02:48 UTC ( [id://1065359]=note: print w/replies, xml ) Need Help??


in reply to Best way to deal with a bug in a CORE Module

just make a note of it in my own docs and go on?

Bump the version number and make a note in your code/Makefile.PL

If you have a CPAN account, you should release a patched version and save the next monk-ey from having to go to rt, find patch, download patch, apply patch, deploy patch ... they can just  cpan BOTFX/AppConfig-1.6601.tar.gz and be done with it

Beyond that, there are numerous bug reports for that module, seems a bit dis-concerting for something that is included as part of CORE... CORE...

Where do you get that idea?

$ corelist AppConfig Data for 2013-11-20 AppConfig was not in CORE (or so I think)

Replies are listed 'Best First'.
Re^2: Best way to deal with a bug in a CORE Module (release patched version)
by boftx (Deacon) on Dec 03, 2013 at 02:52 UTC

    I could be mistaken, I thought I saw it in the CORE list. But then again, jokes about "old-timers disease" aren't so funny anymore. I just checked on the Perl site http://perldoc.perl.org/index-modules-A.html so it would appear you are correct.

    It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others rifling through the Monastery: (3)
As of 2024-04-16 22:29 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found