Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

CGI Debugging made easy + more 2 Comments More | Login | Reply /

 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.

  • How to give it back (Score:3, Informative)

    by samtregar (2699) on 2003.04.26 12:41 (#19497) Homepage Journal
    So I have some questions for anyone that is reading this. Is this so specialized a solution to my needs that others would not find much use in it?

    It sounds pretty useful to me. I spend 50% of my time writing CGI::Application modules and I'd love an easier way to debug them. Also, I know other people are working on the same problem. Someone emailed me with information about how to setup Apache to debug CGI::App modules from Komodo. I haven't had a chance to try it yet but it sounds similar to what you've done.

    If not how do I give this to the Perl community, is it a tool, a set of libs, a hack or some combination of those choices?

    The most successful Perl projects are modules on CPAN. If you can figure out a way to make it a module then you should. Keep in mind that modules are allowed to distribute scripts too (ex. Mail::SpamAssassin includes spamd and spamc).

    Do I need to contact the authors of the modules I needed to modify before I submit it to the Perl community? I just don't know what etiquette is in this situation.

    It's not a bad idea, but hardly required. I think you should at least post about it to the CGI::App mailing-list since I bet you'll find most of your users there.

    Still have more questions about open-sourcing Perl code? Why not buy my book [amazon.com]?

    -sam

Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.