Re: Customizing cpan modules

Submit your suggestions, fixes, updates, additions, etc. Have you tried doing that?

If your changes are so specific to your purposes that they might not be of any use to others, simply place The::Original::Module into namespace YourName::The::Original::Module

And use that module instead. I understand hacking Standard::Module::Used::Everywhere to do what you want it to, this is sh1++y practice. Bad practice. Bad.

Comment on Re: Customizing cpan modules

Replies are listed 'Best First'.
Re^2: Customizing cpan modules by Ovid (Cardinal) on Jul 20, 2009 at 10:44 UTC
All of our local patches are required to have the URL of the bug report attached to it. This allows future developers to come along and easily see the history, including whether or not the situation was resolved and if we can delete our local patch. The end result of this has been several ignored bug reports, including one in which two module authors seem to feel that since their modules don't play well together, the fault likes with the other author. Regrettably, sometimes a fork is required :( Cheers, Ovid The official Perl 6 wiki.	[reply]
Re^2: Customizing cpan modules by jrsimmon (Hermit) on Jul 17, 2009 at 15:18 UTC
One of the changes is what I believe to be a bug, described here. The other may or may not be a bug, depending on what the original author intended. I intend to submit both of the changes, but I'd like to do so after cleaning them up and having some run-time on them. In the mean time, I'm curious as to the best way to make changes to the modules in a way that doesn't lead to horribly disfigured /lib and /site/lib directories. All of the posts in the thread have been extremely helpful.	[reply]